N-able N-central before 2026.4.1 HF3 does not authenticate callers of the ServerMMS2 RemoteExecutionTaskSubmit operation or verify task ownership. A remote, unauthenticated attacker can submit forged results for remote execution tasks belonging to any customer.
N-able N-central before 2026.4.1 HF3 does not neutralise control characters in an Audit Export setting before writing it to the system logging configuration. An authenticated attacker with product administrator privileges can inject configuration and execute commands as root on the N-central server.
N-able N-central before 2026.4.1 HF3 uses a predictable credential to authenticate appliances to an agent-facing API. A remote, unauthenticated attacker who knows or guesses an appliance identifier can obtain a valid appliance token and session and impersonate that appliance.
Lotuslite V2 is a .NET-based backdoor malware attributed to the Mustang Panda threat actor, targeting government and diplomatic entities in Thailand. It is delivered via a public Zoho WorkDrive link containing a ZIP archive themed as an assessment. The infection chain uses a signed PDFgear executable for DLL side-loading, establishes persistence through registry modifications, and communicates with command-and-control servers over TCP using AES-256-GCM encrypted application-layer traffic. This variant represents an evolution from the original C++ LOTUSLITE malware, featuring enhanced cryptographic protections and refined command routing techniques.
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 is fixed in version 2.19.0_2.
AIOHTTP versions >=2.19.0 and <2.19.0_2 contain a vulnerability where decompressing concatenated compressed streams (gzip, deflate, or zstd) causes excessive CPU usage due to quadratic time complexity. This can block the event loop of servers or clients when processing specially crafted compressed payloads. The issue is fixed in version 2.19.0_2.
A vulnerability in the pure-Python HTTP parser used by AIOHTTP can cause excessive memory consumption and repeated processing of pipelined requests when the request queue is full and an upgrade request is declined. This affects users relying on the Python parser instead of the default C parser. The issue is fixed in version 2.19.0_2.
AIOHTTP versions >=2.19.0 and <2.19.0_2 have a vulnerability where data received during an HTTP upgrade request (such as a WebSocket handshake) is buffered without limit 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.
AIOHTTP's WebSocket implementation contains an integer overflow vulnerability in the max_msg_size check within the 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 near 2^63, causing unbounded memory use. The issue affects versions from 2.19.0 up to but not including 2.19.0_2. A patch is available in version 2.19.0_2. As a workaround, disabling the C extension by setting AIOHTTP_NO_EXTENSIONS=1 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 set to base64. This causes the server to read excessive data into memory or spin the event loop, potentially leading to denial of service. The issue affects versions >=2.19.0 and fixed in 2.19.0_2.
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 flaw allows 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 fix is available in version 2.19.0_2.
AIOHTTP's client CookieJar component improperly parses Set-Cookie headers, creating additional cookies from unrecognized name=value attributes without limiting the number of stored cookies. This allows a malicious server to cause excessive memory and CPU consumption on the client by forcing it to store and send very large Cookie headers, especially on repeated redirects. The issue affects scrapy versions from 2.19.0 up to but not including 2.19.0_2. A patch is available in version 2.19.0_2.
AIOHTTP's Application.add_domain() function had a performance issue where using two or more wildcards (*) in a domain mask caused polynomial-time matching delays on long Host headers. This could allow an attacker to stall the server's event loop by sending crafted requests with long Host headers against such domain masks. The issue is fixed in version 2.19.0_2. Until patched, a workaround is to limit domain masks to at most one wildcard.