Quick answers
- Is CVE-2026-101914 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-101914 being exploited in the wild.
- How severe is CVE-2026-101914?
- Medium severity, with a CVSS score of 6.5, published 28 September 2026.
- Which products and versions are affected?
- Google Grpc-Js-Xds < 1.13.1, = 1.14.0; @grpc/grpc-js-xds (npm) SEMVER:introduced=0,fixed=1.13.1.
- Is there a fix for CVE-2026-101914?
- Yes. @grpc/grpc-js-xds (npm): upgrade to 1.13.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-101914 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-101914?
- Check whether you run Google Grpc-Js-Xds or @grpc/grpc-js-xds (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @grpc/grpc-js-xds (npm): upgrade to 1.13.1 or later
npm install @grpc/grpc-js-xds@1.13.1
Technical details
The exact path matcher in the RBAC implementation applies a prefix match instead of an exact match for case-insensitive method name comparisons, violating the intended authorization semantics. An unauthenticated network attacker can exploit this by invoking a gRPC method whose name is a prefix of a differently-protected method when case-insensitive matching is configured. The fix applies exact matching logic consistently across both case-sensitive and case-insensitive paths.
Affected products
- Google grpc-js-xds < 1.13.1, = 1.14.0
Identifiers
- CVE-2026-101914
- GHSA-88h9-xgvx-hvf2
Timeline
- 2026-09-17: disclosed
- 2026-09-17: patched: Patches released in versions 1.13.1 and 1.14.1