vciy

CVE-2024-8088

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.

Infinite loop when iterating over zip archive entry names from zipfile.Path

CVE-2024-80883 of 4 sources documented this
22

rank 22 = 0 + 22 + 0 + 0 + 0

rank@v1 · backlog

Someone is already using it

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

EPSS 0.01275  ·  without this subject the record ranks 22

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 8.7, from the CNA  ·  without this subject the record ranks 0

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 22

How much of the world it touches

NVD CPE configurations

0 products in the CPE ranges  ·  without this subject the record ranks 22

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$38,900over 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

$38,900 = $4.99M incident cost x 0.6121449559255632 exposure x 0.01275 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.01275EPSSNOT IN KEVas of 2026-09-20
Severity8.7 HIGHreceipt
Harmunauthenticated · networkreceipt
Exploitationnone in held sources
Defensefix version namedreceipt
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2024-08-23, 707 days at 0.01, as of 2026-07-31. 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 Python Software Foundation CPython? 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 complexity · no attack requirementsreceipt
ImpactComplete availability lossreceipt
Scored fromCVSS v4.0 · the CNA's vectorreceipt
Weakness classCWE-835 Loop with Unreachable Exit Condition ('Infinite Loop')receipt
Published consequencesCWE-835: Availability: DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory), DoS: Amplification[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

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

Fixed in3.8.20; 3.9.20; 3.10.15; 3.11.10; 3.12.6; 3.13.0rc2receipt
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 CNA8.7 HIGHreceipt
Exploit probability0.01275 · top 31% of all CVEsreceipt
Assigned byPSFreceipt
Recorded changes57 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productPython Software Foundation CPythonreceipt
Fixed in3.8.20; 3.9.20; 3.10.15; 3.11.10; 3.12.6; 3.13.0rc2receipt

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.

What it is stated by the CNA

There is a HIGH severity vulnerability affecting the CPython "zipfile" module affecting "zipfile.Path". Note that the more common API "zipfile.ZipFile" class is unaffected. When iterating over names of entries in a zip archive (for example, methods of "zipfile.Path" like "namelist()", "iterdir()", etc) the process can be put into an infinite loop with a maliciously crafted zip archive. This defect applies when reading only metadata or extracting the contents of the zip archive. Programs that are not handling user-controlled zip archives are not affected. receipt

NVD's analysis a second authority

weakness
CWE-835
also scored by
[email protected] 8.7 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:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:N/AU:N/R:U/V:X/RE:L/U:X

check it yourself mail.python.org github.com github.com github.com github.com github.com +10 morereceipt

Movement the material steps

23 Aug 20240.00044
17 Mar 20250.00485 · scoring model v2025.03.14
15 Jun 20260.01275 · scoring model v2026.06.15
31 Jul 20260.01275

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 57 observations
23 Aug 20240.00044
5 Sep 20240.00046
17 Mar 20250.00485
18 Mar 20250.00556
20 Mar 20250.00044
22 Mar 20250.00034
27 Mar 20250.00033
28 Mar 20250.00038
29 Mar 20250.00133
30 Mar 20250.00038
27 Apr 20250.00042
8 May 20250.00083
11 May 20250.00064
18 May 20250.00092
21 May 20250.00071
26 May 20250.00068
29 May 20250.00071
8 Jun 20250.00077
15 Jun 20250.001
16 Jun 20250.0009
18 Jun 20250.00106
20 Jun 20250.00091
21 Jun 20250.00087
3 Jul 20250.00091
16 Jul 20250.00117
17 Jul 20250.00106
22 Jul 20250.00087
4 Aug 20250.00091
21 Sep 20250.00106
30 Sep 20250.00178
1 Oct 20250.00179
6 Oct 20250.00162
8 Oct 20250.00166
10 Oct 20250.00143
15 Oct 20250.00166
24 Oct 20250.00143
28 Oct 20250.00139
29 Oct 20250.00143
31 Oct 20250.00166
4 Nov 20250.00226
13 Nov 20250.0022
18 Nov 20250.01971
21 Nov 20250.00226
30 Nov 20250.0022
29 Dec 20250.00244
11 Jan 20260.00332
23 Jan 20260.00285
28 Jan 20260.00341
10 Feb 20260.00332
21 Feb 20260.0018
23 Feb 20260.00154
26 Feb 20260.00198
28 Feb 20260.00237
13 Mar 20260.0023
15 Jun 20260.01275
19 Jul 20260.01264
31 Jul 20260.01275

57 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.01275Published2024-08-22Index as of2026-07-31

Exploit probability more than doubled between 2025-03-28 and 2025-03-29 (0.00038 → 0.00133) and the record had been public for 1 year, 11 months when this index was last written.

Published 2024-08-22 receipt · Index as of 2026-07-31 derived

Siblings and hubs

Records related to this one

Its defect family

python software foundation cpython

Of the 2 records in this family, this is the only one holding a stated fix version: 3.8.20; 3.9.20; 3.10.15; 3.11.10; 3.12.6; 3.13.0rc2.

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-2024-8088.

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.