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.
Published: 2026-09-28
Score: 7.4 High
EPSS: n/a
KEV: No
Impact: Improper Authentication
Action: Apply Patch
AI Analysis

Impact

@grpc/grpc-js improperly treats unauthorized peer certificates as authorized when server credentials set requireClientCertificate is false, allowing an attacker to gain authorized status by presenting any certificate. The flaw is based on CWE-295 and leads to unauthorized access to the application’s protected resources.

Affected Systems

The vulnerability affects the grpc:grpc-node project, specifically @grpc/grpc-js versions prior to 1.13.6 and 1.14.5. Applications using these libraries in configurations with RBAC authentication enabled are at risk.

Risk and Exploitability

The CVSS score is 7.4, indicating high severity, and the vulnerability is not listed in CISA KEV. EPSS data is unavailable. Attackers can exploit the issue by sending a gRPC request with an unauthorized certificate to a server that accepts such certificates, effectively bypassing authentication. The exposure is limited to deployments that use the affected library versions with the described configuration.

Generated by OpenCVE AI on September 28, 2026 at 21:26 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade grpc-node to version 1.13.6 or later
  • Upgrade grpc-node to version 1.14.5 or later
  • If immediate upgrade is not possible, configure the server to set requireClientCertificate to true so that getAuthContext does not return unauthorized certificates
  • As an interim measure, add application logic to validate that the authentication context contains a valid authorized certificate before granting access

Generated by OpenCVE AI on September 28, 2026 at 21:26 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 28 Sep 2026 20:30:00 +0000

Type Values Removed Values Added
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.
Title @grpc/grpc-js: In certain configurations, getAuthContext can return unauthorized certificates as though they were authorized
Weaknesses CWE-295
References
Metrics cvssV3_1

{'score': 7.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N'}

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-09-28T20:01:53.640Z

Reserved: 2026-09-28T15:55:37.907Z

Link: CVE-2026-101916

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-28T21:17:13.030

Modified: 2026-09-28T21:17:13.030

Link: CVE-2026-101916

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-28T21:30:07Z

Weaknesses
  • CWE-295

    Improper Certificate Validation