CVE-2025-62518

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2025-35176 (ENISA EUVD) · GHSA-j5gw-2vrg-8fgx (GitHub Security Advisories)Source: ENISA EUVD

8.1EG
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).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.1Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

astral-tokio-tar is a tar archive reading/writing library for async Rust. Versions of astral-tokio-tar prior to 0.5.6 contain a boundary parsing vulnerability that allows attackers to smuggle additional archive entries by exploiting inconsistent PAX/ustar header handling. When processing archives with PAX-extended headers containing size overrides, the parser incorrectly advances stream position based on ustar header size (often zero) instead of the PAX-specified size, causing it to interpret file content as legitimate tar headers. This issue has been patched in version 0.5.6. There are no workarounds.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
52
EG Risk 52/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)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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
53rd
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 (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 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 (model v2026.06.15, score date 2026-10-31). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

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

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

October 21, 2025

Last Modified

October 8, 2026

Advisory Details (5)

Auto-updated Sep 18, 2026
Patch available. Sources: github_commit, github.
Web page

GitHub - edera-dev/cve-tarmageddon: CVE-2025-62518: TARmageddon · GitHub

https://github.com/edera-dev/cve-tarmageddon
GitHub advisoryMentions a patch (unverified)

Differential in tar extraction with PAX headers · Advisory · astral-sh/uv · GitHub

https://github.com/astral-sh/uv/security/advisories/GHSA-w476-p2h3-79g9
GitHub advisoryMentions a patch (unverified)

PAX Header Desynchronization in astral-tokio-tar · Advisory · astral-sh/tokio-tar · GitHub

https://github.com/astral-sh/tokio-tar/security/advisories/GHSA-j5gw-2vrg-8fgx
GitHub commit Patch Available

commit 22b3f884adb7 (astral-sh/tokio-tar)

Patch available: astral-sh/tokio-tar v0.5.6 (contains commit 22b3f884adb7)

https://github.com/astral-sh/tokio-tar/commit/22b3f884adb7a2adf1d3a8d03469533f5cbc8318
Web page

CVE-2025-62518 Shows the Cost of Open Source Abandonware

https://edera.dev/stories/tarmageddon

Vendor Advisories for CVE-2025-62518(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
rustastral-tokio-tar @ 0.5.6 (fixes <= 0.5.5)—ghsa
rusttokio-tar—ghsa

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

(4 across 3 ecosystems)
crates.io(2)
PackageVulnerable rangeFix by version rangeDependents
astral-tokio-tar—
  • every version up to 0.5.6: fixed in 0.5.6
  • 0.0.0-0 up to 0.5.6: fixed in 0.5.6
—
tokio-tar—
  • every version through 0.3.1: no fix on record
  • 0.0.0-0 on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rust-astral-tokio-tar0.5.2-2 ... 0.6.4-1 (8 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rust-astral-tokio-tar0.5.2-2, 0.5.5-1
  • every version up to 0.5.6-1: fixed in 0.5.6-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 41× 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 95 of 224 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. 5 repeat rows among the latest 100 are merged into the row they repeat. The 129 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • GitHub PoCedera-dev/cve-tarmageddon
    Published Aug 21, 2025

    CVE-2025-62518: TARmageddon

    Open source ↗

Frequently asked(5)

What is CVE-2025-62518?
CVE-2025-62518 is a high-severity vulnerability; its CVE record was published on October 21, 2025. astral-tokio-tar is a tar archive reading/writing library for async Rust. Versions of astral-tokio-tar prior to 0.5.6 contain a boundary parsing vulnerability that allows attackers to smuggle additional archive entries by exploiting inconsistent PAX/ustar header handling. When processing archives…
When was the CVE record for CVE-2025-62518 published?
The CVE record for CVE-2025-62518 was published on October 21, 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 October 8, 2026; the record at its source may have been updated since.
Is CVE-2025-62518 actively exploited?
CVE-2025-62518 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-62518?
CVE-2025-62518 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-62518?
A fix for CVE-2025-62518 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-62518 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-62518

Explore →

Is Your Infrastructure Affected by CVE-2025-62518?

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