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

CVE-2026-128130: AIOHTTP: Pure-Python parser request replay and buffer growth behind a declined upgrade

highCVSS 4.0 8.3 · 3.1 8.2GHSA-28qf-cpwq-vmc2

aiohttp's pure-Python HTTP parser mishandles pipelined requests behind a declined upgrade. Memory grows with each handled request, and requests that were already handled are dispatched to the application again. Only servers that use the Python parser are affected. Upgrade aiohttp to 3.14.4, or switch to the default C parser.

Published Nov 16, 2026 · Analysis Nov 16, 2026

What an attacker can do

When the queue of pipelined requests was full, the pure-Python parser kept the unparsed remainder in an internal buffer and also returned it to the caller. After a handler declined an upgrade request, that buffered data was fed to the parser again. The buffer therefore grew with every request handled, and requests that had been answered were dispatched to the application a second time (CWE-770, CWE-835).

An attacker sends many pipelined requests on one connection, starting with an upgrade request that the handler declines. Two effects follow. Server memory use climbs, which can end in an out-of-memory kill. Requests are also replayed: if a pipelined request changes state, such as a POST that creates an order or a payment call, the application may run it more than once. That is why the CVSS vector scores limited integrity impact next to high availability impact.

No authentication is needed. Most deployments are not exposed, because the standard wheels ship the C parser. You are exposed only if AIOHTTP_NO_EXTENSIONS is set, or if aiohttp was installed without compiled extensions, for example on an unsupported platform or from source without a build step.

Who is affected

aiohttp 3.14.3 and earlier, and only when the pure-Python parser is in use. That happens when AIOHTTP_NO_EXTENSIONS is set in the environment, or when no compiled wheel was installed. Check the version and whether the environment variable is set:

pip show aiohttp

Then look for AIOHTTP_NO_EXTENSIONS in your Dockerfiles, service units and CI settings.

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 13356, listed in the 3.14.4 release notes. The advisory's workaround is to switch to the default C parser: unset AIOHTTP_NO_EXTENSIONS and install a standard wheel so the compiled extensions load.

How to tell if you were hit

The advisory gives no log signature. Look for aiohttp processes whose memory grows with long-lived connections that carry many pipelined requests. Check application logs for the same request ID, order or transaction handled twice close together. Also search deployments for AIOHTTP_NO_EXTENSIONS to find the servers where the flaw can occur at all.

Original advisory

From the GitHub Advisory Database (CC BY 4.0).

Summary

When the pipelined request queue was full, the pure-Python parser stored the unparsed remainder internally and also returned it to the caller. After a handler declined an upgrade request, the buffered data was re-fed, so the buffer grew with each handled request and already-handled requests were dispatched to the application again.

Impact

If users are using the Python parser (AIOHTTP_NO_EXTENSIONS, or not a standard wheel installed), an attacker could cause excessive memory use and cause pipelined requests to be processed more than once.

Workaround

Switch to the default C parser.

---

Patch: https://github.com/aio-libs/aiohttp/commit/47babd8c23ca79e2bae6cc8dcb5752b61e369fc7

Credited to axel-mierczuk-1pw, rodrigobnogueira, Dreamsorcerer.

Questions

Am I affected if I installed aiohttp from a normal wheel?

Normally not. The flaw is in the pure-Python parser, and standard wheels use the C parser by default. You are affected if AIOHTTP_NO_EXTENSIONS is set or the compiled extensions are missing.

What is the quickest mitigation for CVE-2026-128130?

Switch to the default C parser, as the advisory says. The full fix is aiohttp 3.14.4, which is the patched version in the advisory.

Can a request really run twice?

Yes, per the advisory. Pipelined requests that had already been handled were dispatched to the application again after a declined upgrade. Non-idempotent handlers are the concern.

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