Skip to content
Fencer Intel
medium —

GHSA-fp55-jw48-c537 json

astral-tokio-tar is Vulnerable to PAX Header Desynchronization

published 6mo ago modified 30d ago also RUSTSEC-2026-0112

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

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)

Patch / fix

  • crates.io astral-tokio-tar 0.6.1

Is GHSA-fp55-jw48-c537 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
crates.io astral-tokio-tar
<0.6.1
>=0.0.0-0, <0.6.1
0.6.1

Classification

Weakness
  • CWE-20 Improper Input Validation
  • CWE-843 Access of Resource Using Incompatible Type

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.