# CVE-2025-69230: aiohttp logging storm in cookie parsing

Source: https://junglewise.ai/threats/cve-2025-69230-aiohttp-logging-storm-in-cookie-parsing  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-01-06. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

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

aiohttp is a Python library for building asynchronous web applications. A specially crafted HTTP Cookie header can trigger excessive warning-level logs in applications that access the cookies attribute, potentially degrading performance and filling log storage. This is resolved in version 3.13.3.

Technologies: [aiohttp (PyPI)](https://junglewise.ai/threats/technologies/aiohttp). Vendors: [PyPI](https://junglewise.ai/threats/vendors/pypi).

## 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

  ```sh
  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

## References

- [https://github.com/aio-libs/aiohttp/commit/64629a0834f94e46d9881f4e99c41a137e1f3326](https://github.com/aio-libs/aiohttp/commit/64629a0834f94e46d9881f4e99c41a137e1f3326)
- [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-fh55-r93g-j68g](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-fh55-r93g-j68g)

## Related threats

- [aiohttp HTTP request smuggling in pure Python parser](https://junglewise.ai/threats/cve-2026-111750-aiohttp-is-an-asynchronous-http-client-server-framework-for)
- [aiohttp host-only cookie scope bypass in subdomain handling](https://junglewise.ai/threats/cve-2026-111749-aiohttp-is-an-asynchronous-http-client-server-framework-for)
- [aiohttp Request scheme manipulation in absolute-form requests](https://junglewise.ai/threats/cve-2026-111748-aiohttp-is-an-asynchronous-http-client-server-framework-for)
- [AIOHTTP multipart request file descriptor exhaustion](https://junglewise.ai/threats/cve-2026-111066-aiohttp-is-an-asynchronous-http-client-server-framework-for)
- [aiohttp cookie Max-Age integer overflow causes connection pool exhaustion](https://junglewise.ai/threats/cve-2026-111065-aiohttp-is-an-asynchronous-http-client-server-framework-for)