Advisory

RUSTSEC-2026-0068

Also known as: CVE-2026-33055, GHSA-gchp-q4r4-x4ff

Summary

tar-rs incorrectly ignores PAX size headers if header size is nonzero

Details

Versions 0.4.44 and below of tar-rs have conditional logic that skips the PAX
size header in cases where the base header size is nonzero.

As part of [CVE-2025-62518][astral-cve], the [astral-tokio-tar]
project was changed to correctly honor PAX size headers in the case where it
was different from the base header. This is almost the inverse of the
astral-tokio-tar issue.

Any discrepancy in how tar parsers honor file size can be used to create
archives that appear differently when unpacked by different archivers. In this
case, the tar-rs (Rust tar) crate is an outlier in checking for the header size
— other tar parsers (including e.g. Go [archive/tar][go-tar]) unconditionally
use the PAX size override. This can affect anything that uses the tar crate to
parse archives and expects to have a consistent view with other parsers.

This issue has been fixed in version 0.4.45.

[astral-cve]: https://www.cve.org/CVERecord?id=CVE-2025-62518
[astral-tokio-tar]: https://github.com/astral-sh/tokio-tar
[go-tar]: https://pkg.go.dev/archive/tar

Severity

Not rated by the source.

Dates

Published
2026-03-19 12:00 UTC
Modified
2026-03-23 09:45 UTC

Affected packages and fixes

tar

crates.io · All systems

Affected

  • introduced 0.0.0-0, fixed 0.4.45 (semver)

Fixed versions

0.4.45

Fix

  • Fixed version 0.4.45
    cargo update -p tar --precise 0.4.45

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences