Name
tar
Version
1.35
Type
library
Description
GNU file archiving program
Licenses
GPL-3.0-only
PURL
-
CPE
cpe:2.3:*:gnu:tar:1.35:*:*:*:*:*:*:*
Other Versions#
Patches#
#
Title
Author
Resolve
1
Fix more -t/-x discrepancies
Paul Eggert <eggert@cs.ucla.edu>
CVE-2026-5704
2
Avoid acl_ prefix for functions
Pavel Cahyna <pcahyna@redhat.com>
3
tests: fix TESTSUITE_AT
Paul Eggert <eggert@cs.ucla.edu>
4
--no-overwrite-dir no overwrite even temporarily
Paul Eggert <eggert@cs.ucla.edu>
CVE-2026-5704
5
tests: check for recently-fixed bug
Paul Eggert <eggert@cs.ucla.edu>
6
Handle directory members consistently when listing and when
Sergey Poznyakoff <gray@gnu.org>
CVE-2026-5704
7
Exclude VCS directory with writing from an archive
Anton Makrushin <makrusan@gmail.com>
8
Prefer other types to int in extract.c
Paul Eggert <eggert@cs.ucla.edu>
CVE-2026-5704
Vulnerabilities#
Name
Analysis
Description
Patched
A flaw was found in tar. A remote attacker could exploit this vulnerability by crafting a malicious archive, leading to hidden file injection with fully attacker-controlled content. This bypasses pre-extraction inspection mechanisms, potentially allowing an attacker to introduce malicious files onto a system without detection.
Exploitable
A flaw was found in GNU tar. When extracting an archive with the --one-top-level option, hardlink targets are not confined to the designated top-level directory and may resolve relative to the extraction working directory. A crafted archive can create hardlinks that escape the intended boundary and, when combined with a preexisting symbolic link under the working directory, may allow writing outside that boundary during a single extraction.
Exploitable
A TOCTOU (Time-of-Check Time-of-Use) vulnerability in GNU tar's incremental dumpdir 'X' rename handling allows a local attacker with write access to a directory being backed up to influence the restore process if the attacker has access to the system where the restore is being performed. During restoration, files or directories may be created, renamed or overwritten outside the intended extraction directory. This could lead to unauthorized file modification or, in some cases, privilege escalation. Exploitation does not require the attacker to modify or craft the archive, and standard backup and restore workflows—including extracting into a newly created directory without using the -P option do not mitigate the issue.