CVE-2026-126367: @grpc/grpc-js · safe_regex incorrectly applies partial string matching for patterns with alternation
Affects @grpc/grpc-js-xdsSource GCVE Database
Not known to be exploited · CVSS 4.8 Medium : upgrade to 1.14.2 when convenient.
Data as of 13 Nov 2026, 00:08 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 4.8 |
|---|
- Patch
- Available – fixed in 1.14.2, 1.13.2
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 12 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.
What to do
Upgrade @grpc/grpc-js-xds to 1.14.2; @grpc/grpc-js-xds to 1.13.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npm@grpc/grpc-js-xds | Affected
| Fixed in
|
| npm@grpc/grpc-js-xds | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available and users should upgrade to versions 1.14.2 or 1.13.2 or later to resolve this issue. Applying these fixed versions will correct the regex matching behavior and prevent the overly permissive matches. No additional mitigation steps are required beyond upgrading.
Description
A vulnerability in @grpc/grpc-js-xds safe_regex matchers causes incorrect partial string matching when regex patterns use alternation. This leads to overly permissive matches in route selection, xDS credentials, and RBAC rules, potentially allowing unauthorized access. The issue arises because the regex anchors are applied incorrectly, causing patterns like "a|b|c" to match unintended strings. This affects versions >=1.14.0 <1.14.2 and <1.13.2 and is fixed in 1.14.2 and 1.13.2.
References
- github.com/grpc/grpc-node/security/advisories/GHSA-r7hq-q2xm-6c5m (opens in a new tab)
- github.com/grpc/grpc-node/commit/3fc3b0ebf7a89d64843a73679951142d33b40cb1 (opens in a new tab)
- github.com/grpc/grpc-node/commit/57a67e96babcb29b6eabc1833221ccf2fa152d43 (opens in a new tab)
- github.com/grpc/grpc-node (opens in a new tab)
- github.com/grpc/grpc-node/releases/tag/@grpc/grpc-js-xds@1.13.2 (opens in a new tab)
- github.com/grpc/grpc-node/releases/tag/@grpc/grpc-js-xds@1.14.2 (opens in a new tab)