Skip to main content
CVE-2025-69228VulnerabilityPublished

CVE-2025-69228: aio-libs aiohttp · Unthrottled Resource Allocation

Affects aio-libs aiohttpSource CVE Database V5

0

Not known to be exploited · CVSS 6.6 Medium : upgrade to 3.13.3 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
6.6Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.13.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade aio-libs aiohttp to 3.13.3.

Affected software

ProductAffectedFixed in
aio-libsaiohttpAffected
  • <3.13.3
Fixed in
  • 3.13.3
PyPIaiohttppkg:pypi/aiohttpOther threatsAffected
  • <3.13.3
Fixed in
  • 3.13.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The most effective mitigation is to upgrade all aiohttp deployments to version 3.13.3 or later, where this vulnerability is fixed. Organizations should audit their Python environments to identify and update affected aiohttp versions promptly. Beyond patching, developers should implement strict limits on request sizes and payload processing within their aiohttp handlers to prevent excessive memory consumption. Employing rate limiting and connection throttling at the application or network level can reduce the risk of resource exhaustion attacks. Monitoring server memory usage and application logs for unusual spikes or patterns indicative of abuse can enable early detection and response. In containerized or cloud environments, setting resource quotas and limits can help contain the impact of such attacks. Finally, incorporating fuzz testing and resource usage profiling during development can help identify similar vulnerabilities proactively.

Description

CVE-2025-69228 is a medium severity vulnerability in aiohttp versions prior to 3.13.3 that allows an attacker to exhaust server memory by crafting malicious HTTP requests targeting handlers using the Request.post() method. This flaw arises from the lack of resource allocation limits or throttling, causing uncontrolled memory consumption and potential server freeze or denial of service. The vulnerability requires no authentication or user interaction and can be exploited remotely over the network. Although no known exploits are currently in the wild, affected servers remain at risk until patched. European organizations using aiohttp-based asynchronous Python web servers should prioritize updating to version 3.13.3 to mitigate this risk.

References

Community reviews

Loading reviews…