Categories
CVE-2026-101916 high CVSS 7.4

Vulnerability in @grpc/grpc-js (CVE-2026-101916)

Summary

Vulnerability in @grpc/grpc-js (CVE-2026-101916). Confidential information can be exposed externally. Exploitable via requireClientCertificate. Mitigation: upgrade to 1.13.6 or later.

Original description

The description as published by the source.

Impact

When server credentials are created with the requireClientCertificate option set to false, getAuthContext does not distinguish between authorized and unauthorized certificates in its return value. This can create improper authentication vulnerabilities for @grpc/grpc-js users who use the result of getAuthContext for authentication.

In particular, @grpc/grpc-js-xds can both set the requireClientCertificate option to false and use the return value of getAuthContext for RBAC authentication in some configurations.

Patches

This vulenrability is fixed in 1.13.6 and 1.14.5.

Workarounds

@grpc/grpc-js users using getAuthContext this way can avoid this problem by setting requireClientCertificate to true. @grpc/grpc-js-xds users using RBAC can avoid this by setting the require_client_certificate field to true in the DownstreamTlsContext in the xDS configuration.

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-101916 has been found in @grpc/grpc-js.
Attackers can target a specific entry point like requireClientCertificate over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.4/10.
What to do: upgrade @grpc/grpc-js to 1.13.6 or later.
If unsure, ask your IT team or search "@grpc/grpc-js CVE-2026-101916" on the vendor's site.

CVE-2026-101916 (@grpc/grpc-js) — CWE-295 / CVSS v3 7.4
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: requireClientCertificate / false / getAuthContext / true
Patched: 1.13.6 — apply immediately
Workaround: @grpc/grpc-js users using getAuthContext this way can avoid this problem by setting requireClientCertificate to true.
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.

❓ What is the problem

A vulnerability (CWE-295) exists in @grpc/grpc-js. Attackers reach the vulnerable code path via requireClientCertificate without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of @grpc/grpc-js. Attack surface: requireClientCertificate / false / getAuthContext / true.

🔥 Severity

Severity: High (CVSS 7.4/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 1.13.6.

🛡️ Workaround

Workaround: @grpc/grpc-js users using getAuthContext this way can avoid this problem by setting requireClientCertificate to true.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@grpc/grpc-js' . 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

  1. 1
    Identify exposure identify
    grep -r '@grpc/grpc-js' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @grpc/grpc-js を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate
    `@grpc/grpc-js` users using `getAuthContext` this way can avoid this problem by setting `requireClientCertificate` to `true`.

    パッチが適用されるまでの応急処置として、@grpc/grpc-js users using getAuthContext this way can avoid this problem by setting requireClientCertificate to true. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch
    Upgrade @grpc/grpc-js to 1.13.6

    ステージング環境で 1.13.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @grpc/grpc-js
[{"type":"SEMVER","events":[{"introduced":"1.14.0"},{"fixed":"1.14.5"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details