Vulnerability in @grpc/grpc-js-xds (CVE-2026-101914)
Summary
Vulnerability in @grpc/grpc-js-xds (CVE-2026-101914). Data can be tampered with by attackers. Mitigation: upgrade to 1.13.1 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-101914 has been found in @grpc/grpc-js-xds.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade @grpc/grpc-js-xds to 1.13.1 or later.
If unsure, ask your IT team or search "@grpc/grpc-js-xds CVE-2026-101914" on the vendor's site.
CVE-2026-101914 (@grpc/grpc-js-xds) — CWE-187 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.13.1 — apply immediately
Workaround: This problem can be avoided by enabling case-sensitive path matching.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-187) exists in @grpc/grpc-js-xds.
Check the vendor advisory for the affected versions of @grpc/grpc-js-xds.
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.
Update to 1.13.1.
Workaround: This problem can be avoided by enabling case-sensitive path matching.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@grpc/grpc-js-xds' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@grpc/grpc-js-xds' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@grpc/grpc-js-xdsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
This problem can be avoided by enabling case-sensitive path matching.パッチが適用されるまでの応急処置として、This problem can be avoided by enabling case-sensitive path matching. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade @grpc/grpc-js-xds to 1.13.1ステージング環境で 1.13.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com