Cyber Posture

CVE-2025-69227

High

Published: 06 January 2026

Published
06 January 2026
Modified
14 January 2026
KEV Added
Patch
CVSS Score 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0008 23.8th percentile
Risk Priority 15 60% EPSS · 20% KEV · 20% CVSS

Summary

CVE-2025-69227 is a high-severity Infinite Loop (CWE-835) vulnerability in Aiohttp Aiohttp. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 23.8th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

Threat & Defense at a Glance

What attackers do: exploitation maps to Exploit Public-Facing Application (T1190) and 1 other technique.
Threat & Defense Details

Likely Mitigating ControlsAI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-835

Enables transfer to alternate site if an infinite loop at the primary renders processing unavailable.

addresses: CWE-835

Detects and mitigates infinite loops that produce sustained resource consumption.

MITRE ATT&CK Enterprise TechniquesAI

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
Why these techniques?

Remote unauthenticated exploitation of public-facing AIOHTTP server triggers application DoS via crafted POST causing infinite loop.

Confidence: HIGH · MITRE ATT&CK Enterprise v18.1

NVD Description

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Versions 3.13.2 and below allow for an infinite loop to occur when assert statements are bypassed, resulting in a DoS attack when processing a POST body. If optimizations are…

more

enabled (-O or PYTHONOPTIMIZE=1), and the application includes a handler that uses the Request.post() method, then an attacker may be able to execute a DoS attack with a specially crafted message. This issue is fixed in version 3.13.3.

Deeper analysisAI

CVE-2025-69227 affects AIOHTTP, an asynchronous HTTP client/server framework for asyncio and Python, in versions 3.13.2 and prior. The vulnerability enables an infinite loop when assert statements are bypassed during POST body processing, leading to a denial-of-service (DoS) condition. This issue manifests only if Python optimizations are enabled via the -O flag or PYTHONOPTIMIZE=1 environment variable, and the application includes a handler that invokes the Request.post() method. It is classified under CWE-835 (Infinite Loop) with a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

An unauthenticated attacker with network access can exploit this by sending a specially crafted POST request to a vulnerable endpoint. No user interaction or privileges are required, allowing remote exploitation against affected servers. Successful exploitation triggers the infinite loop, consuming excessive CPU resources and rendering the application unresponsive, resulting in high-impact availability disruption without compromising confidentiality or integrity.

The issue is addressed in AIOHTTP version 3.13.3. Security practitioners should upgrade to this patched release immediately. Additional details are available in the official GitHub security advisory (GHSA-jj3x-wxrx-4x23) and the fixing commit (bc1319ec3cbff9438a758951a30907b072561259).

Details

CWE(s)

Affected Products

aiohttp
aiohttp
≤ 3.13.3

CVEs Like This One

CVE-2025-69223Same product: Aiohttp Aiohttp
CVE-2026-34513Same product: Aiohttp Aiohttp
CVE-2026-22815Same product: Aiohttp Aiohttp
CVE-2026-34516Same product: Aiohttp Aiohttp
CVE-2026-34520Same product: Aiohttp Aiohttp
CVE-2025-69228Same product: Aiohttp Aiohttp
CVE-2026-34515Same product: Aiohttp Aiohttp
CVE-2026-32256Shared CWE-835
CVE-2026-33891Shared CWE-835
CVE-2026-4111Shared CWE-835

References