Back to CVE records
High 8.7Published Jun 15, 2026

CVE-2026-48854Unbounded request body accumulation causes memory exhaustion in elixir-grpc/grpc

Updated under an hour ago ()

Does this affect you?

It affects elixir-grpc grpc. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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.

CVSS
8.7 HIGH (v4.0, CNA)CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Weakness (CWE)
CWE-770
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
EEF
NVD analysis
Deferred
Record last updated
Sep 24, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
elixir-grpc grpc
elixir-grpc:grpc
from 0.3.0-alpha.2 before 1.0.0
CNA record

References

  • vendor-advisory, related
  • related
  • related
  • related
  • patch

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.