GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR archives, with a certain two-step process. First, the victim must extract an archive that contains a ../ symlink to a critical directory. Second, the victim must extract an archive that contains a critical file, specified via a relative pathname that begins with the symlink name and ends with that critical file's name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of "Member name contains '..'" that would occur for a single TAR archive that attempted to specify the critical file via a ../ approach. For example, the first archive can contain "x -> ../../../../../home/victim/.ssh" and the second archive can contain x/authorized_keys. This can affect server applications that automatically extract any number of user-supplied TAR archives, and were relying on the blocking of traversal. This can also affect software installation processes in wh
CVE-2025-45582 is fixed in 2 products on 1 platform, first by RHSA-2026:0135, released July 11, 2025. It is not reported as exploited. Patch Radar priority: Routine.
The GNU tar program can save multiple files in an archive and restore files from an archive. Security Fix(es): * tar: Tar path traversal (CVE-2025-45582) * tar: tar: Hidden file injection via crafted archives (CVE-2026-5704) * tar: tar: TOCTOU in incremental dumpdir 'X' rename handling allows restore path escape (CVE-2026-18477) * tar: tar: --one-top-level hardlink targets not confined to top-level directory enabling arbitrary file overwrite (CVE-2026-18508) Bug Fix(es) and Enhancement(s): * tar: --one-top-level with absolute path fails [rhel-8.10.z] (JIRA:RHEL-144019) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| tar · RHEL 10 | 1.35-7.el10_0.2 | RHSA-2026:0135 | Jul 11, 2025 |
| tar · RHEL 8 | 2:1.30-13.el8_10 | RHSA-2026:70390 | Sep 23, 2026 |
| tar · RHEL 9 | 2:1.34-9.el9_7 | RHSA-2026:0067 | Jan 16, 2026 |
| tar · Ubuntu 22.04.1 LTS (jammy) | 1.34+dfsg-1ubuntu0.1.22.04.4 | tar 1.34+dfsg-1ubuntu0.1.22.04.4 | Jul 11, 2025 |
| tar · Ubuntu 24.04.5 LTS (noble) | 1.35+dfsg-3ubuntu0.2 | tar 1.35+dfsg-3ubuntu0.2 | Jul 11, 2025 |
| tar · Ubuntu 26.04.1 LTS (resolute) | 1.35+dfsg-4ubuntu0.2 | tar 1.35+dfsg-4ubuntu0.2 | Jul 11, 2025 |
| tar · almalinux 10 | 2:1.35-9.el10_1 | ALSA-2026:0002 | Jan 5, 2026 |
| tar · almalinux 8 | 2:1.30-13.el8_10 | ALSA-2026:70390 | Sep 22, 2026 |
| tar · almalinux 9 | 2:1.34-9.el9_7 | ALSA-2026:0067 | Jan 5, 2026 |
| tar · ol 10 | 2:1.35-9.el10_1 | ELSA-2026-0002 | Jan 5, 2026 |
| tar · ol 8 | 2:1.30-13.el8_10 | ELSA-2026-70390 | Sep 23, 2026 |
| tar · ol 9 | 2:1.34-9.el9_7 | ELSA-2026-0067 | Jan 5, 2026 |
| tar · opensuse-leap 15.6 | 1.34-150000.3.37.1 | SUSE-SU-2026:1177-1 | Apr 2, 2026 |
| tar · opensuse-leap 16.0 | 1.35-160000.4.1 | OPENSUSE-SU-2026:21070-1 | Jun 26, 2026 |
| tar · rocky 10 | 2:1.35-9.el10_1 | RLSA-2026:0002 | Jan 5, 2026 |
| tar · rocky 8 | 2:1.30-13.el8_10 | RLSA-2026:70390 | Sep 24, 2026 |
| tar · rocky 9 | 2:1.34-9.el9_7 | RLSA-2026:0067 | Jan 6, 2026 |
| tar · sles 15.6 | 1.34-150000.3.37.1 | SUSE-SU-2026:1177-1 | Apr 2, 2026 |
| tar · sles 15.7 | 1.34-150000.3.37.1 | SUSE-SU-2026:1177-1 | Apr 2, 2026 |
| tar · sles 16.0 | 1.35-160000.4.1 | SUSE-SU-2026:22377-1 | Jun 26, 2026 |
| tar-scripts · Ubuntu 22.04.1 LTS (jammy) | 1.34+dfsg-1ubuntu0.1.22.04.4 | tar-scripts 1.34+dfsg-1ubuntu0.1.22.04.4 | Jul 11, 2025 |
| tar-scripts · Ubuntu 24.04.5 LTS (noble) | 1.35+dfsg-3ubuntu0.2 | tar-scripts 1.35+dfsg-3ubuntu0.2 | Jul 11, 2025 |
| tar-scripts · Ubuntu 26.04.1 LTS (resolute) | 1.35+dfsg-4ubuntu0.2 | tar-scripts 1.35+dfsg-4ubuntu0.2 | Jul 11, 2025 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.