CVE-2026-101916: CWE-295: Improper Certificate Validation in grpc grpc-node
@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.
AI Analysis
Technical Summary
@grpc/grpc-js, a JavaScript implementation of gRPC core functionality, had a flaw in its getAuthContext function prior to versions 1.13.6 and 1.14.5. When server credentials were configured with requireClientCertificate set to false, getAuthContext failed to differentiate between authorized and unauthorized peer certificates. This improper certificate validation could lead applications relying on the authentication context to accept unauthorized certificates as valid, resulting in improper authentication. The @grpc/grpc-js-xds component could also be affected under RBAC authentication in these versions. The vulnerability is addressed by updating to versions 1.13.6 or 1.14.5 or later.
Potential Impact
The vulnerability allows improper authentication by treating unauthorized peer certificates as authorized when requireClientCertificate is false. This can lead to unauthorized access or trust in unverified clients, compromising the security of applications using the affected grpc-node versions. The CVSS score of 7.4 indicates a high impact on confidentiality and integrity without affecting availability.
Mitigation Recommendations
Upgrade affected grpc-node versions to 1.13.6 or 1.14.5 or later, where the issue is fixed. No other mitigation is required as the fix is officially available. There is no indication of active exploitation in the wild.
CVE-2026-101916: CWE-295: Improper Certificate Validation in grpc grpc-node
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.
CVSS v3.1
Score 7.4high
Affected software
grpc
grpc-node
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
@grpc/grpc-js, a JavaScript implementation of gRPC core functionality, had a flaw in its getAuthContext function prior to versions 1.13.6 and 1.14.5. When server credentials were configured with requireClientCertificate set to false, getAuthContext failed to differentiate between authorized and unauthorized peer certificates. This improper certificate validation could lead applications relying on the authentication context to accept unauthorized certificates as valid, resulting in improper authentication. The @grpc/grpc-js-xds component could also be affected under RBAC authentication in these versions. The vulnerability is addressed by updating to versions 1.13.6 or 1.14.5 or later.
Potential Impact
The vulnerability allows improper authentication by treating unauthorized peer certificates as authorized when requireClientCertificate is false. This can lead to unauthorized access or trust in unverified clients, compromising the security of applications using the affected grpc-node versions. The CVSS score of 7.4 indicates a high impact on confidentiality and integrity without affecting availability.
Mitigation Recommendations
Upgrade affected grpc-node versions to 1.13.6 or 1.14.5 or later, where the issue is fixed. No other mitigation is required as the fix is officially available. There is no indication of active exploitation in the wild.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-09-28T15:55:37.907Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6abacf14f7a7c541062b9a4e
Added to database: 09/28/2026, 20:33:24 UTC
Last enriched: 09/28/2026, 20:47:55 UTC
Last updated: 09/29/2026, 02:47:59 UTC
Views: 9
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.