CVE-2026-111101
HIGHDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v4 Vector
Exploitability
Impact
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Exploit Intelligence
Moderate risk: more likely to be exploited than 49% of all known CVEs.
References
Related Vulnerabilities
Other CWE-770 (Allocation of Resources Without Limits or Throttling) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2023-50387 | High | 7.5 | 100% | - | Fix |
| CVE-2019-11478 | Medium | 5.3 | 95% | - | Fix |
| CVE-2019-11479 | High | 7.5 | 92% | - | Fix |
| CVE-2024-27316 | High | 7.5 | 91% | - | Fix |
| CVE-2022-30522 | High | 7.5 | 90% | - | Fix |
| CVE-2019-9515 | High | 7.5 | 87% | - | Fix |
Common questions
How do I fix CVE-2026-111101?
No published fix for CVE-2026-111101 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-111101 being actively exploited?
Not that we know of. CVE-2026-111101 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.60% is the estimated probability that it will be exploited in the next 30 days. That is higher than 49% of all scored CVEs.
How severe is CVE-2026-111101?
CVE-2026-111101 has a CVSS v4 base score of 8.7, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-111101
Markdown
[](https://tridentstack.com/cve/CVE-2026-111101)HTML
<a href="https://tridentstack.com/cve/CVE-2026-111101"><img src="https://tridentstack.com/cve/badge/CVE-2026-111101.svg" alt="CVE-2026-111101"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-26.