CVE-2025-69223: AIOHTTP's HTTP Parser auto_decompress feature is vulnerable to zip bomb
AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Versions 3.13.2 and below allow a zip bomb to be used to execute a DoS against the AIOHTTP server. An attacker may be able to send a compressed request that when decompressed by AIOHTTP could exhaust the host's memory. This issue is fixed in version 3.13.3.
Security readout for executives and security teams
Plain-English summary
A vulnerable aiohttp server can be knocked offline by a specially compressed request that expands dramatically in memory. The issue affects aiohttp versions before 3.13.3 and is fixed in 3.13.3. The business risk is availability loss for Python services using aiohttp to process HTTP requests, not data theft or code execution based on current sources.
Executive priority
Treat this as a high-priority availability issue for Python services using aiohttp. Patch exposed services first, especially customer-facing APIs. Current sources do not indicate data compromise or active exploitation, but the low attack complexity makes delayed remediation risky.
Technical view
aiohttp versions 3.13.2 and below can decompress attacker-supplied compressed request data in a way that exhausts host memory. CVSS 7.5 reflects network reachability, low complexity, no authentication or user interaction, and high availability impact. CWE mappings are CWE-409 and CWE-770.
Likely exposure
Exposure is most likely in internet-facing or internal Python services running aiohttp before 3.13.3 as an HTTP server and accepting compressed request bodies. Applications that only depend on aiohttp transitively still need review, but the bundle does not prove every aiohttp use is exploitable.
Exploitation context
The source bundle does not show KEV listing or confirmed active exploitation. The vulnerability is remotely reachable and requires no authentication, so denial-of-service attempts are plausible where vulnerable aiohttp servers are exposed. No exploit steps or weaponization details are needed to assess urgency.
Researcher notes
Focus triage on server-side aiohttp deployments using affected versions. The advisory identifies auto_decompress and zip-bomb style expansion as the resource-exhaustion path. Evidence provided confirms a fixed upstream version and Red Hat advisory activity, but not active exploitation.
Mitigation direction
Upgrade aiohttp to version 3.13.3 or later.
For Red Hat packages, apply the relevant Red Hat advisory updates.
Inventory Python services and containers for aiohttp before 3.13.3.
Check vendor guidance before relying on compensating controls.
Prioritize exposed services that accept compressed HTTP request bodies.
Validation and detection
Review dependency manifests and lockfiles for aiohttp versions below 3.13.3.
Check runtime images and deployed packages, not only source repositories.
Map aiohttp server usage to public and internal HTTP routes.
Confirm patched Red Hat builds where aiohttp is OS-packaged.
Review monitoring for memory exhaustion and process restarts.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-409: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-409 · source CWE mapping
Improper Handling of Highly Compressed Data (Data Amplification)
Improper Handling of Highly Compressed Data (Data Amplification) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.