Threat Intelligence Database

A vulnerability in the Snyk agent scan affecting AIOHTTP allows the Secure attribute of a shared cookie to not be enforced. This means a cookie marked as Secure could be transmitted over unencrypted HTTP connections, potentially exposing sensitive session data. The issue affects versions from 0.4.3 up to but not including 0.6.9. A patch is available to address this vulnerability.

The aiohttp server did not enforce a keepalive timeout during the initial phase of a request, allowing an attacker to keep an idle connection open indefinitely before sending any data. This vulnerability affects versions from 0.4.3 up to but not including 0.6.9. A reverse proxy with appropriate keepalive limits is recommended as a workaround. A patch is available to address this issue.

A vulnerability in AIOHTTP allows an overflow in Max-Age processing that can prevent closing of connections, leading to temporary exhaustion of the connection pool until garbage collection intervenes. This affects versions from 0.4.3 up to but not including 0.6.9. The issue does not require user interaction or privileges to exploit and has a low impact on availability.

CVE-2026-111066 is a vulnerability in aiohttp where an attacker can exhaust file descriptors by sending specially crafted multipart requests. This affects handlers using Request.post(), potentially leading to resource exhaustion. Versions from 0.4.3 up to but not including 0.6.9 are affected. A patch is available to address this issue.

This vulnerability in AIOHTTP allows an attacker to spoof the Request.scheme attribute by sending an absolute-form request. Applications relying on Request.scheme for security decisions may be tricked into misinterpreting the connection as encrypted or not. A workaround is to use a WAF rule to reject absolute-form requests, which are typically only legitimate for proxy use. A patch is available for affected versions.

A vulnerability in AIOHTTP allows a subdomain to remove the Host-Only flag from an existing cookie set for a parent domain. This could reduce cookie security protections for users accessing untrusted subdomains. The impact is limited because most use cases do not reflect these cookies back to a browser.

AIOHTTP's pure-Python HTTP parser is vulnerable to an HTTP request smuggling attack when the Python parser is used instead of the default C parser. This affects versions from 0.4.3 up to but not including 0.6.9. The vulnerability can be mitigated by switching to the default C parser.

Multiple vulnerabilities in aiohttp versions 0.4.3 up to but not including 0.6.9 can lead to excessive or unbounded memory and CPU usage triggered by attacker-controlled requests. This can cause resource exhaustion on affected systems.

Starlette's StaticFiles component on Windows platforms has a vulnerability where resolving UNC paths triggers outbound SMB connections, leaking NTLMv2 credentials. This occurs because os.path.realpath resolves UNC paths before containment checks, causing server-side request forgery (SSRF). The vulnerability affects default configurations (follow_symlink=False) and can expose service account credentials to attackers. Non-Windows systems and configurations using follow_symlink=True are not affected. Mitigations include using dedicated web servers for static files or blocking outbound SMB traffic.

A vulnerability in the MCP Python SDK HTTP transports (SSE and Streamable HTTP in stateful mode) allows session hijacking by bypassing authentication checks. Incoming requests are routed to existing sessions based solely on session IDs without verifying the authenticated principal. This enables an attacker who knows or guesses a session ID to send JSON-RPC messages on that session regardless of the bearer token used. The issue affects versions from 0.4.3 up to but not including 0.5.17. A fix is available in version 1.27.2 or later.