Rust advisories / crate
Security history · astral-tokio-tar · data from Oct 24, 2026
Is astral-tokio-tar safe to use? Its security history
VerdictNo open advisories. 6 past vulnerabilities were fixed; use 0.6.2 or newer to be clear of all of them.
6advisories on record
6vulnerabilities
0unmaintained notices
0.6.2newest fixed version
Every advisory, newest first
- VulnerabilityRUSTSEC-2026-0145 · 2026-05-18PAX Header Desynchronization in astral-tokio-tar
- 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-0066 · 2026-03-17Insufficient validation of PAX extensions during extraction
- Vulnerability HighRUSTSEC-2025-0110 · 2025-10-21astral-tokio-tar Vulnerable to PAX Header Desynchronization
- VulnerabilityGHSA-3wgq-wrwc-vqmv · 2025-09-23astral-tokio-tar has a path traversal in tar extraction
Check your version
Run cargo tree -i astral-tokio-tar to see which version you build and why, or paste your Cargo.lock into the Cargo.toml checker to match every advisory against your exact versions.
RustSec advisories (CC0-1.0) and GitHub-reviewed advisories via OSV's crates.io export, downloaded Oct 24, 2026.
Up next
Are you affected?Check your whole dependency treeRead it next →Also worth your time
Did this answer your question?