Quick answers
- Is CVE-2026-111101 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111101 being exploited in the wild.
- How severe is CVE-2026-111101?
- Informational severity, published 26 October 2026.
- Which products and versions are affected?
- Mtrudel Bandit 0.1.0 before 1.14.0.
- Is there a fix for CVE-2026-111101?
- Yes: fixed in bandit 1.14.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-111101 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-111101?
- Check whether you run Mtrudel Bandit at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: bandit 1.14.0
Technical details
The HTTP/1.1 chunked body reader in lib/bandit/http1/socket.ex stores each chunk as a separate list cell and binary term without enforcing a limit on chunk count. The :length option of read_body/2 only measures payload bytes, allowing an attacker to send thousands of 1-byte chunks that consume far more memory than the data alone (48 MB of 1-byte chunks can grow a handler process to ~500 MB and consume ~6 seconds of CPU). On keep-alive connections, unread bodies are automatically drained through the same vulnerable reader, eliminating the need for the route to explicitly read the body.
Affected products
- mtrudel bandit 0.1.0 before 1.14.0
Timeline
- 2026-10-26: disclosed