Skip to main content
VulnerabilityPublished

CVE-2026-101914: grpc-node · Partial String Comparison

Affects grpc-nodeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 1.14.1 or 1.13.1 when convenient.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.14.1, 1.13.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 13 Nov 2026.

What to do

Upgrade grpc-node and @grpc/grpc-js to 1.14.1 or 1.13.1.

Affected software

ProductAffectedFixed in
grpcgrpc-nodeAffected
  • >=1.14.0 <1.14.1
Fixed in
  • 1.14.1
grpcgrpc-nodeAffected
  • <1.13.1
Fixed in
  • 1.13.1
npm@grpc/grpc-jspkg:npm/@grpc/grpc-jsOther threatsAffected
  • <1.13.1
  • >=1.14.0 <1.14.1
Fixed in
  • 1.13.1
  • 1.14.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade grpc-node to version 1.13.1 or later, or to version 1.14.1 or later to ensure the path matcher performs exact equality comparisons for method names when case-insensitive matching is enabled. No other mitigation is indicated.

Description

A vulnerability in grpc-node versions prior to 1.13.1 and between 1.14.0 and 1.14.1 causes the RBAC path matcher to perform a prefix comparison instead of an equality comparison when case-insensitive matching is enabled. This can lead to incorrect authorization if one method name prefixes another and they have different access rules. The issue is fixed in versions 1.13.1 and 1.14.1.

References

Community reviews

Loading reviews…