Rust advisories / astral-tokio-tar
Vulnerability HighRUSTSEC-2025-0110 · astral-tokio-tar
RUSTSEC-2025-0110: astral-tokio-tar Vulnerable to PAX Header Desynchronization
Short answerA security vulnerability in the astral-tokio-tar crate: astral-tokio-tar Vulnerable to PAX Header Desynchronization. High severity (CVSS 8.1). Fixed in 0.5.6: update to a fixed version.
| Crate | astral-tokio-tar |
|---|---|
| Type | Vulnerability (format-injection) |
| Affected versions | Before 0.5.6. |
| Fixed in | 0.5.6 |
| Severity | High, CVSS 8.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N |
| Published | 2025-10-21 |
| Last changed | 2026-10-12 |
| Also known as | CVE-2025-62518, GHSA-j5gw-2vrg-8fgx, RUSTSEC-2025-0111 |
What to do
- See which version you have:
cargo tree -i astral-tokio-tar(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p astral-tokio-tar. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for exampleastral-tokio-tar = "0.5.6") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
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 vulnerability was disclosed to multiple Rust tar parsers, all derived from the original async-tar fork of tar-rs.
For additional information see Edera's blog post.
References
- Package: crates.io/crates/astral-tokio-tar
- Advisory: rustsec.org/advisories/RUSTSEC-2025-0110.html
- Web: github.com/astral-sh/tokio-tar/commit/22b3f884adb7a2adf1d3a8d03469533f5cbc8318
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Other advisories for astral-tokio-tar
- VulnerabilityRUSTSEC-2026-0066 · 2026-03-17Insufficient validation of PAX extensions during extraction
- VulnerabilityRUSTSEC-2026-0112 · 2026-04-27PAX Header Desynchronization in astral-tokio-tar
- VulnerabilityRUSTSEC-2026-0113 · 2026-04-27`unpack_in` can chmod arbitrary directories by following symlinks
- VulnerabilityRUSTSEC-2026-0145 · 2026-05-18PAX Header Desynchronization in astral-tokio-tar
- VulnerabilityGHSA-3wgq-wrwc-vqmv · 2025-09-23astral-tokio-tar has a path traversal in tar extraction
Up next
Same crateastral-tokio-tar: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?