{"items":[{"id":"NVI-00013088","kind":"vulnerability","title":"@grpc/grpc-js: In certain configurations, getAuthContext can return unauthorized certificates as though they were authorized","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-m9gg-hp2v-232j","CVE-2026-101916"],"plain_summary":"GitHub lists this reviewed advisory for @grpc/grpc-js, @grpc/grpc-js. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-107dfd55caee9adb80725c8d49821669"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-09-30T15:35:57.000Z","value":"7.4 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-5a491866f193cedaaccfea976501ebfb"},{"kind":"CVSS","as_of":"2026-10-01T15:17:25.083Z","value":"7.4 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-550dedcf8caf5a08f06765dfbdd2e1bf"},{"kind":"EPSS","as_of":"2026-11-03T12:00:27.000Z","value":"0.215%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.12002. Missing scores are unknown.","source_id":"sr-107dfd55caee9adb80725c8d49821669"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-5a491866f193cedaaccfea976501ebfb","url":"https://github.com/advisories/GHSA-m9gg-hp2v-232j","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-m9gg-hp2v-232j","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T07:22:52.960Z"},{"id":"sr-550dedcf8caf5a08f06765dfbdd2e1bf","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-101916","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-101916","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T09:58:04.487Z"},{"id":"sr-107dfd55caee9adb80725c8d49821669","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-101916","publisher":"FIRST EPSS","observed_at":"2026-11-03T17:44:07.769Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-5a491866f193cedaaccfea976501ebfb"],"technology":"@grpc/grpc-js","known_exclusions":[],"conditions_summary":"### Impact\nWhen server credentials are created with the `requireClientCertificate` option set to `false`, `getAuthContext` does not distinguish between authorized and unauthorized certificates in its return value. This can create improper authentication vulnerabilities for `@grpc/grpc-js` users who use the result of `getAuthContext` for authentication.\n\nIn particular, `@grpc/grpc-js-xds` can both set the `requireClientCertificate` option to `false` and use the return value of `getAuthContext` for RBAC authentication in some configurations.\n\n### Patches\n\nThis vulenrability is fixed in 1.13.6 and 1.14.5.\n\n### Workarounds\n`@grpc/grpc-js` users using `getAuthContext` this way can avoid this problem by setting `requireClientCertificate` to `true`. `@grpc/grpc-js-xds` users using RBAC can avoid this by setting the `require_client_certificate` field to `true` in the DownstreamTlsContext in the xDS configuration.","public_affected_ranges":["< 1.13.6"]},{"certainty":"source_listed","source_ids":["sr-5a491866f193cedaaccfea976501ebfb"],"technology":"@grpc/grpc-js","known_exclusions":[],"conditions_summary":"### Impact\nWhen server credentials are created with the `requireClientCertificate` option set to `false`, `getAuthContext` does not distinguish between authorized and unauthorized certificates in its return value. This can create improper authentication vulnerabilities for `@grpc/grpc-js` users who use the result of `getAuthContext` for authentication.\n\nIn particular, `@grpc/grpc-js-xds` can both set the `requireClientCertificate` option to `false` and use the return value of `getAuthContext` for RBAC authentication in some configurations.\n\n### Patches\n\nThis vulenrability is fixed in 1.13.6 and 1.14.5.\n\n### Workarounds\n`@grpc/grpc-js` users using `getAuthContext` this way can avoid this problem by setting `requireClientCertificate` to `true`. `@grpc/grpc-js-xds` users using RBAC can avoid this by setting the `require_client_certificate` field to `true` in the DownstreamTlsContext in the xDS configuration.","public_affected_ranges":[">= 1.14.0, < 1.14.5"]}],"null_published_at":"2026-11-06T00:29:57.288Z","source_updated_at":"2026-09-30T15:35:57.000Z","source_disclosed_at":"2026-09-30T15:35:53.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-11-01T07:22:52.960Z"},{"id":"NVI-00013088","kind":"vulnerability","title":"@grpc/grpc-js: In certain configurations, getAuthContext can return unauthorized certificates as though they were authorized","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-m9gg-hp2v-232j","CVE-2026-101916"],"plain_summary":"GitHub lists this reviewed advisory for @grpc/grpc-js, @grpc/grpc-js. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-550dedcf8caf5a08f06765dfbdd2e1bf"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-09-30T15:35:57.000Z","value":"7.4 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-5a491866f193cedaaccfea976501ebfb"},{"kind":"CVSS","as_of":"2026-10-01T15:17:25.083Z","value":"7.4 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-550dedcf8caf5a08f06765dfbdd2e1bf"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-5a491866f193cedaaccfea976501ebfb","url":"https://github.com/advisories/GHSA-m9gg-hp2v-232j","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-m9gg-hp2v-232j","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T07:22:52.960Z"},{"id":"sr-550dedcf8caf5a08f06765dfbdd2e1bf","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-101916","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-101916","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T09:58:04.487Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-5a491866f193cedaaccfea976501ebfb"],"technology":"@grpc/grpc-js","known_exclusions":[],"conditions_summary":"### Impact\nWhen server credentials are created with the `requireClientCertificate` option set to `false`, `getAuthContext` does not distinguish between authorized and unauthorized certificates in its return value. This can create improper authentication vulnerabilities for `@grpc/grpc-js` users who use the result of `getAuthContext` for authentication.\n\nIn particular, `@grpc/grpc-js-xds` can both set the `requireClientCertificate` option to `false` and use the return value of `getAuthContext` for RBAC authentication in some configurations.\n\n### Patches\n\nThis vulenrability is fixed in 1.13.6 and 1.14.5.\n\n### Workarounds\n`@grpc/grpc-js` users using `getAuthContext` this way can avoid this problem by setting `requireClientCertificate` to `true`. `@grpc/grpc-js-xds` users using RBAC can avoid this by setting the `require_client_certificate` field to `true` in the DownstreamTlsContext in the xDS configuration.","public_affected_ranges":["< 1.13.6"]},{"certainty":"source_listed","source_ids":["sr-5a491866f193cedaaccfea976501ebfb"],"technology":"@grpc/grpc-js","known_exclusions":[],"conditions_summary":"### Impact\nWhen server credentials are created with the `requireClientCertificate` option set to `false`, `getAuthContext` does not distinguish between authorized and unauthorized certificates in its return value. This can create improper authentication vulnerabilities for `@grpc/grpc-js` users who use the result of `getAuthContext` for authentication.\n\nIn particular, `@grpc/grpc-js-xds` can both set the `requireClientCertificate` option to `false` and use the return value of `getAuthContext` for RBAC authentication in some configurations.\n\n### Patches\n\nThis vulenrability is fixed in 1.13.6 and 1.14.5.\n\n### Workarounds\n`@grpc/grpc-js` users using `getAuthContext` this way can avoid this problem by setting `requireClientCertificate` to `true`. `@grpc/grpc-js-xds` users using RBAC can avoid this by setting the `require_client_certificate` field to `true` in the DownstreamTlsContext in the xDS configuration.","public_affected_ranges":[">= 1.14.0, < 1.14.5"]}],"null_published_at":"2026-11-05T19:10:23.272Z","source_updated_at":"2026-09-30T15:35:57.000Z","source_disclosed_at":"2026-09-30T15:35:53.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-11-01T07:22:52.960Z"},{"id":"NVI-00013088","kind":"vulnerability","title":"@grpc/grpc-js: In certain configurations, getAuthContext can return unauthorized certificates as though they were authorized","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-m9gg-hp2v-232j","CVE-2026-101916"],"plain_summary":"GitHub lists this reviewed advisory for @grpc/grpc-js, @grpc/grpc-js. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-5a491866f193cedaaccfea976501ebfb"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-09-30T15:35:57.000Z","value":"7.4 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-5a491866f193cedaaccfea976501ebfb"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-5a491866f193cedaaccfea976501ebfb","url":"https://github.com/advisories/GHSA-m9gg-hp2v-232j","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-m9gg-hp2v-232j","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T07:22:52.960Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-5a491866f193cedaaccfea976501ebfb"],"technology":"@grpc/grpc-js","known_exclusions":[],"conditions_summary":"### Impact\nWhen server credentials are created with the `requireClientCertificate` option set to `false`, `getAuthContext` does not distinguish between authorized and unauthorized certificates in its return value. This can create improper authentication vulnerabilities for `@grpc/grpc-js` users who use the result of `getAuthContext` for authentication.\n\nIn particular, `@grpc/grpc-js-xds` can both set the `requireClientCertificate` option to `false` and use the return value of `getAuthContext` for RBAC authentication in some configurations.\n\n### Patches\n\nThis vulenrability is fixed in 1.13.6 and 1.14.5.\n\n### Workarounds\n`@grpc/grpc-js` users using `getAuthContext` this way can avoid this problem by setting `requireClientCertificate` to `true`. `@grpc/grpc-js-xds` users using RBAC can avoid this by setting the `require_client_certificate` field to `true` in the DownstreamTlsContext in the xDS configuration.","public_affected_ranges":["< 1.13.6"]},{"certainty":"source_listed","source_ids":["sr-5a491866f193cedaaccfea976501ebfb"],"technology":"@grpc/grpc-js","known_exclusions":[],"conditions_summary":"### Impact\nWhen server credentials are created with the `requireClientCertificate` option set to `false`, `getAuthContext` does not distinguish between authorized and unauthorized certificates in its return value. This can create improper authentication vulnerabilities for `@grpc/grpc-js` users who use the result of `getAuthContext` for authentication.\n\nIn particular, `@grpc/grpc-js-xds` can both set the `requireClientCertificate` option to `false` and use the return value of `getAuthContext` for RBAC authentication in some configurations.\n\n### Patches\n\nThis vulenrability is fixed in 1.13.6 and 1.14.5.\n\n### Workarounds\n`@grpc/grpc-js` users using `getAuthContext` this way can avoid this problem by setting `requireClientCertificate` to `true`. `@grpc/grpc-js-xds` users using RBAC can avoid this by setting the `require_client_certificate` field to `true` in the DownstreamTlsContext in the xDS configuration.","public_affected_ranges":[">= 1.14.0, < 1.14.5"]}],"null_published_at":"2026-11-01T07:29:12.917Z","source_updated_at":"2026-09-30T15:35:57.000Z","source_disclosed_at":"2026-09-30T15:35:53.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-01T07:22:52.960Z"}],"next_cursor":null,"snapshot_revision":"42594"}