CVE-2025-69225: PYSEC-2026-1109 - AIOHTTP has unicode match groups in regexes for ASCII protocol elements

CVE-2025-69225 · Severity: medium · CVSS 5.3 · Published 2026-01-06

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Versions 3.13.2 and below contain parser logic which allows non-ASCII decimals to be present in the Range header. There is no known impact, but there is the possibility that there's a method to exploit a request smuggling vulnerability. This issue is fixed in version 3.13.3.

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

Quick answers

Is CVE-2025-69225 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-69225 being exploited in the wild.
How severe is CVE-2025-69225?
Medium severity, with a CVSS score of 5.3, published 6 January 2026.
Which products and versions are affected?
aiohttp (PyPI) ECOSYSTEM:introduced=0,fixed=3.13.3.
Is there a fix for CVE-2025-69225?
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-69225?
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-69225
  • GHSA-mqqc-3gqh-h2x8
  • PYSEC-2026-1109

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