vciy

CVE-2025-69223

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

AIOHTTP's HTTP Parser auto_decompress feature is vulnerable to zip bomb

CVE-2025-692234 of 4 sources documented this
21

rank 21 = 0 + 19 + 0 + 2 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.00570  ·  without this subject the record ranks 21

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 7.5, from the CNA  ·  without this subject the record ranks 2

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 21

How much of the world it touches

NVD CPE configurations

1 product in the CPE ranges  ·  without this subject the record ranks 19

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 21

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$17,400over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$17,400 = $4.99M incident cost x 0.6121449559255632 exposure x 0.0057 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.0057EPSSNOT IN KEVas of 2026-09-20
Severity7.5 HIGHreceipt
Harmunauthenticated · networkreceipt
Exploitationnone in held sources
Defenseunaffected versions publishedreceipt
Movementrisenreceipt
PLATEAU10Minimal movement since 2026-01-06, 239 days at 0.01, as of 2026-09-02. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Running aio-libs aiohttp? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · no privileges required · no user interaction · low attack complexityreceipt
ImpactComplete availability lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-409 Improper Handling of Highly Compressed Data (Data Amplification); CWE-770 Allocation of Resources Without Limits or Throttlingreceipt
Published consequencesCWE-409: Availability: DoS: Amplification, DoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory)[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

First unaffected version, by branchaiohttp 3.13.3receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA7.5 HIGHreceipt
Exploit probability0.0057 · top 54% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byGitHub_Mreceipt
Recorded changes13 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productaio-libs aiohttpreceipt
Published rangesaiohttp < 3.13.3receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

Attack path

Unauthenticated network requestno credentials, no interactionaio-libs aiohttpCWE-409 weaknessAvailability lossA:Hexploits CWE-409data compromise

What it is stated by the CNA

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. receipt

NVD's analysis a second authority

weakness
CWE-409; CWE-770
affected versions
aiohttp < 3.13.3
also scored by
[email protected] 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

check it yourself github.com github.com receipt

Movement the material steps

6 Jan 20260.0004
15 Jun 20260.00299 · scoring model v2026.06.15
2 Sep 20260.0057
Show all 13 observations
6 Jan 20260.0004
11 Jan 20260.00052
15 Jan 20260.00055
6 Feb 20260.0006
14 Mar 20260.00063
7 May 20260.00082
3 Jun 20260.00057
4 Jun 20260.00055
15 Jun 20260.00299
30 Jun 20260.00487
4 Aug 20260.00505
28 Aug 20260.00517
2 Sep 20260.0057

13 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.0057Published2026-01-05Index as of2026-09-02

The record had been public for 7 months when this index was last written.

Published 2026-01-05 receipt · Index as of 2026-09-02 derived

Siblings and hubs

Records related to this one

Its defect family

aio-libs aiohttp

Of the 2 records in this family, this is the only one whose title names http parser auto_decompress.

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: held values

This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

These are index-wide views, not findings about CVE-2025-69223.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.