Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Medium severity, with a CVSS score of 6.9, published 29 May 2026.
- Which products and versions are affected?
- Astral Tokio-Tar <= 0.6.1; astral-tokio-tar (crates.io) <= 0.6.1.
- Is there a fix for This vulnerability?
- A patch was published on 2026-05-29: Version 0.6.2 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run Astral Tokio-Tar or astral-tokio-tar (crates.io) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The astral-tokio-tar library incorrectly applies PAX headers ('x') to the immediate next entry in a tar stream regardless of its type, violating the POSIX pax specification which requires PAX headers to apply only to file entries. By inserting intermediary entries like GNU longname ('L') headers between a PAX header and a file, an attacker can cause a desynchronization of the stream. This differential in parsing allows an attacker to craft archives where specific members are skipped or extracted differently by astral-tokio-tar compared to other tar implementations. This vulnerability is classified as Improper Input Validation (CWE-20) and Type Confusion (CWE-843). The issue is resolved in version 0.6.2.
Affected products
- Astral astral-tokio-tar <= 0.6.1
Timeline
- 2026-05-18: disclosed: Initial disclosure to maintainers
- 2026-05-29: advisory: GitHub Advisory published
- 2026-05-29: patched: Version 0.6.2 released