Answer in brief
CVE-2026-101914 records a Medium severity (CVSS 6.5) vulnerability in @grpc/grpc-js: The exact path match matcher incorrectly only applies a prefix match for case-insensitive matches. The current sources do not mark it as known exploited. The current feed maps grpc/grpc-node (generic), @grpc/grpc-js-xds (npm), @grpc/grpc-js-xds (npm). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps grpc/grpc-node (generic), @grpc/grpc-js-xds (npm), @grpc/grpc-js-xds (npm). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| grpc/grpc-nodegeneric | <1.13.1 || >=1.14.0 <1.14.1 | 1.13.1, 1.14.1 |
| @grpc/grpc-js-xdsnpm | <1.13.1 | 1.13.1 |
| @grpc/grpc-js-xdsnpm | =1.14.0 | 1.14.1 |
Published upstream
Sep 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 28, 2026
@grpc/grpc-js implements the core functionality of gRPC purely in JavaScript, without a C++ addon. Prior to 1.13.1 and 1.14.1, the exact path (method name) matcher used by RBAC performs a prefix comparison instead of an equality comparison when case-insensitive matching is enabled. If one service method name prefixes another and the methods have different access rules, a request for the longer method can match the shorter method's rule and cause incorrect authorization. This issue is fixed in versions 1.13.1 and 1.14.1.
Quoted source text, attributed separately from HOL analysis.