CVE-2026-124279 json
Streaming request body limit enforced only after an 8 MB read in elixir-grpc grpc_server
published yesterday modified yesterday also EEF-CVE-2026-124279 , EUVD-2026-125543 , GHSA-736x-r87j-jhcm
- cvss
- 8.2
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 42%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- hex grpc_server 1.1.0
- elixir-grpc grpc_server 1.1.0
Is CVE-2026-124279 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- yesterday
Exploit prediction
0.49% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-14).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.2 | 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 | 4.0 | 8.2 | 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 |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| hex | grpc_server | >=1.0.0, <1.1.0 |
1.1.0 |
Affected products
- elixir-grpc grpc_server
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
References
-
github.com
/elixir-grpc/grpc/commit/49e18c3ec6bb9afe2f712caad3dbab5c56a68a00
related, web
-
github.com
/elixir-grpc/grpc/commit/b1e771d558941b1ed4b6de8b39f6a5375543db01
patch
-
github.com
/elixir-grpc/grpc/security/advisories/GHSA-736x-r87j-jhcm
vendor-advisory, related, advisory
-
cna.erlef.org
/cves/CVE-2026-124279.html
related, web
-
osv.dev
/vulnerability/EEF-CVE-2026-124279
related
-
hex.pm
/packages/grpc_server
package
Sources
- CVE List CVE-2026-124279
- NVD CVE-2026-124279
- OSV EEF-CVE-2026-124279
- Maintainer advisory GHSA-736x-r87j-jhcm
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of elixir-grpc/grpc published their own advisory on GitHub. Reviewed sources take precedence over it.