A high-severity vulnerability in the now-abandoned async-tar Rust library and its forks can be exploited to gain remote code execution on systems running unpatched software. Tracked as CVE-2025-62518, this logic flaw results from a desynchronization issue that allows unauthenticated attackers to inject additional archive entries during TAR file extraction. This occurs specifically when processing nested TAR files with mismatched ustar and PAX extended headers, causing the parser to jump into the file content and mistake it for tar headers, leading to the extraction of attacker-supplied files. Edera, the cybersecurity company that discovered the vulnerability and dubbed it TARmageddon, explains that threat actors can exploit it to overwrite files in supply chain attacks by replacing configuration files and hijacking build backends. This security flaw affects not only projects using async-tar but also tokio-tar, an extremely popular fork with over 7 million downloads on crates.io that has also been abandoned. While the active forks have already been patched, Edera says it's not possible to accurately estimate the impact of this vulnerability due to the widespread nature of its forks, including tokio-tar. "Due to the widespread nature of tokio-tar in various forms, it is not possible to truly quantify upfront the blast radius of this bug across the ecosystem," said Edera. "While the active forks have been successfully patched (see also Astral Security Advisory), this disclosure...
TARmageddon flaw in abandoned Rust library enables RCE attacks
BleepingComputer
·Sergiu Gatlan
·Published Oct 22, 2025
·Updated
Affected Software
2 affected components
Rust async-tar
Rust tokio-tar
Frequently Asked Questions
1
What is the main topic of this article?
The article discusses a high-severity vulnerability in the abandoned async-tar Rust library that allows remote code execution (RCE) attacks.
2
What security implications are discussed regarding the TARmageddon flaw?
The TARmageddon flaw enables unauthenticated attackers to execute arbitrary code on systems using unpatched versions of the affected software.
3
What specific vulnerability is tracked in this article?
The vulnerability is tracked as CVE-2025-62518.
4
Which software products are affected by this vulnerability?
The affected software products are the Rust async-tar library and its fork, the Rust tokio-tar library.
5
Why is the async-tar library described as abandoned in the article?
The async-tar library is labeled as abandoned because it is no longer actively maintained, which raises security risks for users.