Quick answers
- Is CVE-2026-108525 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-108525 being exploited in the wild.
- How severe is CVE-2026-108525?
- Informational severity, published 26 October 2026.
- Which products and versions are affected?
- Mtrudel Bandit 0.3.1 before 1.14.0.
- Is there a fix for CVE-2026-108525?
- 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-108525 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-108525?
- 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 vulnerability exists in HTTP/2 flow-control implementation: handle_frame/3 forwards DATA frames to stream processes without validating the receive window, and compute_recv_window/2 replenishes the window upon arrival rather than consumption and never sends FLOW_CONTROL_ERROR on violations. An attacker requests a response larger than the 65,535-byte initial window, withholds WINDOW_UPDATE frames, then floods small DATA frames on the blocked stream; each frame queues in the stream mailbox until memory exhaustion.
Affected products
- mtrudel bandit 0.3.1 before 1.14.0
Timeline
- 2026-10-26: disclosed