astral-tokio-tar is Vulnerable to PAX Header Desynchronization
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
### 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)
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | astral-tokio-tar (crates.io) | before 0.6.1 | 0.6.1 | Patch available | GHSA-fp55-jw48-c537 |
- astral-tokio-tar (crates.io) Vendor— Affected before 0.6.1 Fixed in 0.6.1 Patch available GHSA-fp55-jw48-c537
Remediation
- Fix · GHSA-fp55-jw48-c537 astral-tokio-tar (crates.io) Fixed in 0.6.1 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-fp55-jw48-c537
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences