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.
A vulnerability in aiohttp's WebSocket implementation allows attackers to bypass receive queue limits by sending many small or compressed messages. This causes excessive memory consumption due to the WebSocket reader continuing to parse frames after the receive queue has paused the transport, and empty messages not being counted towards the queue size. The issue is fixed in version 0.5.0_4.
AIOHTTP versions from 0.2.0 up to but not including 0.5.0_4 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 of servers or clients when processing specially crafted compressed payloads. The issue is fixed in version 0.5.0_4.
CVE-2026-128130 is a vulnerability in aiohttp's pure-Python HTTP parser where, under certain conditions, the request buffer grows uncontrollably and previously handled pipelined requests are replayed to the application. This occurs when the pipelined request queue is full and an upgrade request is declined, causing excessive memory use and duplicate request processing. The issue affects aiohttp versions from 0.2.0 up to but not including 0.5.0_4. A patch is available in version 0.5.0_4. Users relying on the pure-Python parser (e.g., with AIOHTTP_NO_EXTENSIONS) are vulnerable, while switching to the default C parser mitigates the issue.
AIOHTTP versions from 0.2.0 up to but not including 0.5.0_4 have a vulnerability where data received during an upgrade request (such as a WebSocket handshake) is buffered without limit until the handler finishes. 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. A patch fixing this issue is available in version 0.5.0_4.
A vulnerability in AIOHTTP's WebSocket implementation allows bypassing the max_msg_size limit due to an integer overflow in the C extension's 64-bit arithmetic. This flaw permits an attacker to send an oversized WebSocket message after a small non-final fragment, causing unbounded memory consumption. The issue affects versions from 0.2.0 up to but not including 0.5.0_4. A fix is available in version 0.5.0_4. As a workaround, disabling C extensions by setting AIOHTTP_NO_EXTENSIONS=1 uses the unaffected Python reader.
AIOHTTP versions >=0.2.0 and <0.5.0_4 have a vulnerability in multipart handling where base64-encoded parts can bypass the client_max_size limit. This occurs because the multipart reader reads chunks until their length is a multiple of 4 without enforcing size limits, allowing excessive memory use or event loop blocking. The issue is fixed in version 0.5.0_4.
AIOHTTP's Request.post() method lacked a 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 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(). The vulnerability is fixed in version 0.5.0_4.
AIOHTTP's client CookieJar component improperly handled Set-Cookie headers by creating extra cookies from unrecognized name=value attributes and lacked limits on cookie storage. This allowed a malicious server to cause the client to store an excessive number of cookies, leading to very large Cookie headers and excessive memory and CPU usage, especially on repeated redirects. This vulnerability was fixed in version 0.5.0_4.
A vulnerability in aiohttp's Application.add_domain() method causes event loop stalls when matching host masks with 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 0.2.0 up to but not including 0.5.0_4. A patch is available in version 0.5.0_4. As a workaround, limiting domain masks to at most one wildcard reduces the risk.
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.