Is CVE-2026-111103 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-111103 being exploited in the wild.

How severe is CVE-2026-111103?

Informational severity, published 26 October 2026.

Which products and versions are affected?

Mtrudel Bandit 1.9.0 before 1.14.0.

Is there a fix for CVE-2026-111103?

Yes: fixed in bandit 1.14.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-111103 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-111103?

Check whether you run Mtrudel Bandit at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-111103: mtrudel bandit HTTP/2 handler resource limit bypass

CVE-2026-111103 · Severity: info · Published 2026-10-26

Bandit, an Elixir HTTP/2 server library, contains a flaw in its HTTP/2 frame handler that allows remote attackers to bypass per-connection resource limits without authentication. An attacker can send specially crafted TCP packets containing multiple frames that exceed the configured concurrent stream limits, potentially running many more server processes simultaneously than allowed and leading to resource exhaustion or denial of service.

Technologies: Mtrudel Bandit. Vendors: Mtrudel.

Quick answers

Is CVE-2026-111103 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-111103 being exploited in the wild.
How severe is CVE-2026-111103?: Informational severity, published 26 October 2026.
Which products and versions are affected?: Mtrudel Bandit 1.9.0 before 1.14.0.
Is there a fix for CVE-2026-111103?: Yes: fixed in bandit 1.14.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-111103 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-111103?: Check whether you run Mtrudel Bandit at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: bandit 1.14.0

Technical details

When a StreamError occurs partway through processing a chunk of HTTP/2 frames, the handler sends RST_STREAM but rolls back connection state (stream counts, timestamps, HPACK decoder) while leaving already-spawned streams running. This causes resource accounting to lose track of streams, allowing an attacker to exceed max_concurrent_streams and max_requests limits by packing multiple HEADERS frames into single TCP writes. The vulnerability is a state-management bug in Bandit.HTTP2.Handler.handle_data/3.

Affected products

mtrudel bandit 1.9.0 before 1.14.0

Timeline

2026-10-26: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.