@grpc/grpc-js: In certain configurations, getAuthContext can return unauthorized certificates as though they were authorized

Why it is Yellow

• CVSS 7.4 high
• Remotely exploitable without logging in
• On your watchlist: npm

Affected packages

References

• https://github.com/advisories/GHSA-m9gg-hp2v-232j
• https://github.com/grpc/grpc-node/security/advisories/GHSA-m9gg-hp2v-232j
• https://nvd.nist.gov/vuln/detail/CVE-2026-101916
• https://github.com/grpc/grpc-node/commit/2a84ec8b01b9db68ed9d2b117a53a81449edb8ee
• https://github.com/grpc/grpc-node/commit/b4e0079c6d22a2adedfcac748e0bc083f783bc7c
• https://github.com/grpc/grpc-node/releases/tag/@grpc/grpc-js%401.14.5
• https://github.com/advisories/GHSA-m9gg-hp2v-232j

Original description

@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.