CVE-2026-115269 json
HTTP/2 WINDOW_UPDATE and SETTINGS frames reset the request body read timeout in Bandit
published 14d ago modified 14d ago also EEF-CVE-2026-115269 , EUVD-2026-109819 , GHSA-p2qv-vx88-385x
- cvss
- 8.7
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 49%
- public exploits
- 0
- none known
Summary
Allocation of Resources Without Limits or Throttling vulnerability in the HTTP/2 request body reader of mtrudel bandit allows an unauthenticated remote attacker to hold stream processes open indefinitely via WINDOW_UPDATE or empty SETTINGS frames sent while a Plug reads the request body.
Bandit.HTTP2.Stream.do_read_data/4 in lib/bandit/http2/stream.ex waits for each frame with a fresh read_timeout. A stream WINDOW_UPDATE, or the zero-delta window update that every empty SETTINGS frame delivers to all streams, ends the wait without delivering any body data, and the loop starts a new full countdown. A client that sends one of these 9-byte frames before each countdown expires keeps read_body blocked, together with the stream process and whatever the application holds while reading, for as long as it likes.
This issue affects bandit: from 1.4.0 before 1.14.0.
Patch / fix
- hex bandit 1.14.0
- mtrudel bandit 1.14.0
Is CVE-2026-115269 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 14d ago
Exploit prediction
0.60% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.7 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
| CNA | 4.0 | 8.7 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| hex | bandit | >=1.4.0, <1.14.0 |
1.14.0 |
Affected products
- mtrudel bandit
Classification
References
-
github.com
/mtrudel/bandit/commit/fff06efe3be962b484bd4d3eb339372fda5a231f
related, web
-
github.com
/mtrudel/bandit/commit/220b9dfd27f9a21305be2afc75cbe585ddc24e7a
patch
-
github.com
/mtrudel/bandit/security/advisories/GHSA-p2qv-vx88-385x
vendor-advisory, related, advisory
-
cna.erlef.org
/cves/CVE-2026-115269.html
related, web
-
osv.dev
/vulnerability/EEF-CVE-2026-115269
related
-
hex.pm
/packages/bandit
package
Sources
- CVE List CVE-2026-115269
- NVD CVE-2026-115269
- OSV EEF-CVE-2026-115269
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.