rust-tar - Debian Package Tracker

general

source: rust-tar (main)
version: 0.4.45-2
maintainer: Debian Rust Maintainers (archive) (DMD)
uploaders: Wolfgang Silbermayr [DMD] – Ximin Luo [DMD]
arch: any
std-ver: 4.7.3
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 0.4.26-1
oldstable: 0.4.38-1
stable: 0.4.43-4
testing: 0.4.45-2
unstable: 0.4.45-2

versioned links

0.4.26-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
0.4.38-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
0.4.43-4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
0.4.45-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

librust-tar-dev

action needed

A new upstream version is available: 0.4.46 high

A new upstream version 0.4.46 is available, you should consider packaging it.

Created: 2026-05-22 Last update: 2026-08-16 15:01

1 security issue in trixie high

There is 1 open security issue in trixie.

1 important issue:

CVE-2026-70622: tar-rs versions 0.4.11 through 0.4.46 contain a symlink escape vulnerability in the Builder::append_dir_all() function that allows attackers to read files outside the intended source root directory by planting symlinks in an attacker-controlled directory. When a privileged process archives an untrusted directory, the function follows symlinks without verifying that resolved targets remain within the source root, causing out-of-bounds files to be included in the archive as regular files and disclosed to the attacker.

2 issues that should be fixed with the next stable update:

CVE-2026-33055: 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.
CVE-2026-33056: tar-rs is a tar archive reading/writing library for Rust. In versions 0.4.44 and below, when unpacking a tar archive, the tar crate's unpack_dir function uses fs::metadata() to check whether a path that already exists is a directory. Because fs::metadata() follows symbolic links, a crafted tarball containing a symlink entry followed by a directory entry with the same name causes the crate to treat the symlink target as a valid existing directory — and subsequently apply chmod to it. This allows an attacker to modify the permissions of arbitrary directories outside the extraction root. This issue has been fixed in version 0.4.45.

Created: 2026-08-12 Last update: 2026-08-14 20:30

1 security issue in sid high

There is 1 open security issue in sid.

1 important issue:

CVE-2026-70622: tar-rs versions 0.4.11 through 0.4.46 contain a symlink escape vulnerability in the Builder::append_dir_all() function that allows attackers to read files outside the intended source root directory by planting symlinks in an attacker-controlled directory. When a privileged process archives an untrusted directory, the function follows symlinks without verifying that resolved targets remain within the source root, causing out-of-bounds files to be included in the archive as regular files and disclosed to the attacker.

Created: 2026-08-12 Last update: 2026-08-14 20:30

1 security issue in forky high

There is 1 open security issue in forky.

1 important issue:

CVE-2026-70622: tar-rs versions 0.4.11 through 0.4.46 contain a symlink escape vulnerability in the Builder::append_dir_all() function that allows attackers to read files outside the intended source root directory by planting symlinks in an attacker-controlled directory. When a privileged process archives an untrusted directory, the function follows symlinks without verifying that resolved targets remain within the source root, causing out-of-bounds files to be included in the archive as regular files and disclosed to the attacker.

Created: 2026-08-12 Last update: 2026-08-14 20:30

4 security issues in bullseye high

There are 4 open security issues in bullseye.

1 important issue:

CVE-2026-70622: tar-rs versions 0.4.11 through 0.4.46 contain a symlink escape vulnerability in the Builder::append_dir_all() function that allows attackers to read files outside the intended source root directory by planting symlinks in an attacker-controlled directory. When a privileged process archives an untrusted directory, the function follows symlinks without verifying that resolved targets remain within the source root, causing out-of-bounds files to be included in the archive as regular files and disclosed to the attacker.

3 issues postponed or untriaged:

CVE-2021-38511: (needs triaging) An issue was discovered in the tar crate before 0.4.36 for Rust. When symlinks are present in a TAR archive, extraction can create arbitrary directories via .. traversal.
CVE-2026-33055: (postponed; to be fixed through a stable update) 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.
CVE-2026-33056: (postponed; to be fixed through a stable update) tar-rs is a tar archive reading/writing library for Rust. In versions 0.4.44 and below, when unpacking a tar archive, the tar crate's unpack_dir function uses fs::metadata() to check whether a path that already exists is a directory. Because fs::metadata() follows symbolic links, a crafted tarball containing a symlink entry followed by a directory entry with the same name causes the crate to treat the symlink target as a valid existing directory — and subsequently apply chmod to it. This allows an attacker to modify the permissions of arbitrary directories outside the extraction root. This issue has been fixed in version 0.4.45.

Created: 2026-08-12 Last update: 2026-08-14 20:30

3 security issues in bookworm high

There are 3 open security issues in bookworm.

1 important issue:

CVE-2026-70622: tar-rs versions 0.4.11 through 0.4.46 contain a symlink escape vulnerability in the Builder::append_dir_all() function that allows attackers to read files outside the intended source root directory by planting symlinks in an attacker-controlled directory. When a privileged process archives an untrusted directory, the function follows symlinks without verifying that resolved targets remain within the source root, causing out-of-bounds files to be included in the archive as regular files and disclosed to the attacker.

2 issues postponed or untriaged:

CVE-2026-33055: (postponed; to be fixed through a stable update) 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.
CVE-2026-33056: (postponed; to be fixed through a stable update) tar-rs is a tar archive reading/writing library for Rust. In versions 0.4.44 and below, when unpacking a tar archive, the tar crate's unpack_dir function uses fs::metadata() to check whether a path that already exists is a directory. Because fs::metadata() follows symbolic links, a crafted tarball containing a symlink entry followed by a directory entry with the same name causes the crate to treat the symlink target as a valid existing directory — and subsequently apply chmod to it. This allows an attacker to modify the permissions of arbitrary directories outside the extraction root. This issue has been fixed in version 0.4.45.

Created: 2026-08-12 Last update: 2026-08-14 20:30

lintian reports 1 warning normal

Lintian reports 1 warning about this package. You should make the package lintian clean getting rid of them.

Created: 2026-03-27 Last update: 2026-03-27 09:31

debian/patches: 3 patches to forward upstream low

Among the 3 debian patches available in version 0.4.45-2 of the package, we noticed the following issues:

3 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2023-02-26 Last update: 2026-03-27 10:30

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.4 instead of 4.7.3).

Created: 2026-03-31 Last update: 2026-03-31 15:01

news

[rss feed]

[2026-03-30] rust-tar 0.4.45-2 MIGRATED to testing (Debian testing watch)
[2026-03-26] Accepted rust-tar 0.4.45-2 (source) into unstable (Yifei Zhan)
[2026-03-26] rust-tar 0.4.45-1 MIGRATED to testing (Debian testing watch)
[2026-03-23] Accepted rust-tar 0.4.45-1 (source) into unstable (Fabian Grünbichler) (signed by: Fabian Gruenbichler)
[2025-08-29] rust-tar 0.4.44-1 MIGRATED to testing (Debian testing watch)
[2025-08-27] Accepted rust-tar 0.4.44-1 (source) into unstable (Christopher Hoskin)
[2024-11-16] rust-tar 0.4.43-4 MIGRATED to testing (Debian testing watch)
[2024-11-11] Accepted rust-tar 0.4.43-4 (source) into unstable (Fabian Grünbichler)
[2024-11-10] Accepted rust-tar 0.4.43-3 (source) into unstable (Fabian Grünbichler)
[2024-11-08] Accepted rust-tar 0.4.43-2 (source) into unstable (Fabian Grünbichler)
[2024-11-05] Accepted rust-tar 0.4.43-1 (source) into unstable (Fabian Grünbichler)
[2024-01-18] rust-tar 0.4.40-1 MIGRATED to testing (Debian testing watch)
[2024-01-16] Accepted rust-tar 0.4.40-1 (source) into unstable (Peter Michael Green)
[2023-07-19] rust-tar 0.4.38-2 MIGRATED to testing (Debian testing watch)
[2023-07-09] Accepted rust-tar 0.4.38-2 (source) into unstable (Sylvestre Ledru)
[2022-10-23] rust-tar 0.4.38-1 MIGRATED to testing (Debian testing watch)
[2022-10-21] Accepted rust-tar 0.4.38-1 (source) into unstable (Fabian Gruenbichler) (signed by: James McCoy)
[2021-11-12] rust-tar 0.4.37-3 MIGRATED to testing (Debian testing watch)
[2021-11-09] Accepted rust-tar 0.4.37-3 (source) into unstable (Peter Michael Green)
[2021-11-09] Accepted rust-tar 0.4.37-2 (source) into unstable (Peter Michael Green)
[2021-10-23] Accepted rust-tar 0.4.37-1 (source) into unstable (Ximin Luo) (signed by: infinity0@debian.org)
[2020-04-15] rust-tar 0.4.26-1 MIGRATED to testing (Debian testing watch)
[2020-03-25] rust-tar REMOVED from testing (Debian testing watch)
[2019-07-16] rust-tar 0.4.26-1 MIGRATED to testing (Debian testing watch)
[2019-07-11] Accepted rust-tar 0.4.26-1 (source) into unstable (Wolfgang Silbermayr)
[2018-12-21] rust-tar 0.4.20-1 MIGRATED to testing (Debian testing watch)
[2018-12-15] Accepted rust-tar 0.4.20-1 (amd64 source) into unstable (Wolfgang Silbermayr)
[2018-10-12] rust-tar 0.4.17-1 MIGRATED to testing (Debian testing watch)
[2018-10-07] Accepted rust-tar 0.4.17-1 (source) into unstable (Wolfgang Silbermayr) (signed by: Sylvestre Ledru)
[2018-08-05] rust-tar 0.4.16-1 MIGRATED to testing (Debian testing watch)

bugs [bug history graph]

all: 1
RC: 0
I&N: 1
M&W: 0
F&P: 0
patch: 0

links

homepage
lintian (0, 1)
buildd: logs, reproducibility, cross
popcon
browse source code
other distros
security tracker
debian patches
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 0.4.45-2