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.
AIOHTTP's WebSocket implementation has an integer overflow vulnerability in the max_msg_size check that allows bypassing the message size limit. This occurs because the addition of the declared frame length to the buffered partial message size uses 64-bit arithmetic, which overflows for lengths near 2^63. An attacker can exploit this to send an oversized WebSocket message after a small fragment, causing unbounded memory consumption.
AIOHTTP's Application.add_domain() method had a performance issue where domain masks with two or more wildcards caused polynomial-time matching on long Host headers, leading to event loop stalls. An attacker could exploit this by sending requests with long Host headers to stall the server. The vulnerability affects versions starting from 0.1.5. A patch is available that addresses this issue. As a workaround, limiting domain masks to at most one wildcard reduces the risk.
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.
A vulnerability in AIOHTTP's pure-Python HTTP parser causes buffer growth and request replay when handling declined upgrade requests with a full pipelined request queue. This affects users relying on the Python parser instead of the default C parser. An attacker could exploit this to cause excessive memory consumption and trigger multiple processing of pipelined requests.
The CODESYS Automation Server Connector uses server-supplied file names without sufficient path traversal checks. An unauthenticated remote attacker controlling a malicious Automation Server and tricking a user to trust it, or performing a man-in-the-middle attack on a trusted communication channel, can exploit this vulnerability to write attacker-controlled files to arbitrary locations on the engineering workstation and subsequently achieve arbitrary code execution with user privileges.
The affected products do not sufficiently validate CODESYS Automation Server TLS certificates when a user starts the certificate enrollment. An unauthenticated remote attacker performing a man-in-the-middle attack can exploit this vulnerability by supplying an untrusted certificate that is accepted as trusted. Successful exploitation may allow an attacker to intercept and manipulate communications between the CODESYS Automation Server and the PLC network.
The affected products process a server-supplied URL without sufficient validation. An unauthenticated remote attacker controlling a malicious Automation Server and tricking a user to trust it or performing a man-in-the-middle attack, can exploit this vulnerability by causing the affected product to process unintended content. Successful exploitation may result in arbitrary code execution with the privileges of the user running the affected product.
The NLTK library's sql_query() function in the chat80 module bypasses the pathsec sandbox intended to restrict SQLite database access to specific data roots. It does so by following symbolic links inside trusted data roots that point to SQLite databases outside those roots, allowing read access to out-of-sandbox databases. This occurs because sql_query() uses nltk.data.find() which only performs lexical checks and does not resolve symlinks, unlike other functions that enforce path containment. An attacker with write access to a trusted NLTK data root can exploit this to read sensitive SQLite databases elsewhere on the filesystem.
AIOHTTP versions >=3.27.1_1 and <3.27.1_2 contain a vulnerability where multipart parts encoded with base64 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 a byte limit, allowing excessive memory consumption or event loop blocking. A specially crafted multipart request can exploit this to cause denial of service. The issue is fixed in version 3.27.1_2.
A post-authentication command injection vulnerability exists in the "Description" parameter of a CGI program in Zyxel DX3300-T0 firmware versions up to 5.50(ABVY.8.3)C0. An attacker with administrator privileges can exploit this flaw by sending a crafted HTTP request to execute arbitrary OS commands.