Resource exhaustion in elixir-grpc grpc_server streaming requests
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- Present
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · None · High
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-770.
Summary
The elixir-grpc grpc_server package from 1.0.0 before 1.1.0 does not enforce its body size limit on streaming requests in time (CWE-770). Each stream buffers up to one full 8,000,000 byte read beyond max_body_size before the request is refused, and the gRPC length prefix is not checked first. An unauthenticated remote attacker can exhaust server memory by opening many concurrent client-streaming or bidirectional-streaming requests.
Written with Claude Haiku 5.5 from the sources below · 2026-11-13
Description from the CNA
Allocation of Resources Without Limits or Throttling vulnerability in elixir-grpc grpc_server allows unauthenticated attackers to exhaust server memory via client-streaming or bidirectional-streaming requests. The streaming read clause of GRPC.Server.Adapters.Cowboy.Handler.info/3 (grpc_server/lib/grpc/server/adapters/cowboy/handler.ex) asks Cowboy for up to 8,000,000 bytes per read and compares the running total with max_body_size only after the read returns. The gRPC length prefix of a message is not checked before the message is buffered. Each stream can therefore buffer up to one full read beyond the configured limit before it is refused, and many concurrent streams exhaust node memory. Releases before 1.0.6 apply no limit to streaming requests at all. This issue affects grpc_server: from 1.0.0 before 1.1.0.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| elixir-grpc | grpc_server | 1.0.0 to before 1.1.0 | 1.1.0 | Patch available | CNA |
- grpc_server Vendorelixir-grpc Affected 1.0.0 to before 1.1.0 Fixed in 1.1.0 Patch available CNA
CPE names CNA · 1
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:elixir-grpc:grpc_server:*:*:*:*:*:*:*:* | — | — | — |
- cpe:2.3:a:elixir-grpc:grpc_server:*:*:*:*:*:*:*:* Versions — — ·—
Remediation
Upgrade grpc_server to 1.1.0, the fixed version.
Written with Claude Haiku 5.5 from the sources below · 2026-11-13
- Fix · CNA grpc_server (elixir-grpc) Fixed in 1.1.0
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
elixir-grpc grpc_server 1.1.0
4 records Highest priority Priority LOW 4 LOW
Other records, highest priority first
- TI-2026-91650 Infinite loop in elixir-grpc grpc_server streaming RPCs exhausts CPUPriority LOW 37
- TI-2026-91649 Path bindings ignored for gRPC Content-Types in elixir-grpc grpc_serverPriority LOW 36
- TI-2026-91620 Refused calls stall HTTP/2 connections in elixir-grpc grpc_serverPriority LOW 28
Timeline
- 2026-11-13 Threatist record created from CVE-2026-124279
- 2026-11-13 CISA SSVC decision points changed
References
More elixir-grpc vulnerabilities
- TI-2026-36118 Remote code execution and denial of service via unsafe Erlang term deserialization in elixir-grpc/grpc CVSS 4.0CRITICAL 9.2
- TI-2026-38512 grpc gzip decompression bomb in GRPC.Compressor.Gzip.decompress/1 CVSS 4.0HIGH 8.7
- TI-2026-36119 Unbounded request body accumulation causes memory exhaustion in elixir-grpc/grpc CVSS 4.0HIGH 8.7
- TI-2026-86129 Unbounded request buffering in elixir-grpc grpc_server exhausts memory CVSS 4.0HIGH 8.2
- TI-2026-35955 Authorization bypass via path binding override in elixir-grpc/grpc HTTP transcoding CVSS 4.0HIGH 7.6
- TI-2026-91650 Infinite loop in elixir-grpc grpc_server streaming RPCs exhausts CPU CVSS 4.0HIGH 8.2
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences