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

Published Mar 17, 2026
·
Updated

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)

Other sources

astral-tokio-tar is a tar archive reading/writing library for async Rust. In versions 0.5.6 and earlier, 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 silently skipping 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. This vulnerability is considered low-severity as it requires a separate vulnerability against any unrelated tar parser. This issue has been fixed in version 0.6.0.

— MITRE

Affected Software

2 affected componentsFixes available
rust/astral-tokio-tar<=0.5.6
0.6.0
astral Astral-tokio-tar Rust<0.6.0

Event History

Mar 17, 2026
Advisory Published
via GitHub·07:49 PM
Data Sourced
via GitHub·07:49 PM
DescriptionWeaknessAffected Software
Mar 20, 2026
CVE Published
via MITRE·12:07 AM
Data Sourced
via MITRE·12:07 AM
DescriptionWeakness
Data Sourced
via NVD·12:16 AM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-32766?

CVE-2026-32766 has a medium severity due to the potential for parser differential attacks.

2

How do I fix CVE-2026-32766?

To fix CVE-2026-32766, upgrade astral-tokio-tar to version 0.6.0 or later.

3

What versions are affected by CVE-2026-32766?

CVE-2026-32766 affects versions 0.5.6 and earlier of astral-tokio-tar.

4

What is the impact of CVE-2026-32766?

The impact of CVE-2026-32766 is the silent skipping of malformed PAX extensions when parsing tar archives.

5

Is CVE-2026-32766 a common vulnerability?

CVE-2026-32766 is specifically related to the astral-tokio-tar package and its handling of tar archives.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203