@grpc/grpc-js: In certain configurations, getAuthContext can return unauthorized certificates as though they were authorized — GHSA-M9GG-HP2V-232J
GitHub · GitHub · GHSA-M9GG-HP2V-232J
ID
GHSA-M9GG-HP2V-232J
GHSA-M9GG-HP2V-232J
Date
Source
GitHub
GitHub
Vendor
GitHub
GitHub
Threat
high
high
CVSS
7.4
7.4
EPSS
0.00208
0.00208
Summary
### Impact When 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. In particular, `@grpc/grpc-js-xds` can both set the…
Timeline
- Published by source
- 2026-09-30
Risk context
- Reported severity or threat level: high.
- Reported CVSS score: 7.4 out of 10.
- Reported EPSS value: 0.00208.
- Review exposure for the affected product or family: npm: @grpc/grpc-js.
Product
npm: @grpc/grpc-js
What to do
General, cautious steps (verify details in the official source):
- Prioritize patching or mitigation immediately (treat as actively risky).
- Identify affected product versions in your inventory and verify whether you are impacted.
- Apply vendor patches/updates or recommended mitigations as soon as available.
- Read the official advisory for exact affected versions and remediation steps.
Official advisory
Evidence and provenance
- Canonical advisory ID
- GHSA-M9GG-HP2V-232J
- Source
- GitHub
- Vendor
- GitHub
- Published by source
- 2026-09-30
- Last source activity
- 2026-09-30
- Additional identifiers
- CVE-2026-101916
- Curated by
- hlukh.ch
Related advisories and connections
These advisories are connected by shared CVE, product, vendor, source, or time signals.