@grpc/grpc-js implements the core functionality of gRPC purely in JavaScript, without a C++ addon. Before…
Historical advisory recorded 15 Nov 2026 00:30:56 UTC. Read the latest advisory.
nvd · CVE-2026-126367
Published@grpc/grpc-js implements the core functionality of gRPC purely in JavaScript, without a C++ addon. Before 1.13.2, and from 1.14.0 through 1.14.1, the @grpc/grpc-js-xds SafeRegexValueMatcher and PathSafeRegexValueMatcher add start and end anchors without grouping a supplied top-level alternation. An expression intended to match one of several complete values can therefore match a prefix, substring, or suffix. The affected matchers are used for route selection, xDS credential identity matching, and RBAC URL path, principal name, server name, and header rules. An ALLOW policy using an alternation can consequently accept a method, certificate identity, or header value outside the intended set, while a DENY policy becomes broader rather than permissive. This issue is fixed in versions 1.13.2 and 1.14.2.
Read the publisher's advisoryAffected versions, risk and source history
nvd · CVE-2026-126367
PublishedNVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Received
Weakness classifications: CWE-625 · CWE-863
Original publisher date fields
published: 2026-11-13T00:20:12.563
lastModified: 2026-11-13T00:20:12.563
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
Original source record · Cite this exact observation · Complete original publisher JSON