RUSTSEC-2026-0068

See a problem?
Please try reporting it to the source first.

Source

https://rustsec.org/advisories/RUSTSEC-2026-0068

Import Source

https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2026-0068.json

JSON Data

https://api.test.osv.dev/v1/vulns/RUSTSEC-2026-0068

Aliases

Published

2026-03-19T12:00:00Z

Modified

2026-03-23T09:45:16.594182Z

Severity

5.1 (Medium) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N CVSS Calculator

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, 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.

Database specific

{
    "license": "CC0-1.0"
}

References

Affected packages

crates.io / tar

Package

Name: tar; View open source insights on deps.dev
Purl: pkg:cargo/tar

Affected ranges

Type: SEMVER
Events: Introduced

0.0.0-0

Fixed

0.4.45

Ecosystem specific

{
    "affected_functions": null,
    "affects": {
        "functions": [],
        "os": [],
        "arch": []
    }
}

Database specific

informational

null