LiveActive security incident?Get immediate response
CVE Record

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.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

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.
Prepared
Confidence
high
Sources
10

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.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-770: 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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-69223 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

2CVSS vectors
5Timeline events
2ADP providers
26Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

2 official scores

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.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6GitHub_M
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2025-69223Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPaiohttp: AIOHTTP's HTTP Parser auto_decompress feature is vulnerable to zip bomb
other:Red Hat severity ratingcvssV3_1
  • 2026-01-06T20:01:19.831Z: Reported to Red Hat.
  • 2026-01-05T22:00:17.715Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
aio-libsaiohttp< 3.13.3Listed
Weakness

CWE details

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.

CWE-770 · source CWE mapping

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.