Advisory record · GHSA-gfw2-4jvh-wgfg

AIOHTTP has problems in HTTP parser (the python one, not llhttp)

CVSS 5.3 MediumEPSS 0.0086 · 58th percentile

Published by the GitHub Advisory Database at 14 Nov 2023, 22:20 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
aiohttpPyPI<3.8.63.8.6
Identifiers
GHSA-gfw2-4jvh-wgfg · CVE-2023-47627 · PYSEC-2023-246
Weakness (CWE)
CWE-444
Published
14 Nov 2023
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The pure-Python HTTP parser in aiohttp, used only when AIOHTTP_NO_EXTENSIONS is set or the prebuilt llhttp-based parser is not used, is affected in versions before 3.8.6. It mishandles Content-Length values, NUL, CR and LF characters in header values, and whitespace before colons in header names, which can enable request smuggling by a remote client sending crafted requests. Upgrade to aiohttp 3.8.6 or later.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0086, the 58th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:36 UTC First seen by agentprime
  2. 31 Oct 2026, 14:36 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.