A vulnerability in mail-parser's get_server_ipaddress() function allowed sender IP address spoofing due to unreliable candidate address selection. This was fixed in version 4.6.2 by changing how candidate addresses are selected and improving IPv6 pattern matching. The function now returns None in cases where it previously returned unreliable addresses, requiring callers to handle this new behavior. No workarounds exist within mail-parser itself; callers unable to upgrade should rely on authenticated signals like MTA logs or SPF/DKIM/DMARC results for sender attribution.
mail-parser versions 3.8.0 through 4.5.0 contain a path traversal vulnerability in the write_attachments() and write_sample() APIs. Maliciously crafted email attachments with filenames containing directory traversal sequences or absolute paths could cause files to be written outside the intended directory, potentially overwriting arbitrary files depending on process permissions. The issue is fixed in version 10.4.2 by sanitizing filenames, validating output paths, rejecting symbolic links, and normalizing path separators.
Parsedmarc's mail-parser component contains two regular expressions used in email header parsing that exhibit polynomial-time backtracking on attacker-controlled input, causing severe CPU consumption and denial of service. These vulnerabilities affect common parsing functions without requiring special input structures. The issues impact all six address headers and the Received header clause splitter, allowing small crafted emails to exhaust parsing resources. The vulnerability has been fixed in version 4.6.1 with linear-time regex replacements and whitespace normalization.
CVE-2026-128132 is a vulnerability in AIOHTTP's WebSocket implementation where the receive queue limits can be bypassed by sending many small or compressed messages. This occurs because the WebSocket reader continues parsing frames after the receive queue has paused the transport, and empty messages are not counted towards the queue size. With permessage-deflate compression enabled, a single read of compressed frames can add large amounts of decompressed data to the queue, potentially causing excessive memory use.
CVE-2026-128131 is a high-severity vulnerability in aiohttp affecting parsedmarc versions >=8.11.0 <9.9.0 and >=9.11.0 <11.0.4. It arises from inefficient decompression of concatenated compressed streams (gzip, deflate, zstd), causing excessive CPU usage due to quadratic time complexity. This can be exploited by an attacker to block the event loop of a server or client using specially crafted compressed request bodies or WebSocket messages. A patch is available in versions 9.9.0 and 11.0.4.
CVE-2026-128130 is a high-severity vulnerability in the pure-Python HTTP parser used by AIOHTTP when the pipelined request queue is full. The flaw causes the parser to buffer unparsed data and re-feed it after an upgrade request is declined, leading to buffer growth and repeated processing of already-handled requests. This can result in excessive memory consumption and duplicate request handling. The issue affects versions >=8.11.0 <9.9.0 and >=9.11.0 <11.0.4 of the parsedmarc product. A patch is available in versions 9.9.0 and 11.0.4. Users relying on the pure-Python parser (e.g., with AIOHTTP_NO_EXTENSIONS set or without the standard wheel) are vulnerable. Switching to the default C parser mitigates the issue.
AIOHTTP versions >=8.11.0 <9.9.0 and >=9.11.0 <11.0.4 have a vulnerability where data received during an HTTP upgrade request (such as a WebSocket handshake) is buffered without limit until the handler completes. This can lead to unbounded memory consumption if an attacker streams large amounts of data behind the upgrade request.
AIOHTTP versions >=8.11.0 <9.9.0 and >=9.11.0 <11.0.4 contain a vulnerability in the WebSocket max_msg_size check due to an integer overflow in the C extension. This flaw allows an attacker to bypass the max_msg_size limit by sending a crafted WebSocket message with a declared length close to 2^63, causing unbounded memory usage. The issue is fixed in versions 9.9.0 and 11.0.4. A workaround is to disable the C extension by setting AIOHTTP_NO_EXTENSIONS=1, which uses the unaffected Python reader.
A vulnerability in aiohttp's multipart handling allows bypassing the client_max_size limit when processing parts with Content-Transfer-Encoding: base64. This causes the server to read excessive data into memory or block the event loop, potentially leading to denial of service.
AIOHTTP's Request.post() method had no limit on the number of URL-encoded form fields, causing insertion of many repeated keys into a MultiDict to take quadratic time on the event loop. This could allow an attacker to block the event loop by sending a form POST within the default client_max_size to any handler calling Request.post(). The vulnerability is fixed in versions 9.9.0 and 11.0.4.
CVE-2026-128125 is a vulnerability in aiohttp's client CookieJar where unbounded cookie storage occurs due to improper parsing of Set-Cookie headers. The client stores additional cookies from unrecognized name=value attributes without limits, allowing a malicious server to cause excessive memory and CPU usage and generate very large Cookie headers on subsequent requests.
AIOHTTP's Application.add_domain() method had a performance issue where domain masks with two or more wildcards caused polynomial-time matching delays on long Host headers. This could be exploited by attackers to stall the server event loop by sending requests with long Host headers that do not match the mask. The issue affects parsedmarc versions from 8.11.0 up to but not including 9.9.0 and from 9.11.0 up to but not including 11.0.4. A patch is available in versions 9.9.0 and 11.0.4 that fixes this vulnerability.