Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2025-62518: TARmageddon

Published Oct 21, 2025 · Updated 27 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.1High · v3.1
EPSS0.70%54th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2025-62518CWE-436

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

2 exploits validated by Mallory's analysis.

View more in app →
cve-tarmageddonThis repository is a comprehensive, multi-language proof-of-concept for CVE-2025-62518, a critical vulnerability in several Rust async tar libraries (tokio-tar, async-tar, krata-tokio-tar, astral-tokio-tar) related to improper handling of PAX extended header size overrides. The exploit is implemented as a full test suite and reproduction harness: - The core exploit is a specially crafted tar archive (pax_bug_compact.tar) generated by repro_generator/repro_generator.cpp. This archive contains a PAX header specifying a large file size, but a ustar header with size zero, and file content that begins with a valid tar header for a nested file. - The repository includes C++ tools (tarwalk.cpp, tarwalk_bad.cpp) to analyze and compare correct vs buggy parsing behavior, and a Rust tool (tar-bug-detector) to compare the behavior of different tar libraries. - The exploit demonstrates that vulnerable libraries will misinterpret file content as new archive entries, allowing attackers to smuggle or overwrite files during extraction, bypassing manifest validation and potentially leading to code execution or supply chain attacks. - The repository also contains detailed disclosure documentation, technical analysis, and patches for affected libraries. No network endpoints or remote services are involved; the attack is local and targets archive extraction logic, but the impact is significant for supply chain and build systems that process untrusted tar files.edera-dev · Disclosed Aug 21, 2025 · cpp · python · local · supply-chainPoCTarmageddon-CVE-2025-62518-Repository is a Rust proof-of-concept for “TARmageddon” (CVE-2025-62518) affecting the `tokio-tar` crate’s handling of PAX extended headers. Structure/purpose: - `malicious-payload/` (Rust crate): Generates a crafted `malicious.tar` using the `tar` crate. The generator writes a PAX extended header that sets `size=1024` for the next file, then writes a USTAR header for `benign_file.txt` with size set to `0`. It then places a second, valid TAR header for `sh_profile_hijack` inside what should be the benign file’s data region, followed by the smuggled content (`alias ls='rm -rf /'\n`) and proper 512-byte padding and EOF blocks. - `vulnerable-extract/` (Rust crate): Minimal async extractor using `tokio-tar = 0.3.1` that unpacks a user-supplied TAR into `./output`. This demonstrates the vulnerable behavior: the library uses the PAX size for reading content but uses the USTAR size for advancing to the next header, causing a parser/content pointer mismatch and interpreting embedded data as a new header. - `reproduce.sh`: Automates building the payload, showing that GNU tar lists only the benign file, then running the vulnerable extractor to show the extra smuggled file appears in `output/`. Exploit capability: - Not a network exploit; it is a malicious archive that, when processed by vulnerable `tokio-tar`, results in additional attacker-controlled files being written to disk that may evade naive archive inspection/scanning. This can enable supply-chain/CI poisoning or security-tool bypass scenarios where inspection uses correct TAR semantics but extraction uses the vulnerable parser.AirineiAndrei · Disclosed Jan 19, 2026 · rust · bash · local (malicious TAR file processed by a vulnerable extractor/library); supply-chain/CI ingestion scenarioPoC
FAQ

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.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity75Community discussion across Reddit, Mastodon, and other social sources.