CVE-2026-101916@grpc/grpc-js: In certain configurations, getAuthContext can return unauthorized certificates as though they were authorized
Updated under an hour ago ()
Does this affect you?
It affects grpc-node. Add what you run to find out whether that includes you.
EPSS puts the chance of exploitation in the next 30 days at 0.21%, higher than 10% of scored CVEs.
Do this next
Free account, 1 product
@grpc/grpc-js implements the core functionality of gRPC purely in JavaScript, without a C++ addon. Prior to 1.13.6 and 1.14.5, getAuthContext does not distinguish authorized from unauthorized peer certificates when server credentials set requireClientCertificate to false. When applications use the returned authentication context, they can treat an unauthorized certificate as authorized, causing improper authentication. @grpc/grpc-js-xds can reach this condition when RBAC authentication is enabled in affected configurations. This issue is fixed in version 1.14.5 and 1.13.6.
- CVSS
- 7.4 HIGH (v3.1, CNA)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
- Weakness (CWE)
- CWE-295
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- 0.21% (percentile 10)
- Assigned by
- GitHub_M
- NVD analysis
- Deferred
- Record last updated
- Oct 1, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
grpc grpc-node grpc:node (from the name) | before 1.13.6; from 1.14.0, < 1.14.5 | CNA record |
References
- https://github.com/grpc/grpc-node/security/advisories/GHSA-m9gg-hp2v-232jx-refsource-confirm
- https://github.com/grpc/grpc-node/commit/2a84ec8b01b9db68ed9d2b117a53a81449edb8eex-refsource-misc
- https://github.com/grpc/grpc-node/commit/b4e0079c6d22a2adedfcac748e0bc083f783bc7cx-refsource-misc
- https://github.com/grpc/grpc-node/releases/tag/@grpc/grpc-js%401.14.5x-refsource-misc
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.