Skip to content
Threat Brief

← All advisories

CVE-2026-116078

High 8.7No known exploitationFix available

HTTP/2 request bodies made of 1-byte DATA frames amplify memory use in Bandit

Record last updated

CVSS score

8.7

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.5%

Higher than 43% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Weakness: CWE-770

Patching and mitigation

Patch status
Fix available (source: CVE record (EEF))
Fix documented (source date)
Mitigation
From 0.7.0, disable HTTP/2 with http_2_options: [enabled: false], so that the vulnerable body reader never runs. Source (opens in a new tab)
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
mtrudelbanditfrom 0.3.1 before 1.14.11.14.1CVE Program
mtrudelbanditfrom c8dc1e97050cf359f61ed6cdd110f3cdaf1d6f5f before 327bb02ff84171237e1aeff787930debd16155ee327bb02ff84171237e1aeff787930debd16155eeCVE Program

Timeline

  1. Disclosure

    CVE record published by EEF

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (EEF)

    Source: CVE record (EEF) (opens in a new tab)

Vendor guidance and references