CVE-2026-121809
CPU exhaustion via a truncated gRPC message on streaming RPCs in elixir-grpc grpc_server
Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability in elixir-grpc grpc_server and grpc allows unauthenticated attackers to occupy a BEAM scheduler indefinitely via a client-streaming or bidirectional-streaming request whose body ends inside a gRPC message. GRPC.Server.Adapters.Cowboy.read_stream/1 (grpc_server/lib/grpc/server/adapters/cowboy.ex, and the Cowboy adapter in grpc before the package split) asks for more data whenever the buffer does not hold a complete message. Once the request body has ended, every further read returns an empty chunk, so the buffer never changes and the function retries without end. A single 5-byte length prefix sent with END_STREAM keeps one scheduler busy for as long as the connection stays open, and repeated requests exhaust all schedulers. This issue affects grpc_server: from 1.0.0 before 1.1.0; grpc: from 0.3.1 before 1.0.0.
Fixes and workarounds
Fix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: EEFAffected products and versions
| Product | Versions | Authority |
|---|---|---|
| grpc_server elixir-grpc grpc_server
hex |
≥ 1.0.0; < 1.1.0 (affected, semver)
Other versions: unaffected |
CNA: EEF |
| grpc_server elixir-grpc elixir-grpc/grpc
github |
≥ 0332faae5f5e132314794dbfdae5edecbccea292; < 38955f1392cbf08eef231a347348445410455c85 (affected, git)
Other versions: unaffected |
CNA: EEF |
| grpc elixir-grpc grpc
hex |
≥ 0.3.1; < 1.0.0 (affected, semver)
Other versions: unaffected |
CNA: EEF |
| grpc elixir-grpc elixir-grpc/grpc
github |
≥ 6d8a09ad919e208fb600538ac8b19bd733a04310; < 0332faae5f5e132314794dbfdae5edecbccea292 (affected, git)
Other versions: unaffected |
CNA: EEF |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 4.0 / 8.2 high |
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N | CNA: EEF |
| 4.0 / 8.2 high |
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X | NVD: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://github.com/elixir-grpc/grpc/security/advisories/GHSA-c2h9-f9cc-27xhCNA: EEF · vendor-advisory, related
- https://cna.erlef.org/cves/CVE-2026-121809.htmlCNA: EEF · related
- https://osv.dev/vulnerability/EEF-CVE-2026-121809CNA: EEF · related
- https://github.com/elixir-grpc/grpc/commit/0332faae5f5e132314794dbfdae5edecbccea292CNA: EEF · related
- https://github.com/elixir-grpc/grpc/commit/38955f1392cbf08eef231a347348445410455c85CNA: EEF · patch
- https://github.com/elixir-grpc/grpc/commit/6d8a09ad919e208fb600538ac8b19bd733a04310CNA: EEF · related
- https://cna.erlef.org/cves/CVE-2026-121809.html6b3ad84c-e1a6-4bf7-a703-f496b71e49db
- https://github.com/elixir-grpc/grpc/commit/0332faae5f5e132314794dbfdae5edecbccea2926b3ad84c-e1a6-4bf7-a703-f496b71e49db
- https://github.com/elixir-grpc/grpc/commit/38955f1392cbf08eef231a347348445410455c856b3ad84c-e1a6-4bf7-a703-f496b71e49db
- https://github.com/elixir-grpc/grpc/commit/6d8a09ad919e208fb600538ac8b19bd733a043106b3ad84c-e1a6-4bf7-a703-f496b71e49db
- https://github.com/elixir-grpc/grpc/security/advisories/GHSA-c2h9-f9cc-27xh6b3ad84c-e1a6-4bf7-a703-f496b71e49db
- https://osv.dev/vulnerability/EEF-CVE-2026-1218096b3ad84c-e1a6-4bf7-a703-f496b71e49db
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.