Allocation of Resources Without Limits or Throttling Affecting bandit package, versions >=0.3.1 <1.14.1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-HEX-BANDIT-22149921
- published3 Nov 2026
- disclosed28 Oct 2026
- creditneilberkman
Introduced: 28 Oct 2026
NewCVE-2026-116078 (opens in a new tab)How to fix?
Upgrade bandit to version 1.14.1 or higher.
Overview
bandit is a HTTP server for Plug and WebSock apps.
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in the HTTP/2 request body reader of mtrudel bandit, an unauthenticated remote attacker can 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.