Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-111750 Overview
CVE-2026-111750 is an HTTP Request Smuggling vulnerability in AIOHTTP, an asynchronous HTTP client/server framework for asyncio and Python. The pure Python parser accepts ambiguous HTTP request framing in versions prior to 3.14.4. An unauthenticated remote attacker can smuggle requests when an application uses AIOHTTP_NO_EXTENSIONS or runs without a standard wheel, and an upstream intermediary interprets the framing differently. The flaw is categorized under CWE-444: Inconsistent Interpretation of HTTP Requests. Maintainers fixed the issue in AIOHTTP 3.14.4.
Critical Impact
Unauthenticated attackers can bypass front-end security controls, poison caches, or hijack sessions by desynchronizing request parsing between an intermediary proxy and an AIOHTTP backend.
Affected Products
- AIOHTTP versions prior to 3.14.4 (pure Python parser path)
- Deployments using the AIOHTTP_NO_EXTENSIONS environment variable
- AIOHTTP installations running without the standard C-extension wheel
Discovery Timeline
- 2026-10-19 - CVE-2026-111750 published to the National Vulnerability Database (NVD)
- 2026-10-19 - Last updated in NVD database
Technical Details for CVE-2026-111750
Vulnerability Analysis
The vulnerability resides in AIOHTTP's pure Python HTTP parser. The parser accepts ambiguous framing constructs in incoming HTTP requests. When AIOHTTP sits behind an intermediary such as a reverse proxy or load balancer, the two components may disagree on where one request ends and the next begins. This parser disagreement is the mechanism exploited in HTTP Request Smuggling (HRS) attacks.
The pure Python code path is used when the C-accelerated parser is unavailable. This occurs when AIOHTTP_NO_EXTENSIONS=1 is set, when a source-only install is performed, or when a non-standard wheel is used. The patched commit in aiohttp/http_parser.py corrects empty-body method handling, ensuring EMPTY_BODY_METHODS applies only to responses and that self.method is referenced on the request parser. This aligns parsing behavior with RFC 9112 message body length rules.
Root Cause
The root cause is improper determination of message body length during request parsing. The parser incorrectly treated certain method tokens as implying an empty body, causing it to disregard framing headers such as Content-Length and Transfer-Encoding in ways that diverge from upstream proxy interpretation. This inconsistency enables request smuggling.
Attack Vector
An unauthenticated attacker submits a single crafted HTTP request to the front-end intermediary. The intermediary forwards what it believes is one request. The AIOHTTP backend interprets the stream as two requests, with the smuggled second request executed against another user's connection. This can lead to cache poisoning, credential theft, bypass of front-end access controls, and session takeover.
assert self.protocol is not None
# calculate payload
+ # https://www.rfc-editor.org/info/rfc9112/#name-message-body-length
+ # https://www.rfc-editor.org/info/rfc9110/#section-9.3.1-6
+ # EMPTY_BODY_METHODS should only apply to responses.
+ # self.method is None on request parser.
empty_body = code in EMPTY_BODY_STATUS_CODES or bool(
- method and method in EMPTY_BODY_METHODS
+ self.method and self.method in EMPTY_BODY_METHODS
)
if not empty_body and (
(length is not None and length > 0) or msg.chunked
Source: aiohttp commit 9b27347e61454d9f8ca2055f4c67a37dee336e83. The patch ensures the request parser evaluates self.method rather than a stale method variable when determining empty-body semantics.
Detection Methods for CVE-2026-111750
Indicators of Compromise
- Requests arriving at the AIOHTTP backend containing both Content-Length and Transfer-Encoding: chunked headers.
- Unexpected HTTP method verbs or request bodies appearing in logs on connections that were previously idle.
- Mismatched request counts between the front-end proxy access log and the AIOHTTP application log.
- Pipelined requests whose framing disagrees with the intermediary's interpretation.
Detection Strategies
- Inventory Python environments to identify AIOHTTP installations running under AIOHTTP_NO_EXTENSIONS or without the compiled C extension.
- Compare request counts and byte boundaries between the reverse proxy and the AIOHTTP backend to find desynchronization.
- Instrument middleware to log and reject requests containing both Content-Length and Transfer-Encoding headers.
Monitoring Recommendations
- Alert on HTTP 400 bursts and malformed framing errors emitted by AIOHTTP after an intermediary upgrade or configuration change.
- Monitor for anomalous responses served to the wrong user session, a common post-exploitation signal of smuggling.
- Capture full HTTP headers at the WAF or proxy layer to retain evidence of ambiguous framing attempts.
How to Mitigate CVE-2026-111750
Immediate Actions Required
- Upgrade AIOHTTP to version 3.14.4 or later across all Python environments.
- Audit deployments for the AIOHTTP_NO_EXTENSIONS environment variable and remove it unless strictly required.
- Ensure installations use the official pre-built wheel so the C-accelerated parser is active.
- Validate that upstream proxies reject requests containing conflicting Content-Length and Transfer-Encoding headers.
Patch Information
AIOHTTP 3.14.4 contains the fix. Review the GitHub Security Advisory GHSA-pqxq-w44r-73xw and the AIOHTTP v3.14.4 release notes for full remediation details. The underlying code change appears in the upstream commit.
Workarounds
- Remove or unset the AIOHTTP_NO_EXTENSIONS environment variable to force use of the C parser where upgrading is not immediately possible.
- Place a strict HTTP/1.1-compliant reverse proxy in front of AIOHTTP that normalizes or rejects ambiguous framing.
- Terminate client connections after each request at the intermediary to limit the impact of any smuggled payload.
# Upgrade AIOHTTP to the patched release
pip install --upgrade "aiohttp>=3.14.4"
# Verify the C extension parser is in use (should print True)
python -c "from aiohttp import http_parser; print(http_parser.HttpRequestParserC is not None)"
# Ensure the no-extensions flag is not set in the runtime environment
unset AIOHTTP_NO_EXTENSIONS
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

