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 consume 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(). A patch addressing this issue is available.
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 the client to consume excessive memory and CPU resources by storing a very large number of cookies and generating oversized Cookie headers, especially during redirects.
AIOHTTP's Application.add_domain() function had a performance issue where domain masks with two or more wildcards caused polynomial-time matching delays on long Host headers. This could be exploited by an attacker to stall the server's event loop by sending crafted requests with long Host headers. The vulnerability affects versions 1.5.2 and later. A patch is available that fixes the wildcard matching inefficiency. As a workaround, limiting domain masks to at most one wildcard reduces the 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 affected WebSocket servers or clients. The issue arises because the WebSocket reader continues parsing frames after the queue pauses transport, and empty messages are not counted towards the queue size. A fix is available in version 2026.5.16_1.
AIOHTTP versions from 0.21.6 up to but not including 2026.5.16_1, and versions from 2026.9.14 onward, contain a vulnerability where decompressing concatenated compressed streams (gzip, deflate, or zstd) causes excessive CPU usage due to quadratic time complexity. This can allow an attacker to block the event loop of a server or client by sending specially crafted compressed payloads. A fix is available in version 2026.5.16_1.
A vulnerability in the pure-Python parser of AIOHTTP causes the request buffer to grow excessively when handling declined upgrade requests, leading to repeated processing of pipelined requests and excessive memory use. This affects users relying on the Python parser instead of the default C parser. A patch is available that fixes this issue.
AIOHTTP versions from 0.21.6 up to but not including 2026.5.16_1 have a vulnerability where data received during an upgrade request (such as a WebSocket handshake) is buffered without limits 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. The issue is fixed in version 2026.5.16_1.
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 frame length close to 2^63, causing unbounded memory consumption. The issue is fixed in version 2026.5.16_1. Users unable to upgrade can mitigate by disabling the C extension and using the Python reader instead.
AIOHTTP contains a vulnerability in its multipart data 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, allowing an attacker to cause excessive memory consumption or event loop blocking with crafted multipart requests. A fix is available in version 2026.5.16_1.
The RubyGems package 'node-test-repo' version 1.0.1 has been identified as malicious by the OpenSSF Package Analysis project. The package is considered malicious because it communicates with a domain associated with malicious activity. No CVSS score or detailed technical impact information is provided.
The PyPI package 'pepestyglo' version 1.0.0 contains malicious code that exfiltrates basic host information such as IP address and username upon installation or import. The package overrides the install command in setup.py to execute this malicious behavior. It serves no legitimate purpose beyond this data exfiltration.
The logger-prefix-buffer-lexer package on PyPI contains malicious code that exfiltrates basic host information such as IP address and username upon installation or import. The package overrides the install command in setup.py to execute this malicious behavior. It serves no legitimate purpose beyond this data exfiltration.
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.
A Cross-Site Scripting (XSS) vulnerability reflected in the GET parameters `cod_primaria` and `cod_secundaria` of the Novanet Web endpoints `NNws_ShwNewDup` and `NPcd/NFG_VerNoticia`. User-provided data is reflected within a JavaScript block without proper sanitization or context-appropriate output encoding. An unauthenticated remote attacker could craft a manipulated URL that, when visited by a victim, would execute arbitrary JavaScript code in the victim’s browser, within the context of the affected site. The flaw resides in the platform’s shared code, so it could affect organizations using that vulnerable code.