Quick answers
- Is CVE-2025-69230 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-69230 being exploited in the wild.
- How severe is CVE-2025-69230?
- 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-69230?
- 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.
- How is CVE-2025-69230 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-69230?
- Check whether you run 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"
Technical details
The vulnerability is a denial-of-service via logging storm in aiohttp's cookie parser. When an application accesses the cookies attribute of a request and a malformed Cookie header is present, the parser generates repeated warning logs for each invalid cookie, rather than logging once per header. An attacker can craft a Cookie header with multiple invalid entries to flood the application logs. The attack requires network access to send a specially crafted HTTP request to an application using aiohttp. The fix, merged in commit 64629a0, implements per-header logging limits to prevent the storm.
Affected products
- aio-libs aiohttp <=3.13.2
Identifiers
- CVE-2025-69230
- GHSA-fh55-r93g-j68g
- PYSEC-2026-1105
Timeline
- 2026-01-06: disclosed
- 2026-01-05: patched: Fix available in version 3.13.3