Threat Advisory

Aiohttp Flaws Let Attackers Exhaust Memory And CPU

Threat: Vulnerability
Targeted Region: Global
Targeted Sector: Technology & IT
Criticality: High
[subscribe_to_unlock_form]

EXECUTIVE SUMMARY:

Multiple security vulnerabilities have been identified in aiohttp, affecting versions up to and including 3.14.3. The issues span WebSocket handling, request parsing, compression, form processing, cookie storage, and domain matching. They can allow remote attackers to cause excessive memory or CPU consumption, bypass size limits, or stall the event loop, creating a significant availability risk for applications that expose aiohttp endpoints.

CVE-2026-128132 (CVSS 3.0 — Low): The WebSocket receive queue limits could be bypassed by small or compressed messages, allowing a remote peer to cause excessive memory use in a server or client. The flaw affects the WebSocket reader and can be exploited by sending many small or compressed frames faster than the application consumes them.[/subscribe_to_unlock_form]

EXECUTIVE SUMMARY:

Multiple security vulnerabilities have been identified in aiohttp, affecting versions up to and including 3.14.3. The issues span WebSocket handling, request parsing, compression, form processing, cookie storage, and domain matching. They can allow remote attackers to cause excessive memory or CPU consumption, bypass size limits, or stall the event loop, creating a significant availability risk for applications that expose aiohttp endpoints.

CVE-2026-128132 (CVSS 3.0 — Low): The WebSocket receive queue limits could be bypassed by small or compressed messages, allowing a remote peer to cause excessive memory use in a server or client. The flaw affects the WebSocket reader and can be exploited by sending many small or compressed frames faster than the application consumes them.[emaillocker id="1283"]

CVE-2026-128131 (CVSS 3.0 — Low): Concatenated compressed streams could cause excessive CPU use because each compressed member was decoded inefficiently. A remote attacker could block the event loop with a crafted compressed request body or WebSocket message, or a malicious server could do the same to a client.

CVE-2026-128130 (CVSS 8.3 — High): The pure-Python request parser could replay already handled pipelined requests and grow internal buffers after an upgrade request was declined. A remote attacker could cause excessive memory use and repeated request processing in deployments using the pure-Python parser.

CVE-2026-128129 (CVSS 3.0 — Low): Data received while an upgrade request was being handled was buffered without size limits or flow control. A remote attacker could cause unbounded memory use by streaming data behind an upgrade request to a handler that does not immediately accept or reject it.

CVE-2026-128128 (CVSS 7.5 — High): The WebSocket message size limit could be bypassed through an integer overflow in the compiled reader. A remote attacker could stream an oversized WebSocket message after a small non-final fragment and cause unbounded memory use.

CVE-2026-128127 (CVSS 8.7 — High): Base64-encoded multipart parts could bypass the client size limit because chunk reading continued without a byte limit. A remote attacker could cause excessive memory use or block the event loop with a crafted multipart request to a handler that reads multipart data.

CVE-2026-128126 (CVSS 8.7 — High): URL-encoded form processing had no limit on the number of fields, and repeated keys could cause quadratic-time work on the event loop. A remote attacker could block the event loop with a form POST within normal size limits to a handler that parses form data.

CVE-2026-128125 (CVSS 6.3 — Medium): Cookie parsing and storage had no limit on the number of cookies, and unrecognised attributes could create additional cookies. A malicious server could cause excessive memory and CPU use in a client and make later requests build an excessively large cookie header.

CVE-2026-128124 (CVSS 3.0 — Low): Domain wildcard matching could stall the event loop when a host mask contained multiple wildcards and a long non-matching host header was supplied. A remote attacker could stall a server that registers such a domain mask by sending requests with a long host header.

These vulnerabilities collectively present a significant availability risk, particularly for network-facing aiohttp services that accept untrusted WebSocket, multipart, form, cookie, or host-header input. Operators of such services should prioritize exposure review and take appropriate actions to reduce the risk of denial of service.

RECOMMENDATION:

We recommend you to update aiohttp to version 3.14.4.

REFERENCES:

The following reports contain further technical details:

[/emaillocker]
crossmenu