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.
AIOHTTP's client CookieJar component improperly handled Set-Cookie headers by creating additional cookies from unrecognized name=value attributes without limiting the total number of cookies stored or sent. This flaw allows a malicious server to cause excessive memory and CPU consumption on the client side by forcing it to store a very large number of cookies and generate oversized Cookie headers, especially during redirects.
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 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. A fix is available in version 5.14.0_18.
CVE-2026-128131 is a vulnerability in AIOHTTP where decompressing concatenated compressed streams (gzip, deflate, or zstd) causes excessive CPU usage due to quadratic time complexity in processing. This can block the event loop of a server or client when handling specially crafted compressed request bodies or WebSocket messages. The issue is fixed in version 5.14.0_18.
A vulnerability in AIOHTTP's pure-Python HTTP parser causes the request buffer to grow uncontrollably when an upgrade request is declined, leading to excessive memory use and repeated processing of pipelined requests. This affects users relying on the Python parser instead of the default C parser. The issue is fixed in version 5.14.0_18.
AIOHTTP versions from 5.14.0_13 up to but not including 5.14.0_18 have a vulnerability 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. A patch is available in version 5.14.0_18 to address this issue.
AIOHTTP's WebSocket implementation contains an integer overflow vulnerability in the max_msg_size check within its C extension. This flaw allows an attacker to bypass the maximum message size restriction by sending a crafted WebSocket message with a declared length near 2^63, causing unbounded memory consumption. The vulnerability affects versions from 5.14.0_13 up to but not including 5.14.0_18. A fix is available in version 5.14.0_18. As a workaround, disabling the C extension by setting AIOHTTP_NO_EXTENSIONS=1 forces use of the unaffected Python reader.
Deserialization of Untrusted Data in Apache Roller versions 4.0.0 through 6.1.4 allows an unauthenticated remote attacker to execute arbitrary code. The XML-RPC endpoint accepts vendor extension types and deserializes them before authenticating the requester.
This is the same vulnerability as CVE-2026-82384, which listed only Apache Roller 6.1.5 as affected. This issue is being actively exploited.
Users are recommended to upgrade to Apache Roller 6.1.6 or later, which disables the extension types and rejects XML-RPC requests when the XML-RPC feature is disabled.
Users who cannot upgrade right away should set "enabledForExtensions" to "false" in WEB-INF/web.xml, or remove the "/roller-services/xmlrpc" servlet mapping, and restart Roller. Disabling XML-RPC in the administration UI is not enough, because older versions deserialize the request before checking that setting.
The XaocMail ClickFix campaign is a sophisticated multi-stage phishing operation by a Russian-speaking threat actor targeting organizations in Latin America, Asia, and Europe. It uses the XaocMail phishing platform to deliver malicious MSI payloads via social engineering lures named ClickFix. The campaign employs Phantom53, a DNS-over-HTTPS command-and-control framework, and Havoc, a post-exploitation toolkit, leveraging Cloudflare Workers infrastructure for stealth and resilience. The attackers use advanced techniques including domain generation algorithms, scheduled tasks with Python virtual environments for persistence, and AI-assisted development for rapid iteration. Targets include sectors such as technology, finance, education, government, logistics, and manufacturing. The operation demonstrates advanced operational security and infrastructure abuse to evade detection.
On November 16, 2026, a widespread malware campaign compromised 178 organizations via the Optimizely Web experimentation platform. Attackers injected malicious JavaScript into customer Project JavaScript fields, which was then served from trusted Optimizely CDN domains. The malware performed cryptocurrency wallet address swapping, payment card skimming, cookie theft, screenshot capture, and deployed iOS exploit kits targeting iPhones and iPads. Approximately $7,040 in cryptocurrency theft was confirmed within nine hours. The payload was frequently updated throughout the day to add new capabilities. Most malicious code was removed by 21:52 UTC. Proper Content Security Policy configurations could have prevented the attack on some sites.
The Pilz Industrial PC product contains vulnerabilities in its PHP component (referred to as PHP2Shell) that allow an attacker to send specially crafted requests to the webserver. Successful exploitation can result in remote code execution on the affected device.
Operation ShadowCloud is a sophisticated cyber intrusion campaign targeting government entities in Asia and Africa. It uses novel backdoors named GitDoor and GraphDoor deployed via the legitimate MeshAgent utility. These backdoors hide command-and-control communications by leveraging cloud platforms such as Microsoft SharePoint, GitHub, and Ably messaging services to evade network detection. The modular toolset supports on-demand plugin downloads and in-memory shellcode injection, enabling keylogging, screen capture, credential theft, and proxy deployment. The campaign employs DLL sideloading with legitimate executables to deliver encrypted payloads. Multiple GitHub repositories created since late 2024 are used for data exfiltration and command distribution. The operation uses advanced obfuscation techniques including control flow flattening and multi-stage payloads.
A phishing campaign uses a credential-harvesting page that collects not only victims' passwords but also additional information including public IP, geolocation, browser details, and notably, MX records of the victim's email domain via DNS-over-HTTPS queries. The MX records are included with stolen credentials to help attackers identify the victim organization's email infrastructure, potentially aiding further attacks or prioritization of stolen data. The phishing page is hosted on Google Cloud Storage and personalizes the login form using the victim's email domain. This behavior represents an enhanced reconnaissance step embedded in the phishing process.