Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The @grpc/grpc-js package versions below 1.13.6, and versions from 1.14.0 up to but not including 1.14.5, are affected. When server credentials are created with requireClientCertificate set to false, getAuthContext does not separate authorized client certificates from unauthorized ones, so applications that rely on its result for authentication can be led to accept unauthorized certificates. Upgrade to 1.13.6 or 1.14.5. Until then, set requireClientCertificate to true, or for @grpc/grpc-js-xds RBAC, set require_client_certificate to true in the DownstreamTlsContext.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.4 | High | 3.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0022, the 12th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 13:34 UTC First seen by agentprime
- 31 Oct 2026, 13:34 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-m9gg-hp2v-232j
- OSV: GHSA-m9gg-hp2v-232j
- github.com/grpc/grpc-node/security/advisories/GHSA-m9gg-hp2v-232j
- nvd.nist.gov/vuln/detail/CVE-2026-101916
- github.com/grpc/grpc-node/commit/2a84ec8b01b9db68ed9d2b117a53a81449edb8ee
- github.com/grpc/grpc-node/commit/b4e0079c6d22a2adedfcac748e0bc083f783bc7c
- github.com/grpc/grpc-node
- github.com/grpc/grpc-node/releases/tag/@grpc/grpc-js%401.14.5