Answer in brief
CVE-2026-116078 records a High severity (CVSS 8.7) vulnerability in HTTP/2 request bodies made of 1-byte DATA frames amplify memory use in Bandit. The current sources do not mark it as known exploited. The current feed maps mtrudel/bandit (generic), mtrudel/mtrudel/bandit (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps mtrudel/bandit (generic), mtrudel/mtrudel/bandit (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| mtrudel/banditgeneric | >=0.3.1 <1.14.1 | 1.14.1 |
| mtrudel/mtrudel/banditgeneric | >=c8dc1e97050cf359f61ed6cdd110f3cdaf1d6f5f <327bb02ff84171237e1aeff787930debd16155ee | 327bb02ff84171237e1aeff787930debd16155ee |
Published upstream
Oct 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 28, 2026
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.
Quoted source text, attributed separately from HOL analysis.