Vulnerability in grpc (CVE-2026-48854)
Summary
Vulnerability in grpc (CVE-2026-48854). Risk of unauthorized operations or information disclosure. Exploitable via WINDOW_UPDATE. Mitigation: upgrade to 1.0.0 or later.
Original description
The description as published by the source.
Summary
Allocation of Resources Without Limits or Throttling vulnerability in elixir-grpc grpc allows unauthenticated attackers to exhaust the BEAM's memory and crash the server by streaming a large or slow-trickle unary request body.
'Elixir.GRPC.Server.Adapters.Cowboy.Handler':read_full_body/3 (lib/grpc/server/adapters/cowboy/handler.ex) accumulates every received chunk into a single growing binary with no size cap. Additionally, when the client omits the grpc-timeout header, the per-chunk read timeout resolves to :infinity, allowing a slow-trickle client to keep the connection alive indefinitely while memory grows. A single connection is sufficient to exhaust server memory and crash the node.
This issue affects grpc: from 0.3.0-alpha.2 before 1.0.0.
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-48854 has been found in grpc.
Attackers can target a specific entry point like WINDOW_UPDATE over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade grpc to 1.0.0 or later.
If unsure, ask your IT team or search "grpc CVE-2026-48854" on the vendor's site.
CVE-2026-48854 (grpc) — CWE-770
Attack surface: WINDOW_UPDATE / grpc / END_STREAM
Patched: 1.0.0 — apply immediately
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-770) exists in grpc. Attackers reach the vulnerable code path via WINDOW_UPDATE.
Check the vendor advisory for the affected versions of grpc. Attack surface: WINDOW_UPDATE / grpc / END_STREAM.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.0.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'grpc' . 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' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
grpcを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade grpc to 1.0.0ステージング環境で 1.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- package hex.pm
- patch github.com
- web cna.erlef.org
- web osv.dev
- web github.com
- web github.com
- web github.com
- web github.com