CVE-2025-8194

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2025-07-28. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

There is a defect in the CPython “tarfile” module affecting the “TarFile” extraction and entry enumeration APIs. The tar implementation would process tar archives with negative offsets without error, resulting in an infinite loop and deadlock during the parsing of maliciously crafted tar archives.

This vulnerability can be mitigated by including the following patch after importing the “tarfile” module:  https://gist.github.com/sethmlarson/1716ac5b82b73dbcbf23ad2eff8b33e1

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
52nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 28, 2025

Last Modified

July 31, 2026

Advisory Details (10)

Auto-updated Jul 30, 2026
Patch available. Sources: github_pr, github_commit.
GitHub commit

commit 73f03e480820 (python/cpython)

Fix landed in python/cpython commit 73f03e480820 — awaiting tagged release

https://github.com/python/cpython/commit/73f03e4808206f71eb6b92c579505a220942ef19
GitHub commit

commit 57f5981d6260 (python/cpython)

Fix landed in python/cpython commit 57f5981d6260 — awaiting tagged release

https://github.com/python/cpython/commit/57f5981d6260ed21266e0c26951b8564cc252bc2
GitHub commit

commit fbc2a0ca9ac8 (python/cpython)

Fix landed in python/cpython commit fbc2a0ca9ac8 — awaiting tagged release

https://github.com/python/cpython/commit/fbc2a0ca9ac8aff6887f8ddf79b87b4510277227
GitHub commit

commit c9d9f78feb14 (python/cpython)

Fix landed in python/cpython commit c9d9f78feb14 — awaiting tagged release

https://github.com/python/cpython/commit/c9d9f78feb1467e73fd29356c040bde1c104f29f
Web page

Mitigation for CVE-2025-8194 · GitHub

https://gist.github.com/sethmlarson/1716ac5b82b73dbcbf23ad2eff8b33e1
GitHub commit

commit cdae923ffe18 (python/cpython)

Fix landed in python/cpython commit cdae923ffe18 — awaiting tagged release

https://github.com/python/cpython/commit/cdae923ffe187d6ef916c0f665a31249619193fe
GitHub commit

commit 7040aa54f146 (python/cpython)

Fix landed in python/cpython commit 7040aa54f146 — awaiting tagged release

https://github.com/python/cpython/commit/7040aa54f14676938970e10c5f74ea93cd56aa38
Web page

Mailman 3 [CVE-2025-8194] Tarfile infinite loop during parsing with negative member offset - Security-announce - python.org

https://mail.python.org/archives/list/[email protected]/thread/ZULLF3IZ726XP5EY7XJ7YIN3K5MDYR2D/
GitHub pull request

gh-130577: tarfile now validates archives to ensure member offsets are non-negative

Fix merged in python/cpython PR #137027 on 2025-07-28 — awaiting tagged release

https://github.com/python/cpython/pull/137027
Web page

`tarfile.StreamError: seeking backwards is not allowed` due to unskipped block with bad checksum · Issue #130577 · python/cpython · GitHub

https://github.com/python/cpython/issues/130577

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhelai1/bootc-azure-amd-rhel9:1.5.4-17610737932025-11-03redhat
redhatrhelai1/bootc-gcp-nvidia-rhel9:1.5.4-17612360792025-11-03redhat
redhatrhelai1/instructlab-nvidia-rhel9:1.5.4-17612202542025-11-03redhat
redhatrhelai1/bootc-aws-nvidia-rhel9:1.5.4-17612361502025-11-03redhat
redhatrhelai1/instructlab-amd-rhel9:1.5.4-17610432272025-11-03redhat
redhatrhelai1/bootc-nvidia-rhel9:1.5.4-17612288382025-11-03redhat
redhatrhelai1/instructlab-intel-rhel9:1.5.4-17610504132025-11-03redhat
redhatrhelai1/bootc-azure-nvidia-rhel9:1.5.4-17612387362025-11-03redhat
redhatrhelai1/bootc-amd-rhel9:1.5.4-17610641792025-11-03redhat
redhatrhelai1/bootc-intel-rhel9:1.5.4-17610606892025-11-03redhat
redhatdiscovery/discovery-server-rhel9:2.2.1-17585559342025-09-23redhat
redhatpython3-0:3.6.8-24.el8_2.42025-09-22redhat
redhatpython3-0:3.6.8-39.el8_4.72025-09-18redhat
redhatpython3-0:3.6.8-51.el8_8.112025-09-18redhat
redhatpython3.9-0:3.9.16-1.el9_2.102025-09-18redhat
redhatpython39:3.9-8080020250908115040.93c2fc2f2025-09-17redhat
redhatpython39:3.9-8040020250909092632.63cd9eba2025-09-17redhat
redhatpython3-0:3.6.8-21.el7_9.22025-09-17redhat
redhatpython39:3.9-8060020250915132015.6a6313992025-09-17redhat
redhatpython3.11-0:3.11.2-2.el8_8.52025-09-17redhat
redhatpython3.11-0:3.11.7-1.el9_4.92025-09-16redhat
redhatpython3.11-0:3.11.2-2.el9_2.72025-09-16redhat
redhatpython3-0:3.6.8-47.el8_6.92025-09-16redhat
redhatpython3.9-0:3.9.10-4.el9_0.72025-09-15redhat
redhatpython3.9-0:3.9.18-3.el9_4.92025-09-15redhat
redhatpython3.12-0:3.12.1-4.el9_4.72025-09-04redhat
redhatpython3.11-0:3.11.11-2.el9_6.22025-09-02redhat
redhatpython3.12-0:3.12.9-2.el10_0.32025-09-02redhat
redhatpython3.9-0:3.9.21-2.el9_6.22025-09-02redhat
redhatpython3.12-0:3.12.9-1.el9_6.22025-09-02redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(9 across 4 ecosystems)
Debian:11(3)
PackageVulnerable rangeFix by version rangeDependents
pypy37.3.10+dfsg-1 ... 7.3.9+dfsg-5 (53 versions)
  • every version on: no fix on record
—
python2.72.7.18-10 ... 2.7.18-9 (10 versions)
  • every version on: no fix on record
—
python3.93.9.2-1, 3.9.2-1+deb11u1, 3.9.2-1+deb11u2, 3.9.2-1+deb11u3
  • every version up to 3.9.2-1+deb11u4: fixed in 3.9.2-1+deb11u4
—
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
pypy37.3.11+dfsg-2 ... 7.3.23+dfsg-1 (29 versions)
  • every version on: no fix on record
—
python3.113.11.2-6 ... 3.11.2-6+deb12u6 (7 versions)
  • every version up to 3.11.2-6+deb12u7: fixed in 3.11.2-6+deb12u7
—
Debian:13(2)
PackageVulnerable rangeFix by version rangeDependents
pypy37.3.19+dfsg-2 ... 7.3.23+dfsg-1 (11 versions)
  • every version on: no fix on record
—
python3.133.13.5-2
  • every version up to 3.13.5-2+deb13u1: fixed in 3.13.5-2+deb13u1
—
Debian:14(2)
PackageVulnerable rangeFix by version rangeDependents
pypy37.3.19+dfsg-2, 7.3.20+dfsg-1, 7.3.20+dfsg-2, 7.3.20+dfsg-3, 7.3.20+dfsg-4
  • every version up to 7.3.21+dfsg-1: fixed in 7.3.21+dfsg-1
—
python3.133.13.5-2
  • every version up to 3.13.6-1: fixed in 3.13.6-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(15)

Data Freshness Timeline

(refreshed 11× in last 7d / 35× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 217 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 119 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  2. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  3. 2026-10-18 05:14 UTCEG score recompute
  4. 2026-10-17 21:29 UTCEG score recompute
  5. 2026-10-17 21:29 UTCVendor advisory
  6. 2026-10-17 21:28 UTCGHSA enrichmentGHSA-v594-44hm-2j7p · GitHub severity HIGH · GitHub CVSS 7.5
  7. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  8. 2026-10-16 16:39 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  9. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  10. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  11. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  12. 2026-10-12 16:44 UTCEG score recompute
  13. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  14. 2026-10-11 20:19 UTCEG score recompute
  15. 2026-10-11 18:31 UTCEG score recompute
  16. 2026-10-11 15:05 UTCEG score recompute
  17. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  18. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  19. 2026-10-10 10:03 UTCOSV refresh
  20. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  21. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  22. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  23. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  24. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  25. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.7% · 50th percentile
Show 73 more
  1. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  2. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  3. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  4. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  5. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  6. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  7. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  8. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  9. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  10. 2026-09-20 19:44 UTCOSV refresh
  11. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  12. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  13. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  14. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  15. 2026-09-15 03:10 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  16. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  17. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  18. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  19. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  20. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  21. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  22. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  23. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  24. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  25. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  26. 2026-09-01 19:35 UTCOSV refresh
  27. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  28. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  29. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  30. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  31. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  32. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  33. 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  34. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  35. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  36. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  37. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  38. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  39. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  40. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  41. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  42. 2026-08-15 21:07 UTCOSV refresh
  43. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  44. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  45. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  46. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  47. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  48. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  49. 2026-08-08 16:36 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  50. 2026-08-07 16:27 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  51. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  52. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  53. 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  54. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  55. 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  56. 2026-08-01 04:15 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  57. 2026-07-31 14:25 UTCEG score recompute
  58. 2026-07-31 14:25 UTCVendor advisory
  59. 2026-07-31 14:25 UTCGHSA enrichmentGHSA-v594-44hm-2j7p · GitHub severity HIGH · GitHub CVSS 7.5
  60. 2026-07-31 14:09 UTCEG score recompute
  61. 2026-07-31 14:09 UTCVendor advisory
  62. 2026-07-31 14:09 UTCGHSA enrichmentGHSA-v594-44hm-2j7p · GitHub severity HIGH · GitHub CVSS 7.5
  63. 2026-07-30 23:20 UTCEG score recompute
  64. 2026-07-30 23:20 UTCVendor advisory
  65. 2026-07-30 23:20 UTCGHSA enrichmentGHSA-v594-44hm-2j7p · GitHub severity HIGH · GitHub CVSS 7.5
  66. 2026-07-30 22:22 UTCEG score recompute
  67. 2026-07-30 22:21 UTCVendor advisory
  68. 2026-07-30 22:21 UTCGHSA enrichmentGHSA-v594-44hm-2j7p · GitHub severity HIGH · GitHub CVSS 7.5
  69. 2026-07-30 16:27 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  70. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  71. 2026-07-27 15:57 UTCOSV refresh
  72. 2026-07-27 14:13 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  73. 2026-07-26 14:54 UTCEPSS rescoreEPSS 0.6% · 45th percentile

Frequently asked(5)

What is CVE-2025-8194?
CVE-2025-8194 is a high-severity vulnerability; its CVE record was published on July 28, 2025. There is a defect in the CPython “tarfile” module affecting the “TarFile” extraction and entry enumeration APIs. The tar implementation would process tar archives with negative offsets without error, resulting in an infinite loop and deadlock during the parsing of maliciously crafted tar archives.…
When was the CVE record for CVE-2025-8194 published?
The CVE record for CVE-2025-8194 was published on July 28, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 31, 2026; the record at its source may have been updated since.
Is CVE-2025-8194 actively exploited?
CVE-2025-8194 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-8194?
CVE-2025-8194 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-8194?
A fix for CVE-2025-8194 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-8194 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-8194

Explore →

Is Your Infrastructure Affected by CVE-2025-8194?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.