CVE-2026-32766: astral-tokio-tar insufficiently validates PAX extensions during extraction

CVE-2026-32766 · Severity: medium · CVSS 5.3 · Published 2026-03-17

## Impact

In versions 0.5.6 and earlier of astral-tokio-tar, malformed PAX extensions were silently skipped when parsing tar archives. This silent skipping (rather than rejection) of invalid PAX extensions could be used as a building block for a parser differential, for example by having astral-tokio-tar silently skip a malformed GNU “long link” extension so that a subsequent parser would misinterpret the extension.

In practice, exploiting this behavior in astral-tokio-tar requires a secondary misbehaving tar parser, i.e. one that insufficiently validates malformed PAX extensions and interprets them rather than skipping or erroring on them. Consequently this advisory is considered low-severity within astral-tokio-tar itself, as it requires a separate vulnerability against any unrelated tar parser.

## Patches

Versions 0.6.0 and newer of astral-tokio-tar reject invalid PAX extensions, rather than silently skipping them.

## Workarounds

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

Most users should experience no breaking changes as a result of the patch above. Some users who attempt to extract poorly constructed tar files may experience errors; users should re-construct their tar files with a conforming tar parser.

## Attribution

- Sergei Zimmerman (@xokdvium)

Technologies: astral-tokio-tar (crates.io). Vendors: crates.io.

Quick answers

Is CVE-2026-32766 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-32766 being exploited in the wild.
How severe is CVE-2026-32766?
Medium severity, with a CVSS score of 5.3, published 17 March 2026.
Which products and versions are affected?
astral-tokio-tar (crates.io) <= 0.5.6, SEMVER:introduced=0,fixed=0.6.0, SEMVER:introduced=0.0.0-0,fixed=0.6.0.
Is there a fix for CVE-2026-32766?
Yes. astral-tokio-tar (crates.io): upgrade to 0.6.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-32766?
Check whether you run 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.

How to fix

  • astral-tokio-tar (crates.io): upgrade to 0.6.0 or later
    cargo update -p astral-tokio-tar

Affected products

  • astral-tokio-tar (crates.io) <= 0.5.6, SEMVER:introduced=0,fixed=0.6.0, SEMVER:introduced=0.0.0-0,fixed=0.6.0

Identifiers

  • CVE-2026-32766
  • GHSA-6gx3-4362-rf54
  • RUSTSEC-2026-0066

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.