CVE-2026-33055: tar-rs incorrectly ignores PAX size headers if header size is nonzero

Severity: high (CVSS 8.1 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.4% probability of exploitation in the next 30 days
Public exploit or detection template: yes
Published: 2026-03-20 · updated 2026-06-17
Weakness: CWE-843

Description

tar-rs is a tar archive reading/writing library for Rust. Versions 0.4.44 and below have conditional logic that skips the PAX size header in cases where the base header size is nonzero. As part of CVE-2025-62518, 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) 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.

Affected products

alexcrichton tar-rs: before 0.4.45 — fixed in 0.4.45

How to fix

Upgrade to a fixed version: alexcrichton tar-rs 0.4.45. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2026-33055 or the next vulnerability affects your stack