CVE
gRPC Node authorization bypass in xDS safe regex matching
- Exploited
- No known exploitation
- Fix
- Fixed in 1.13.2, 1.14.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.13.2, 1.14.2.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.16% · 5th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 32/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The `@grpc/grpc-js` xDS safe-regex matchers add start and end anchors without grouping a top-level alternation, so a pattern meant to match one of several complete values can instead match a prefix, substring, or suffix. An attacker can remotely, without logging in, get past ALLOW rules that use alternation, such as a method, certificate identity, or header value outside the intended set.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
@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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach10/20Affects npm packages
- Severity4.8/10CVSS 4.8
- No patch0/5No signal
What would change the score
- Would score about 77 if added to CISA KEV
- Would score about 72 if CISA's SSVC rates exploitation active
- Would score about 37 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.13.2, 1.14.2.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126367 (@grpc/grpc-js: safe_regex incorrectly applies partial string matching for patterns with alternation), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126367 (entry last updated 2026-11-12):
Affected:
- grpc grpc-node: fixed in 1.13.2; from 1.14.0, fixed in 1.14.2
- npm package @grpc/grpc-js-xds: from 1.14.0, fixed in 1.14.2
- npm package @grpc/grpc-js-xds: fixed in 1.13.2
Fixed versions: 1.13.2, 1.14.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-126367 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126367 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/grpc/grpc-node/security/advisories/GHSA-r7hq-q2xm-6c5m
- https://github.com/grpc/grpc-node/commit/3fc3b0ebf7a89d64843a73679951142d33b40cb1
- https://github.com/grpc/grpc-node/commit/57a67e96babcb29b6eabc1833221ccf2fa152d43
- https://github.com/grpc/grpc-node/releases/tag/@grpc/grpc-js-xds@1.13.2
- https://github.com/grpc/grpc-node/releases/tag/@grpc/grpc-js-xds@1.14.2
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126367
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126367"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- grpc grpc-node
fixed in 1.13.2; From 1.14.0 · fixed in 1.14.2
From 1.14.0 · fixed in 1.14.2
fixed in 1.13.2
Evidence 7
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 4
- Repository
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126367
Is CVE-2026-126367 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-126367?
grpc-node: before 1.13.2; from 1.14.0 before 1.14.2. @grpc/grpc-js-xds (npm): from 1.14.0 before 1.14.2. @grpc/grpc-js-xds (npm): before 1.13.2.Source: cve.now feed data
How do I fix CVE-2026-126367?
Upgrade to a fixed version: 1.13.2, 1.14.2.Source: cve.now feed data