Quick answers
- Is CVE-2026-105659 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105659 being exploited in the wild.
- How severe is CVE-2026-105659?
- Informational severity, published 14 October 2026.
- Which products and versions are affected?
- Mtrudel Bandit 1.4.0 before 1.13.0.
- Is there a fix for CVE-2026-105659?
- Yes: fixed in 1.13.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105659 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-105659?
- 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: 1.13.0
Technical details
The vulnerability exists in Bandit's HTTP/2 stream and connection window management. By sending periodic small WINDOW_UPDATE frames on stream 0 and manipulating SETTINGS_INITIAL_WINDOW_SIZE, an attacker can keep blocked streams alive with fresh deadlines, causing the server to accumulate stuck processes and hold their associated resources indefinitely. The attack has two independent paths: one at the connection level and one at the stream level, with the stream-level path remaining exploitable even if the connection-level issue is patched.
Affected products
- mtrudel bandit 1.4.0 before 1.13.0
Timeline
- 2026-10-14: disclosed