CVE-2026-111750: Aiohttp · Prior to 3.14.4, the pure Python parser accepts ambiguous HTTP request framing
Affects aiohttpSource GCVE Database
Not known to be exploited · CVSS 6.3 Medium : upgrade to 3.14.4 when convenient.
Data as of 17 Nov 2026, 11:04 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 6.3 |
|---|
- Patch
- Available – fixed in 3.14.4
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:L/SA:LExploitation evidence
Disclosed: evidence found.
CVE published 19 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade aiohttp to 3.14.4.
Patches and advisories
Affected software
| Product | Affected | Fixed in |
|---|---|---|
PyPIaiohttppkg:pypi/aiohttpOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available and the issue is fixed in aiohttp version 3.14.4. Users should upgrade to version 3.14.4 or later to remediate this vulnerability. No other mitigations are specified or required.
Description
Aiohttp versions prior to 3.14.4 contain a vulnerability in the pure Python HTTP request parser that allows ambiguous HTTP request framing. This can enable an unauthenticated attacker to perform HTTP request smuggling when the application uses AIOHTTP_NO_EXTENSIONS or runs without a standard wheel, and an intermediary interprets the framing differently. The issue is resolved in version 3.14.4.