CVE-2026-111101: mtrudel bandit · Unthrottled Resource Allocation
Affects mtrudel banditSource CVE Database V5
Not known to be exploited · CVSS 8.7 High : upgrade to 1.14.0 soon.
Data as of 26 Oct 2026, 16:53 UTC
- Patch
- Available – fixed in 1.14.0, 220b9dfd27f9a21305be2afc75cbe585ddc24e7a
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 26 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade bandit to 1.14.0; bandit to 220b9dfd27f9a21305be2afc75cbe585ddc24e7a.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| mtrudelbandit | Affected
| Fixed in
|
| banditmtrudel/bandit | Affected
| Fixed in
|
Hexbanditpkg:hex/banditOther threats | Affected
| Fixed in
|
CPE configurations (1)
cpe:2.3:a:mtrudel:bandit:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix for this vulnerability is available in mtrudel bandit version 1.14.0. Users should upgrade to version 1.14.0 or later to remediate this issue. No additional mitigation steps are indicated by the vendor advisory.
Description
Allocation of Resources Without Limits or Throttling vulnerability in the HTTP/1.1 chunked body reader of mtrudel bandit allows an unauthenticated remote attacker to exhaust server memory and CPU via a request body made of many 1-byte chunks. The chunked reader in lib/bandit/http1/socket.ex keeps every chunk as its own list cell and binary term until IO.iodata_to_binary/1 joins them, and nothing limits the number of chunks. The :length option of read_body/2 counts only data bytes, so tiny chunks cost far more memory than their payload: 48 MB of 1-byte chunks grew one handler process to about 500 MB and took about 6 s of CPU. The route does not need to read the body, because on keep-alive connections ensure_completed/1 drains unread bodies through the same reader. This issue affects bandit: from 0.1.0 before 1.14.0.
References
- github.com/mtrudel/bandit/security/advisories/GHSA-jwh3-j29h-qfmw (opens in a new tab)
- cna.erlef.org/cves/CVE-2026-111101.html (opens in a new tab)
- osv.dev/vulnerability/EEF-CVE-2026-111101 (opens in a new tab)
- github.com/mtrudel/bandit/commit/7201270c34b90f6c9e15c0386c2bb802c0c72ab4 (opens in a new tab)
- github.com/mtrudel/bandit/commit/220b9dfd27f9a21305be2afc75cbe585ddc24e7a (opens in a new tab)