NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · PyPI

CVE-2026-128129: AIOHTTP: Unbounded buffering of data received during an upgrade request

highCVSS 4.0 8.2GHSA-pw86-h8fm-j323

aiohttp up to 3.14.3 buffers without limit any data a client sends behind an upgrade request, such as a WebSocket handshake, while the handler is still running. A remote attacker can use this to exhaust server memory. Upgrade the pip package aiohttp to 3.14.4.

Published Nov 16, 2026 · Analysis Nov 16, 2026

What an attacker can do

When aiohttp's server receives a request flagged as an upgrade, for example a WebSocket handshake, it keeps reading from the connection. Everything the client sends after the request goes into a buffer. The buffer has no size limit and no flow control, and it stays that way until the handler completes (CWE-770).

An attacker connects, sends an upgrade request, and then streams data. Memory grows for as long as the handler has not accepted or rejected the upgrade. The advisory says this affects any handler that does not immediately accept or reject the upgrade. A handler that awaits a database call, an auth check or another slow step before calling WebSocketResponse.prepare() gives the attacker a long window. Several such connections in parallel can push the process into an out-of-memory kill.

No authentication is needed and the attack is network-reachable. The result is loss of availability, not data exposure. The CVSS vector marks attack requirements as present (AT:P), which fits the need for a handler that delays its answer.

Who is affected

The pip package aiohttp at version 3.14.3 or earlier is affected. This matters for aiohttp used as a server, especially apps with WebSocket endpoints or other handlers that see upgrade requests. Check your installed version:

pip show aiohttp

Also check lock files and container images, since aiohttp is often pulled in as a transitive dependency.

aiohttp

Ecosystem
PyPI
Affected
<= 3.14.3
Fixed in
3.14.4
Check
pip show aiohttp

How to fix it

Upgrade to aiohttp 3.14.4:

pip install --upgrade "aiohttp>=3.14.4"

The fix is in pull request 13501, titled "Fix limit on message tail", and is backported to the 3.14 line. The advisory lists no workaround. Until you upgrade, a reverse proxy that limits request body and connection duration in front of the app reduces the window, but that is general hardening, not vendor guidance. Quick answers in WebSocket handlers also shorten the exposure.

How to tell if you were hit

The sources give no log signature. Watch for aiohttp worker processes whose memory climbs steadily while a few connections stay open, and for OOM kills of the service. In access logs, look for upgrade requests (Upgrade: websocket) from one address that stay open for a long time with large inbound byte counts.

Original advisory

From the GitHub Advisory Database (CC BY 4.0).

Summary

While a request flagged as an upgrade (e.g. a WebSocket handshake) was being handled, all further data received on the connection was buffered with no size limit or flow control until the handler completed.

Impact

An attacker could cause unbounded memory use by streaming data behind an upgrade request to any handler that does not immediately accept or reject the upgrade.

---

Patch: https://github.com/aio-libs/aiohttp/commit/3d850ee9b92573c7e913821cbcb96005beb3f4df

Credited to axel-mierczuk-1pw, Dreamsorcerer.

Questions

Which aiohttp version fixes CVE-2026-128129?

aiohttp 3.14.4. The affected range in the advisory is 3.14.3 and earlier. Upgrade with pip and rebuild any container image that pins an older version.

Do I need WebSocket endpoints to be affected?

The advisory says the flaw hits any handler that does not immediately accept or reject an upgrade request. WebSocket handshakes are the example it gives. Plain HTTP handlers that never see upgrade requests are not the described path.

Does the attacker need credentials?

No. The CVSS vector needs no privileges and no user interaction. The attacker only needs network access to the aiohttp server and a handler that is slow to answer the upgrade.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology

More PyPI vulnerabilities

All PyPI entries