# CVE-2026-128128: AIOHTTP: WebSocket max_msg_size bypass via integer overflow


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 13 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-128128, ECHO-1820-153d-95aa, GHSA-3rp8-rxj8-mvjw, MINI-gc94-348p-r39h, MINI-qxpq-cj7r-7v9w, MINI-rgmr-m92w-rgwx, UBUNTU-CVE-2026-128128

## What is CVE-2026-128128?

CVE-2026-128128 is a high-severity vulnerability in aio-libs aiohttp, published on 13 Nov 2026. 

### Official description

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, the C WebSocket reader adds a declared frame length to the size of an already buffered partial message using signed 64-bit arithmetic. A length near two to the power of 63 can overflow, allowing the max_msg_size check to pass. A remote peer can send a small non-final fragment followed by an oversized message and cause unbounded memory consumption. The Python WebSocket reader is unaffected. This issue is fixed in version 3.14.4.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

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


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `aiohttp` | PyPI | `pkg:pypi/aiohttp` | All versions | 3.14.4 |

Status by vendor (upstream, then each distribution release and vendor build):

| Who | Release | Status | Packages | Fixed in |
| --- | --- | --- | --- | --- |
| Upstream |  | fixed | `aiohttp` | 3.14.4 |

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

Upgrade aiohttp to 3.14.4 or later.

## Is CVE-2026-128128 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-128128 is a high-severity vulnerability in aio-libs aiohttp, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-128128 in the wild and no public exploit code.

Affected packages and fixed versions:
- aiohttp (PyPI): affected all versions; fixed in 3.14.4

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-128128/ (Markdown: https://insights.sbomify.com/CVE-2026-128128/index.md)
```

## Sources

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

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