Quick answers
- Is CVE-2026-108529 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-108529 being exploited in the wild.
- How severe is CVE-2026-108529?
- Informational severity, published 26 October 2026.
- Which products and versions are affected?
- Mtrudel Bandit 0.3.4 to before 1.14.0.
- Is there a fix for CVE-2026-108529?
- 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-108529 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-108529?
- 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
The HTTP/2 implementation in do_pending_sends/2 uses List.delete/2 to remove queued sends before each retry, resulting in O(n²) complexity for n blocked streams. An attacker can create thousands of streams blocked on the connection send window, then send cheap SETTINGS or WINDOW_UPDATE frames that cause the server to walk the entire queue. The issue exists because max_concurrent_streams defaults to infinity, allowing an attacker to choose the number of blocked streams.
Affected products
- mtrudel bandit 0.3.4 to before 1.14.0
Timeline
- 2026-10-26: disclosed: CVE-2026-108529 published