CVE-2026-128131 is a vulnerability in AIOHTTP where decompressing payloads composed of many concatenated compressed streams (gzip, deflate, or zstd) causes excessive CPU usage due to quadratic time complexity. This can block the event loop of a server or client when processing specially crafted compressed request bodies or WebSocket messages.
CVE-2026-128129 is a vulnerability in AIOHTTP where data received during an upgrade request (such as a WebSocket handshake) is buffered without any size limit or flow control until the handler completes. This can lead to unbounded memory consumption if an attacker streams data behind the upgrade request to a handler that does not promptly accept or reject the upgrade.
AIOHTTP's WebSocket implementation contains an integer overflow vulnerability in the max_msg_size check, allowing an attacker to bypass message size limits and cause unbounded memory consumption by sending an oversized WebSocket message after a small fragment.
AIOHTTP's Request.post() method lacked a limit on the number of fields in a URL-encoded form body, causing insertion of many repeated keys into a MultiDict to take quadratic time on the event loop. This can allow an attacker to block the event loop by sending a form POST within the default client_max_size to any handler using Request.post(). A patch addressing this issue is available.
CVE-2026-128125 is a vulnerability in aiohttp's client CookieJar where unbounded cookie storage occurs due to improper parsing of Set-Cookie headers. This allows a malicious server to cause the client to store an excessive number of cookies, resulting in large Cookie headers and excessive memory and CPU usage on the client side.
AIOHTTP's Application.add_domain() method had a performance issue where using two or more wildcards in a domain mask caused polynomial-time matching on long Host headers, leading to event loop stalls. This vulnerability allows an attacker to stall the server by sending requests with long Host headers when multiple wildcards are used in domain masks. The recommended workaround is to limit domain masks to at most one wildcard. A patch addressing this issue is available.
A vulnerability in AIOHTTP's pure-Python HTTP parser causes the request buffer to grow excessively when an upgrade request is declined, leading to repeated processing of pipelined requests and excessive memory use. This affects users relying on the Python parser instead of the default C parser. The issue is fixed in versions after 0.9.3.
A vulnerability in aiohttp's multipart handling allows bypassing the client_max_size limit when processing parts with Content-Transfer-Encoding: base64. This can cause excessive memory consumption or event loop blocking due to unbounded reading of multipart data.
A vulnerability in AIOHTTP's WebSocket implementation allows attackers to bypass receive queue limits by sending many small or compressed messages. This can cause excessive memory consumption on the server or client side. The issue arises because the WebSocket reader continues parsing frames after the receive queue pauses the transport, and empty messages are not counted towards the queue size. With permessage-deflate compression, a single read can decompress many megabytes of data into the queue.
A vulnerability in mail-parser versions 10.4.2 up to but not including 10.5.0 causes the write_attachments() function to abort writing attachments after encountering a single malicious attachment, silently dropping subsequent attachments without error. This allows an attacker to evade detection by placing a poisoned attachment first, preventing later payloads from being extracted by downstream scanners while still delivering them intact to recipients. The issue arises from unguarded exceptions during filename sanitization and payload decoding. The flaw was fixed in version 10.5.0 by improving error handling, filename truncation, and decoding logic.
mail-parser versions from 3.7.0 up to 4.6.2 have a vulnerability where an out-of-range date in the Received email header causes an uncaught OverflowError or OSError. This exception occurs outside the mail-parser exception hierarchy, causing the entire message parsing to abort. The issue affects all parsing entry points and can be triggered by attacker-controlled headers, potentially causing message loss or batch processing failures. The flaw was fixed in version 4.6.3 by catching these exceptions and setting the problematic date to null, allowing parsing to continue.
The mail-parser library versions prior to 4.6.2 contain multiple issues related to handling of email headers from attacker-controlled input. These include uncaught exceptions caused by header names colliding with method names, silent loss or substitution of header values due to normalization and attribute lookup, and improper handling of 8-bit byte headers leading to serialization errors. These flaws can cause worker crashes or evasion of content detection without signaling defects. The issues were fixed in version 4.6.2 by changing header lookup to literal keys, proper initialization, and safer serialization.