Advisory record · GHSA-69f9-5gxw-wvc2

AIOHTTP's unicode processing of header values could cause parsing discrepancies

CVSS 6.3 MediumEPSS 0.0025 · 16th percentile

Published by the GitHub Advisory Database at 5 Jan 2026, 22:58 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
aiohttpPyPI<3.13.33.13.3
Identifiers
GHSA-69f9-5gxw-wvc2 · CVE-2025-69224 · PYSEC-2026-1099
Weakness (CWE)
CWE-444
Published
5 Jan 2026
Updated
10 Sept 2026

Machine-written summary

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

Versions of aiohttp before 3.13.3 are affected. When the pure Python HTTP parser is in use, either because the C extensions are not installed or because AIOHTTP_NO_EXTENSIONS is enabled, an attacker may be able to smuggle requests containing non-ASCII characters in header values, which could bypass certain firewall or proxy protections. Upgrade to aiohttp 3.13.3 or later. The source gives few details on the exact conditions.

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
6.3 Medium 4.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0025, the 16th 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.