Allocation of Resources Without Limits or Throttling vulnerability in the HTTP/2 request body…

Why it is Yellow

• CVSS 8.7 high
• Remotely exploitable without logging in

References

• https://cna.erlef.org/cves/CVE-2026-116078.html
• https://github.com/mtrudel/bandit/commit/327bb02ff84171237e1aeff787930debd16155ee
• https://github.com/mtrudel/bandit/commit/c8dc1e97050cf359f61ed6cdd110f3cdaf1d6f5f
• https://github.com/mtrudel/bandit/security/advisories/GHSA-pxjf-g536-7r93
• https://osv.dev/vulnerability/EEF-CVE-2026-116078

Original description

Allocation of Resources Without Limits or Throttling vulnerability in the HTTP/2 request body reader of mtrudel bandit allows an unauthenticated remote attacker to exhaust server memory via a request body sent as many 1-byte DATA frames. do_read_data/5 in lib/bandit/http2/stream.ex keeps every DATA frame payload as its own list element until the read returns. The :length option of read_body/2 counts body bytes, not frames, so a body of 1-byte frames costs a list cell and a binary term per byte. Interleaving the frames across up to 500 concurrent streams per connection keeps each stream consuming its frames as they arrive; in the reporter's test, 100 streams held 25 to 40 MiB of stream process memory for 5 MB sent. Only routes whose Plug reads the request body are affected, which includes any route behind Plug.Parsers. This issue affects bandit: from 0.3.1 before 1.14.1.