# CVE-2026-115269: HTTP/2 WINDOW_UPDATE and SETTINGS frames reset the request body read timeout in Bandit


- **Severity:** High 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`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** EEF-CVE-2026-115269, GHSA-p2qv-vx88-385x, UBUNTU-CVE-2026-115269

## What is CVE-2026-115269?

CVE-2026-115269 is a high-severity vulnerability in mtrudel bandit, published on 26 Oct 2026. 

### Official description

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.

Weakness: CWE-835 (Loop with Unreachable Exit Condition), CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-115269?

1 open source package ship an affected version, including bandit.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `bandit` | Hex | From 1.4.0 | 1.14.0 |

## How do I fix CVE-2026-115269?

Upgrade bandit to 1.14.0 or later.

## Is CVE-2026-115269 being exploited?

There is no known exploitation of CVE-2026-115269 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-115269 and fix it if it is affected.

What it is: CVE-2026-115269 is a high-severity vulnerability in mtrudel bandit, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115269 in the wild and no public exploit code.

Affected packages and fixed versions:
- bandit (Hex): affected from 1.4.0; fixed in 1.14.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-115269/ (Markdown: https://insights.sbomify.com/CVE-2026-115269/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-115269
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-115269
- OSV: https://osv.dev/vulnerability/CVE-2026-115269

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-115269/
Summaries are generated and may contain mistakes; the official description above is the record.