A vulnerability in AIOHTTP's pure-Python HTTP parser causes the request buffer to grow excessively when an upgrade request is declined. This leads to repeated processing of pipelined requests and excessive memory consumption. The issue affects versions from 2.0.5 up to but not including 2.2.0. A fix is available in version 2.2.0.
CVE-2026-128129 is a high-severity vulnerability in the AIOHTTP library affecting versions >=2.0.5 and <2.2.0. It involves unbounded buffering of data received during an HTTP upgrade request, such as a WebSocket handshake, where all subsequent data is buffered without size limits or flow control until the upgrade handler completes. This can lead to unbounded memory consumption if an attacker streams large amounts of 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 2.2.0.
AIOHTTP versions 2.0.5 up to but not including 2.2.0 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 maximum message size limit by sending a crafted WebSocket message with a declared frame length near 2^63, causing unbounded memory consumption. The issue is fixed in version 2.2.0. A workaround is to disable C extensions 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 can lead to excessive memory consumption or event loop blocking when a specially crafted multipart request is sent to a handler reading multipart data. The issue affects versions from 2.0.5 up to but not including 2.2.0 and has been fixed in version 2.2.0.
CVE-2026-128126 is a high-severity vulnerability in aiohttp's Request.post() method where no limit was imposed on the number of URL-encoded form fields. This allowed an attacker to send a form POST with many repeated keys, causing quadratic time complexity in processing and blocking the event loop. The issue affects versions >=2.0.5 and <2.2.0 and was fixed in version 2.2.0.
CVE-2026-128125 is a vulnerability in the aiohttp client CookieJar where unbounded cookie storage occurs due to improper parsing of Set-Cookie headers. This flaw allows a malicious server to cause the client to store an excessive number of cookies, leading to large Cookie headers and excessive memory and CPU usage on the client side. The issue affects versions >=2.0.5 and <2.2.0 of the affected product. A fix is available in version 2.2.0.
CVE-2026-128124 is a high-severity vulnerability in the Application.add_domain() function of the streamrip product, affecting versions from 2.0.5 up to but not including 2.2.0. The vulnerability arises from the way wildcard characters (*) in domain masks are compiled for matching Host headers, causing polynomial-time event loop stalls when multiple wildcards are used and a long Host header is processed. This can be exploited by an attacker to stall the server. A patch fixing this issue is available in version 2.2.0. As a workaround, limiting domain masks to at most one wildcard character can mitigate the issue.
This security update for QEMU addresses multiple vulnerabilities including CVE-2026-17588, CVE-2026-81627, and CVE-2026-93834. The issues involve unguarded timer callbacks leading to memory corruption, missing validation allowing privileged guest users to inject code into System Management Mode memory, and unsafe mutation of file identifier paths from multiple threads. The update also fixes various non-security bugs and improves stability. The update is provided in QEMU stable release 11.0.5.
AIOHTTP versions from 3.13.0 up to but not including 5.45.0 contain a vulnerability in the WebSocket receive queue handling. The WebSocket reader continues parsing frames after the receive queue pauses the transport, and empty messages are not counted towards the queue size. When permessage-deflate compression is used, a single read of compressed frames can cause many megabytes of decompressed messages to accumulate in the queue. This can lead to excessive memory consumption on the server or client side.
AIOHTTP versions from 3.13.0 up to but not including 5.45.0 are vulnerable to excessive CPU consumption when decompressing payloads containing many concatenated compressed streams (gzip, deflate, or zstd). This occurs because each compressed member is decompressed by passing the entire remaining input to a new decompressor, causing quadratic CPU time. An attacker can exploit this to block the event loop of a server or client using specially crafted compressed request bodies or WebSocket messages. The issue is fixed in version 5.45.0.
The All in One SEO – AI SEO Plugin for WordPress versions up to 5.0.5 contains a stored cross-site scripting (XSS) vulnerability via the 'name' parameter. Authenticated users with subscriber-level access or higher can inject malicious scripts that execute when other users view affected pages. Exploitation requires specific conditions including WordPress 6.6 or later with the Interactivity runtime and an administrator placing the AIOSEO breadcrumb on the author template.
A stored cross-site scripting (XSS) vulnerability exists in LeapWorx Premium Addons for Elementor up to version 4.11.118. This flaw allows improper neutralization of input during web page generation, potentially enabling attackers to inject malicious scripts. The vulnerability has a CVSS score of 6.5, indicating a medium severity level.