AIOHTTP versions from 3.4.2 up to but not including 3.10.0 contain a vulnerability in the WebSocket reader where an integer overflow in the max_msg_size check allows an attacker to bypass message size limits. This can lead to unbounded memory consumption by sending an oversized WebSocket message after a small non-final fragment. The issue is fixed in version 3.10.0. A workaround is to disable C extensions by setting AIOHTTP_NO_EXTENSIONS=1 to use the unaffected Python reader.
AIOHTTP versions from 3.4.2 up to but not including 3.10.0 contain a vulnerability in multipart handling where base64-encoded parts can bypass the client_max_size limit. This occurs because the BodyPartReader.read_chunk() method reads until the chunk length is a multiple of 4 without enforcing size limits, potentially causing excessive memory consumption or event loop blocking. The issue is fixed in version 3.10.0.
AIOHTTP versions from 3.4.2 up to but not including 3.10.0 have a vulnerability where the Request.post() method does not limit the number of URL-encoded form fields. This can cause the event loop to be blocked due to quadratic time processing when many repeated keys are inserted. The issue is fixed in version 3.10.0.
A vulnerability in aiohttp's Application.add_domain() method causes the event loop to stall when matching host masks containing two or more wildcards against long Host headers. This results in polynomial-time processing that can be exploited to stall the server. The issue affects versions from 3.4.2 up to but not including 3.10.0. A patch is available in version 3.10.0. As a workaround, limiting domain masks to at most one wildcard reduces risk.
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 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.
AIOHTTP versions from 2.0.10 up to but not including 3.67.1_18 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. The issue is fixed in version 3.67.1_18.
This High severity Improper Authorization vulnerability was introduced in versions 5.12.0, 10.3.0, and 11.3.0 of Jira Service Management Data Center. This Improper Authorization vulnerability, with a CVSS Score of 7.1, allows an authenticated attacker to gain unintended access and can lead to the exposure of resources or functionality, possibly providing attackers with sensitive information or even execute arbitrary code. Atlassian recommends that Jira Service Management Data Center customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions: Jira Service Management Data Center 10.3: Upgrade to a release greater than or equal to 10.3.27 Jira Service Management Data Center 11.3: Upgrade to a release greater than or equal to 11.3.13 See the release notes (https://confluence.atlassian.com/servicemanagement/jira-service-management-release-notes-780083086.html). You can download the latest version of Jira Service Management Data Center from the download center (https://www.atlassian.com/software/jira/service-management/download-archives). This vulnerability was reported via our Bug Bounty program.
crypton-x509-validation versions from 1.6.12 up to but not including 1.10.2 improperly validate IP addresses in certificates by ignoring the iPAddress subjectAltName (SAN) when no dNSName SAN is present. This causes clients to accept certificates with a commonName (CN) matching the target IP but an iPAddress SAN pointing elsewhere, violating expected SAN precedence rules. The flaw allows impersonation if a trusted CA issues such a certificate, typically possible only with private or enterprise CAs. The issue is fixed in version 1.10.2.
JuicyPixels versions from 3.1.3 up to but not including 3.3.10 contain out-of-bounds write vulnerabilities in BMP RLE and TIFF strip decoding. These flaws allow heap memory corruption via crafted image files, potentially leading to crashes or remote code execution under certain conditions. The issue is fixed in version 3.3.10.
A vulnerability in OpenSSL's QUIC server implementation allows a remote client to cause unbounded memory growth by repeatedly opening and resetting streams. This occurs because the server retains stream state for rejected streams if the peer resets the stream before the rejection is signaled, preventing proper cleanup. The issue leads to a denial of service by exhausting server memory over time. The severity is rated high due to the potential for service disruption, though the memory growth is slow and requires a long-lived connection.
A use-after-free vulnerability exists in OpenSSL's PEM_X509_INFO_read_bio_ex() and related functions when an application passes an existing stack to add entries. If reading PEM data fails, the function frees all entries in the stack but leaves dangling pointers, potentially causing crashes or memory corruption if the application continues to use the stack. This affects only applications that pass a non-NULL stack, which OpenSSL itself does not do. The vulnerability is triggered by malformed PEM data causing read failure.
A vulnerability in OpenSSL occurs when a server is configured with the Suite B certificate flag via SSL_CTX_set_cert_flags() and TLS 1.3 is enabled. The server may read past the end of a fixed group list during ClientHello processing if the client's supported_groups and key_share contain no Suite B group. This out-of-bounds read does not disclose memory but can cause a denial of service on builds with sanitizers or hardened allocators.
CVE-2026-128132 is a high-severity vulnerability in AIOHTTP's WebSocket implementation where the receive queue limits can be bypassed by sending many small or compressed messages. This flaw allows an attacker to cause excessive memory consumption by overwhelming the WebSocket server or client with messages faster than they can be processed. The issue arises because empty messages are not counted towards the queue size, and with permessage-deflate compression, a single read can decompress to many megabytes of data. A fix is available in version 26.10.1.
AIOHTTP versions from 19.10b0_3 up to but not including 26.10.1 contain a vulnerability where decompressing concatenated compressed streams (gzip, deflate, or zstd) causes excessive CPU usage due to quadratic time complexity. This can block the event loop on servers or clients when processing specially crafted compressed payloads. The issue is fixed in version 26.10.1.
A vulnerability in AIOHTTP's pure-Python HTTP request parser causes buffer growth and replay of pipelined requests after a declined upgrade request. This affects users relying on the Python parser instead of the default C parser. An attacker can exploit this to cause excessive memory consumption and multiple processing of the same requests. The issue is fixed in version 26.10.1.