Skip to content
Threat Brief

← All advisories

CVE-2026-111103

High 8.2No known exploitationFix available

HTTP/2 StreamError recovery rolls back connection state and bypasses per-connection limits in Bandit

Record last updated

CVSS score

8.2

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.6%

Higher than 51% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Weakness: CWE-460

Patching and mitigation

Patch status
Fix available (source: CVE record (EEF))
Fix documented (source date)
Mitigation
Disable HTTP/2 with http_2_options: [enabled: false], so that the vulnerable HTTP/2 handler never runs. Source (opens in a new tab)
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
mtrudelbanditfrom 1.9.0 before 1.14.01.14.0CVE Program
mtrudelbanditfrom 3ad49c80c268891e7cc412e69649115456638e59 before 220b9dfd27f9a21305be2afc75cbe585ddc24e7a220b9dfd27f9a21305be2afc75cbe585ddc24e7aCVE Program

Timeline

  1. Disclosure

    CVE record published by EEF

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (EEF)

    Source: CVE record (EEF) (opens in a new tab)

Vendor guidance and references