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.

The version of rust installed on the remote host is prior to 1.94.0-1. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2-2026-3246 advisory.

    A flaw in the gix-date library can generate invalid non-UTF8 strings, leading to undefined behavior when     processed. The most likely impact from a successful attack is to data integrity, by the malicious data     being able to corrupt data being hold in memory and to system availability as it eventually may lead to     the software using the gix_date library to crash. (CVE-2026-0810)

    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-33055)

    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. (CVE-2026-33056)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2026-1566 advisory.

    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-33055)

    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. (CVE-2026-33056)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2026-1568 advisory.

    A flaw in the gix-date library can generate invalid non-UTF8 strings, leading to undefined behavior when     processed. The most likely impact from a successful attack is to data integrity, by the malicious data     being able to corrupt data being hold in memory and to system availability as it eventually may lead to     the software using the gix_date library to crash. (CVE-2026-0810)

    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-33055)

    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. (CVE-2026-33056)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2026-1565 advisory.

    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-33055)

    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. (CVE-2026-33056)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2026-1567 advisory.

    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-33055)

    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. (CVE-2026-33056)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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-33055)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Severity
306296	Amazon Linux 2 : rust, --advisory ALAS2-2026-3246 (ALAS-2026-3246)	Nessus	Amazon Linux Local Security Checks	medium
306233	Amazon Linux 2023 : cargo-c (ALAS2023-2026-1566)	Nessus	Amazon Linux Local Security Checks	medium
306203	Amazon Linux 2023 : cargo, clippy, rust (ALAS2023-2026-1568)	Nessus	Amazon Linux Local Security Checks	medium
306198	Amazon Linux 2023 : clamav1.5, clamav1.5-data, clamav1.5-devel (ALAS2023-2026-1565)	Nessus	Amazon Linux Local Security Checks	medium
306193	Amazon Linux 2023 : below (ALAS2023-2026-1567)	Nessus	Amazon Linux Local Security Checks	medium
303274	Linux Distros Unpatched Vulnerability : CVE-2026-33055	Nessus	Misc.	medium

Detections

Analytics

CVE-2026-33055

medium

Tenable Plugins

medium

medium

medium

medium

medium

medium