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.
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 3.94.2.
AIOHTTP versions 3.91.0 through 3.94.1 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 with specially crafted compressed request bodies or WebSocket messages. The issue is fixed in version 3.94.2.
A vulnerability in aiohttp's pure-Python HTTP parser causes buffered request data to be replayed and the buffer to grow when an upgrade request is declined. This leads to excessive memory consumption and multiple processing of pipelined requests. The issue affects versions 3.91.0 up to but not including 3.94.2 and is fixed in version 3.94.2. Users relying on the pure-Python parser (e.g., with AIOHTTP_NO_EXTENSIONS) are impacted. Switching to the default C parser mitigates the issue.
AIOHTTP versions from 3.91.0 up to but not including 3.94.2 have a vulnerability where data received during an HTTP upgrade request (such as a WebSocket handshake) is buffered without limits until the handler finishes processing. This can lead to unbounded memory consumption if an attacker streams large amounts of data behind the upgrade request. The issue is fixed in version 3.94.2.
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 enables an attacker to send an oversized WebSocket message after a small non-final fragment, causing unbounded memory consumption. The issue affects versions from 3.91.0 up to but not including 3.94.2 and is fixed in version 3.94.2.
A vulnerability in aiohttp multipart handling allows bypassing the client_max_size limit when processing parts with Content-Transfer-Encoding: base64. This can cause excessive memory consumption or event loop blocking due to unbounded reading of multipart data. The issue affects versions from 3.91.0 up to but not including 3.94.2 and is fixed in version 3.94.2.
AIOHTTP's Request.post() method had no 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 flaw allows an attacker to block the event loop by sending a form POST with many fields within the default client_max_size. The issue affects versions from 3.91.0 up to but not including 3.94.2 and has been fixed in version 3.94.2.
CVE-2026-128125 is a vulnerability in aiohttp's client CookieJar where unbounded cookie storage occurs due to improper parsing of Set-Cookie headers. The CookieJar accepts additional cookies from unrecognized name=value attributes without limits, allowing a malicious server to cause excessive memory and CPU usage on the client by making it store a very large number of cookies. This also results in excessively large Cookie headers on subsequent requests to the same domain. The issue affects aiohttp versions from 3.91.0 up to but not including 3.94.2 and has been fixed in version 3.94.2.
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 event loop by sending requests with long Host headers against such domain masks. The issue affects versions from 3.91.0 up to but not including 3.94.2 and is fixed in version 3.94.2.