CVE-2025-69224: PYSEC-2026-1099 - AIOHTTP's unicode processing of header values could cause parsing discrepancies

CVE-2025-69224 · Severity: medium · CVSS 6.5 · Published 2026-01-05

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Versions 3.13.2 and below of the Python HTTP parser may allow a request smuggling attack with the presence of non-ASCII characters. If a pure Python version of AIOHTTP is installed (i.e. without the usual C extensions) or AIOHTTP_NO_EXTENSIONS is enabled, then an attacker may be able to execute a request smuggling attack to bypass certain firewalls or proxy protections. This issue is fixed in version 3.13.3.

Technologies: Aiohttp, aiohttp (PyPI). Vendors: Aiohttp, PyPI.

Quick answers

Is CVE-2025-69224 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-69224 being exploited in the wild.
How severe is CVE-2025-69224?
Medium severity, with a CVSS score of 6.5, published 5 January 2026.
Which products and versions are affected?
aiohttp (PyPI) ECOSYSTEM:introduced=0,fixed=3.13.3.
Is there a fix for CVE-2025-69224?
Yes. aiohttp (PyPI): upgrade to 3.13.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-69224?
Check whether you run Aiohttp or aiohttp (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • aiohttp (PyPI): upgrade to 3.13.3 or later
    pip install "aiohttp>=3.13.3"

Affected products

  • Aiohttp
  • aiohttp (PyPI) ECOSYSTEM:introduced=0,fixed=3.13.3

Identifiers

  • CVE-2025-69224
  • GHSA-69f9-5gxw-wvc2
  • PYSEC-2026-1099

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.