Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-101915 low CVSS 3.7

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

Summary

Vulnerability in @grpc/grpc-js (CVE-2026-101915). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.13.6 or later.

Original description

The description as published by the source.

Impact

If an application method handler crashes, the error message is included in the status message sent to the client. This can leak to the client any sensitive data that may be included in the error message. This impacts anyone using @grpc/grpc-js to run servers.

Patches

This vulnerability is fixed in 1.13.6 and 1.14.5.

Workarounds

This can be avoided by using a top-level error handler in method handlers to strip out sensitive error information.

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-101915 has been found in @grpc/grpc-js.
Risk of unauthorized operations or information disclosure. CVSS score: 3.7/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-101915" on the vendor's site.

CVE-2026-101915 (@grpc/grpc-js) — CWE-550 / CVSS v3 3.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.13.6 — apply immediately
Workaround: This can be avoided by using a top-level error handler in method handlers to strip out sensitive error information.
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-550) exists in @grpc/grpc-js.

📍 Affected scope

Check the vendor advisory for the affected versions of @grpc/grpc-js.

🔥 Severity

Severity: Low (CVSS 3.7/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.13.6.

🛡️ Workaround

Workaround: This can be avoided by using a top-level error handler in method handlers to strip out sensitive error information.

🔍 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 
    This can be avoided by using a top-level error handler in method handlers to strip out sensitive error information.

    パッチが適用されるまでの応急処置として、This can be avoided by using a top-level error handler in method handlers to strip out sensitive error information. を実施。回避策の副作用 (機能低下) を確認した上で。

  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