Skip to content
Fencer Intel
low —

GHSA-xx64-wwv2-hcqq json

astral-tokio-tar: `unpack_in` can chmod arbitrary directories by following symlinks

published 6mo ago modified last mo. also RUSTSEC-2026-0113

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

In versions 0.6.0 and earlier of astral-tokio-tar, the `unpack_in` API could inadvertently modify the permissions of external (i.e. non-archive) directories outside of the archive. An attacker could use this to contrite a tar archive that maliciously changes directory permissions outside of its intended hierarchy. This flaw only affects directories; individual file permissions cannot be modified via it.

See GHSA-j4xf-2g29-59ph for the equivalent flaw in the `tar` crate.

### Patches

Versions 0.6.1 and newer of astral-tokio-tar use `fs::symlink_metdata` rather than `fs::metadata`, avoiding the traversal.

### Workarounds

Users are advised to upgrade to version 0.6.1 or newer to address this advisory.

Users should experience no breaking changes as a result of the patch above.

### Resources

- GHSA-j4xf-2g29-59ph for the original `tar` vulnerability

### Attribution

- Reporter: Adam Harvey (@lawngnome)

Patch / fix

  • crates.io astral-tokio-tar 0.6.1

Is GHSA-xx64-wwv2-hcqq 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-61 UNIX Symbolic Link (Symlink) Following

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.