CVE-2025-62518: TARmageddon
TARmageddon is a boundary-parsing vulnerability in the Rust async-tar library lineage, including astral-tokio-tar versions before 0.5.6. When a PAX extended header overrides an entry's size, the vulnerable parser advances the archive stream using the ustar header's size instead of the PAX-specified size. A crafted archive can therefore cause file payload bytes, including nested TAR headers, to be interpreted as additional top-level archive entries. This enables archive-entry smuggling and unexpected file extraction, potentially resulting in file overwrites and code execution in downstream applications.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Applications extracting attacker-controlled archives can write smuggled entries into extraction directories and overwrite files accessible to the extracting process. In package installation, build, or container workflows, overwriting configuration or executable content can compromise subsequent processing and potentially cause arbitrary code execution. Differences between archive inspection and extraction can also bypass security scanning or bill-of-materials checks. Credential exposure may be possible depending on how the application processes the extracted entries; code execution and data disclosure are application-dependent rather than guaranteed outcomes.
Mitigation
If you can’t patch tonight, do this now.
No supported workaround is available. Until a patched dependency is deployed, avoid extracting untrusted TAR archives with affected versions. Strict extraction validation and sandboxing with minimal filesystem permissions can reduce potential damage, but do not correct the parsing flaw and should not substitute for upgrading.
Remediation
Patch, then assume compromise.
Upgrade astral-tokio-tar to version 0.5.6 or newer and ensure downstream dependency resolution includes the fixed version. For applications using unmaintained tokio-tar, migrate to a patched, actively maintained fork such as astral-tokio-tar, or remove the vulnerable dependency. The parsing fix uses PAX size overrides when determining entry boundaries and strengthens header consistency and boundary validation.
Exploits
2 exploits validated by Mallory's analysis.
References
Frequently asked questions
- Is CVE-2025-62518 exploited in the wild?
- As of Oct 21, 2026, Mallory has no reports of CVE-2025-62518 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2025-62518?
- Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2025-62518, the earliest disclosed Aug 21, 2025.
- Is there a patch for CVE-2025-62518?
- Upgrade astral-tokio-tar to version 0.5.6 or newer and ensure downstream dependency resolution includes the fixed version. For applications using unmaintained tokio-tar, migrate to a patched, actively maintained fork such as astral-tokio-tar, or remove the vulnerable dependency.
- How severe is CVE-2025-62518?
- CVE-2025-62518 has a CVSS v3.1 score of 8.1 (High) and an EPSS score of 0.70% (54th percentile) as of Oct 21, 2026.
Recent activity
81 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.