@grpc/grpc-js: The exact path match matcher incorrectly only applies a prefix match for case-insensitive matches
### Impact When using RBAC to apply authentication rules, the exact path (method name) matcher applies a prefix match instead of an exact match for case-insensitive matches. As a result, if a service has a method with a name that is a prefix of the name of a different method, and they have different access rules, and case-insensitive matching is used, this bug can cause improper authentication. ### Patches This vulnerability is fixed in 1.13.1 and 1.14.1. ### Workarounds This problem can be avoided by enabling case-sensitive path matching.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-101914US | —OT elevated | — | ||
@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 per… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/grpc/grpc-nodePACKAGE
- https://github.com/grpc/grpc-node/commit/6cf64b596da03f1942a6b168998f0670217a99c4WEB
- https://github.com/grpc/grpc-node/commit/a6c5b31180cc8cea94d0a5ea215ce31a49e0409fWEB
- https://github.com/grpc/grpc-node/commit/f32f3712e44581d8dfc8359bd8d30096662f4c75WEB
- https://github.com/grpc/grpc-node/releases/tag/@grpc/grpc-js-xds%401.13.1WEB
- https://github.com/grpc/grpc-node/releases/tag/@grpc/grpc-js-xds%401.14.1WEB
- https://github.com/grpc/grpc-node/security/advisories/GHSA-88h9-xgvx-hvf2WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan