Skip to main content
VulnerabilityPublished Updated

CVE-2023-47627: aio-libs aiohttp · HTTP Request/Response Smuggling

Affects aio-libs aiohttpSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium : upgrade to 3.8.6 when convenient.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 58% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.8.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Nov 2023

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Upgrade aio-libs aiohttp to 3.8.6.

Affected software

ProductAffectedFixed in
PyPIaiohttppkg:pypi/aiohttpOther threatsAffected
  • <3.8.6
Fixed in
  • 3.8.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The primary mitigation is to upgrade all aiohttp installations to version 3.8.6 or later, where the vulnerability has been fixed. Organizations should audit their Python environments to identify any use of aiohttp, especially in configurations where AIOHTTP_NO_EXTENSIONS is set or where prebuilt wheels are not used. If upgrading immediately is not feasible, consider enforcing the use of prebuilt wheels or enabling extensions to avoid the vulnerable parser. Network-level protections such as strict HTTP header validation and deploying web application firewalls with rules to detect request smuggling attempts can provide additional defense layers. Monitoring HTTP traffic for anomalies and unusual request patterns may help detect exploitation attempts. Developers should review their HTTP handling code for reliance on vulnerable aiohttp versions and avoid custom builds that disable extensions unless necessary. Finally, maintain awareness of updates from aio-libs and apply security patches promptly.

Description

aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. The HTTP parser in AIOHTTP has numerous problems with header parsing, which could lead to request smuggling. This parser is only used when AIOHTTP_NO_EXTENSIONS is enabled (or not using a prebuilt wheel). These bugs have been addressed in commit `d5c12ba89` which has been included in release version 3.8.6. Users are advised to upgrade. There are no known workarounds for these issues.

References

Community reviews

Loading reviews…