astral-tokio-tar is Vulnerable to PAX Header Desynchronization
Affects astral-tokio-tarSource GCVE Database
CVSS 8.7 High : upgrade to 0.6.1 soon.
Data as of 27 Oct 2026, 00:07 UTC
- Patch
- Available – fixed in 0.6.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:UWhat to do
Upgrade astral-tokio-tar to 0.6.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| crates.ioastral-tokio-tar | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
### Impact Versions of astral-tokio-tar prior to 0.6.1 contain a PAX header interpretation bug that allows manipulated entries to be made selectively visible or invisible during extraction with astral-tokio-tar versus other tar implementations. An attacker could use this differential to smuggle unexpected files onto a victim's filesystem. See GHSA-j5gw-2vrg-8fgx for a similar desynchronization bug in astral-tokio-tar. ### Patches Versions 0.6.1 and newer of astral-tokio-tar address this differential. ### Workarounds Users are advised to upgrade to version 0.6.1 or newer to address this advisory. There is no workaround other than upgrading. Users should experience no breaking changes as a result of the upgrade. ### Resources - GHSA-j5gw-2vrg-8fgx is a similar PAX desynchronization bug ### Attribution - Reporter: Adam Harvey (@lawngnome)