{"id":"CVE-2025-45582","aliases":["ALSA-2026:0002","ALSA-2026:0067","ALSA-2026:70390","AZL-65082","AZL-65538","BELL-CVE-2025-45582","CLSA-2026-1769513855","CLSA-2026-1769598463","EUVD-2025-21178","GHSA-f93m-9mq4-2fjj","JLSEC-2025-197","MGASA-2026-0401","OESA-2026-1091","OESA-2026-1092","OESA-2026-1093","OESA-2026-1094","OESA-2026-1095","OESA-2026-1096","RHSA-2026:0002","RHSA-2026:0067","RHSA-2026:0135","RHSA-2026:0434","RHSA-2026:0435","RHSA-2026:70390","RLSA-2026:0002","RLSA-2026:0067","RLSA-2026:70390","SUSE-SU-2026:1177-1","SUSE-SU-2026:20955-1","SUSE-SU-2026:20959-1","SUSE-SU-2026:21002-1","SUSE-SU-2026:21143-1","SUSE-SU-2026:22289-1","SUSE-SU-2026:22377-1","SUSE-SU-2026:2615-1","UBUNTU-CVE-2025-45582","USN-8510-1","openSUSE-SU-2026:10743-1","openSUSE-SU-2026:20472-1","openSUSE-SU-2026:21070-1"],"status":"published","title":"GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR archives, with...","description":"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 -\u003e ../../../../../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 which \"tar xf\" is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages). NOTE: the official GNU Tar manual has an otherwise-empty directory for each \"tar xf\" in its Security Rules of Thumb; however, third-party advice leads users to run \"tar xf\" more than once into the same directory.","severity":{"version":"3.1","score":4.1,"vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:N/I:L/A:L","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-10","score":0.0049,"percentile":0.42487,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-24"],"published":"2025-07-11T00:00:00Z","modified":"2026-10-29T11:58:14Z","fixes":[{"ecosystem":"AlmaLinux:10","package":"tar","fixed_in":["2:1.35-9.el10_1"],"sources":["osv"]},{"ecosystem":"AlmaLinux:9","package":"tar","fixed_in":["2:1.34-9.el9_7"],"sources":["osv"]},{"ecosystem":"TuxCare:AlmaLinux:9.6","package":"tar","fixed_in":["2:1.34-7.el9.tuxcare.els1"],"sources":["osv"]},{"ecosystem":"TuxCare:AlmaLinux:9.2","package":"tar","fixed_in":["2:1.34-7.el9.tuxcare.els1"],"sources":["osv"]},{"ecosystem":"Julia","package":"Tar_jll","fixed_in":["1.35.0+0"],"sources":["osv"]},{"ecosystem":"openEuler:22.03-LTS-SP4","package":"tar","fixed_in":["1.34-6.oe2203sp4"],"sources":["osv"]},{"ecosystem":"openEuler:24.03-LTS","package":"tar","fixed_in":["1.35-3.oe2403"],"sources":["osv"]},{"ecosystem":"openEuler:24.03-LTS-SP1","package":"tar","fixed_in":["1.35-3.oe2403sp1"],"sources":["osv"]},{"ecosystem":"openEuler:24.03-LTS-SP2","package":"tar","fixed_in":["1.35-3.oe2403sp2"],"sources":["osv"]},{"ecosystem":"openEuler:24.03-LTS-SP3","package":"tar","fixed_in":["1.35-3.oe2403sp3"],"sources":["osv"]},{"ecosystem":"openEuler:22.03-LTS-SP3","package":"tar","fixed_in":["1.34-6.oe2203sp3"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:10.1","package":"tar","fixed_in":["2:1.35-9.el10_1"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:10.1","package":"tar-debuginfo","fixed_in":["2:1.35-9.el10_1"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:10.1","package":"tar-debugsource","fixed_in":["2:1.35-9.el10_1"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"tar","fixed_in":["2:1.34-9.el9_7"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"tar-debuginfo","fixed_in":["2:1.34-9.el9_7"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"tar-debugsource","fixed_in":["2:1.34-9.el9_7"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux_eus:10.0","package":"tar","fixed_in":["2:1.35-7.el10_0.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_eus:9.4::baseos","package":"tar","fixed_in":["2:1.34-6.el9_4.3"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_eus:9.4::baseos","package":"tar-debuginfo","fixed_in":["2:1.34-6.el9_4.3"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_eus:9.4::baseos","package":"tar-debugsource","fixed_in":["2:1.34-6.el9_4.3"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_eus:9.6::baseos","package":"tar","fixed_in":["2:1.34-7.el9_6.2"],"sources":["osv"]},{"ecosystem":"Rocky Linux:10","package":"tar","fixed_in":["2:1.35-9.el10_1"],"sources":["osv"]},{"ecosystem":"Rocky Linux:9","package":"tar","fixed_in":["2:1.34-9.el9_7"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Micro 5.3","package":"tar","fixed_in":["1.34-150000.3.37.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Micro 5.4","package":"tar","fixed_in":["1.34-150000.3.37.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"tar","fixed_in":["1.34-150000.3.37.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP7","package":"tar","fixed_in":["1.34-150000.3.37.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"tar","fixed_in":["1.34-150000.3.37.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"tar","fixed_in":["1.34-150000.3.37.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"tar","fixed_in":["1.34-150000.3.37.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"tar","fixed_in":["1.34-150000.3.37.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"tar","fixed_in":["1.34-150000.3.37.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"tar","fixed_in":["1.34-150000.3.37.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Server 15 SP6-LTSS","package":"tar","fixed_in":["1.34-150000.3.37.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"tar","fixed_in":["1.34-150000.3.37.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"tar","fixed_in":["1.34-150000.3.37.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP6","package":"tar","fixed_in":["1.34-150000.3.37.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Micro 5.2","package":"tar","fixed_in":["1.34-150000.3.37.1"],"sources":["osv"]},{"ecosystem":"openSUSE:Leap 15.6","package":"tar","fixed_in":["1.34-150000.3.37.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Micro 6.1","package":"tar","fixed_in":["1.35-slfo.1.1_3.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Micro 6.0","package":"tar","fixed_in":["1.35-3.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Micro 6.2","package":"tar","fixed_in":["1.35-160000.3.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"tar","fixed_in":["1.35-160000.3.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"tar","fixed_in":["1.35-160000.3.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"tar","fixed_in":["1.34-15.27.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"tar","fixed_in":["1.34-15.27.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"tar","fixed_in":["1.34+dfsg-1ubuntu0.1.22.04.4"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"tar","fixed_in":["1.35+dfsg-3ubuntu0.2"],"sources":["osv"]},{"ecosystem":"Ubuntu:26.04:LTS","package":"tar","fixed_in":["1.35+dfsg-4ubuntu0.2"],"sources":["osv"]},{"ecosystem":"openSUSE:Tumbleweed","package":"tar","fixed_in":["1.35-7.1"],"sources":["osv"]},{"ecosystem":"openSUSE:Leap 16.0","package":"tar","fixed_in":["1.35-160000.3.1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"AlmaLinux:10","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.35-9.el10_1"}]}]},{"source":"osv","ecosystem":"AlmaLinux:9","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.34-9.el9_7"}]}]},{"source":"osv","ecosystem":"AlmaLinux:8","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.30-13.el8_10"}]}],"bundled":4},{"source":"osv","ecosystem":"Azure Linux:3","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"1.35-2"}]}]},{"source":"osv","ecosystem":"Azure Linux:2","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"1.34-3"}]}]},{"source":"osv","ecosystem":"Alpaquita:23","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.34-r1"}]}]},{"source":"osv","ecosystem":"Alpaquita:stream","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.34-r2"}]}]},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.34-7.el9.tuxcare.els1"}]}]},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.34-7.el9.tuxcare.els1"}]}]},{"source":"osv","ecosystem":"Julia","package":"Tar_jll","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.35.0+0"}]}]},{"source":"osv","ecosystem":"Mageia:10","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.35-4.1.mga10"}]}],"bundled":3},{"source":"osv","ecosystem":"Mageia:9","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.35-4.1.mga9"}]}],"bundled":3},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP4","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34-6.oe2203sp4"}]}]},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.35-3.oe2403"}]}]},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP1","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.35-3.oe2403sp1"}]}]},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP2","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.35-3.oe2403sp2"}]}]},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP3","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.35-3.oe2403sp3"}]}]},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP3","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34-6.oe2203sp3"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.1","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.35-9.el10_1"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.1","package":"tar-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.35-9.el10_1"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.1","package":"tar-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.35-9.el10_1"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.34-9.el9_7"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"tar-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.34-9.el9_7"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::baseos","package":"tar-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.34-9.el9_7"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux_eus:10.0","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.35-7.el10_0.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.4::baseos","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.34-6.el9_4.3"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.4::baseos","package":"tar-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.34-6.el9_4.3"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.4::baseos","package":"tar-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.34-6.el9_4.3"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.6::baseos","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.34-7.el9_6.2"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.30-13.el8_10"}]}],"bundled":4},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"tar-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.30-13.el8_10"}]}],"bundled":4},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"tar-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.30-13.el8_10"}]}],"bundled":4},{"source":"osv","ecosystem":"Rocky Linux:10","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.35-9.el10_1"}]}]},{"source":"osv","ecosystem":"Rocky Linux:9","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.34-9.el9_7"}]}]},{"source":"osv","ecosystem":"Rocky Linux:8","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.30-13.el8_10"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.3","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34-150000.3.37.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.4","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34-150000.3.37.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34-150000.3.37.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP7","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34-150000.3.37.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34-150000.3.37.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34-150000.3.37.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34-150000.3.37.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34-150000.3.37.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34-150000.3.37.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34-150000.3.37.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP6-LTSS","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34-150000.3.37.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34-150000.3.37.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34-150000.3.37.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP6","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34-150000.3.37.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.2","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34-150000.3.37.1"}]}]},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34-150000.3.37.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.35-slfo.1.1_3.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.35-3.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.35-160000.3.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.35-160000.3.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.35-160000.3.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.35-160000.4.1"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.35-160000.4.1"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.35-160000.4.1"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34-15.27.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34-15.27.1"}]}]},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.26+dfsg-8","1.27-3","1.27-4","1.27.1-1","1.27.1-1ubuntu0.1","1.27.1-1ubuntu0.1+esm1","1.27.1-1ubuntu0.1+esm2","1.27.1-1ubuntu0.1+esm3","1.27.1-1ubuntu0.1+esm4","1.27.1-1ubuntu0.1+esm5","1.27.1-1ubuntu0.1+esm6","1.27.1-1ubuntu0.1+esm7"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.27.1-2","1.28-2ubuntu1","1.28-2.1","1.28-2.1ubuntu0.1","1.28-2.1ubuntu0.2","1.28-2.1ubuntu0.2+esm1","1.28-2.1ubuntu0.2+esm2","1.28-2.1ubuntu0.2+esm3","1.28-2.1ubuntu0.2+esm4","1.28-2.1ubuntu0.2+esm5","1.28-2.1ubuntu0.2+esm6"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.29b-2","1.29b-2ubuntu0.1","1.29b-2ubuntu0.2","1.29b-2ubuntu0.3","1.29b-2ubuntu0.4","1.29b-2ubuntu0.4+esm1","1.29b-2ubuntu0.4+esm2","1.29b-2ubuntu0.4+esm3","1.29b-2ubuntu0.4+esm4"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.30+dfsg-6","1.30+dfsg-7","1.30+dfsg-7ubuntu0.20.04.1","1.30+dfsg-7ubuntu0.20.04.2","1.30+dfsg-7ubuntu0.20.04.3","1.30+dfsg-7ubuntu0.20.04.4","1.30+dfsg-7ubuntu0.20.04.4+esm1","1.30+dfsg-7ubuntu0.20.04.4+esm2","1.30+dfsg-7ubuntu0.20.04.4+esm3"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34+dfsg-1ubuntu0.1.22.04.4"}]}],"versions":["1.34+dfsg-1build1","1.34+dfsg-1build2","1.34+dfsg-1build3","1.34+dfsg-1ubuntu0.1.22.04.1","1.34+dfsg-1ubuntu0.1.22.04.2","1.34+dfsg-1ubuntu0.1.22.04.3"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.35+dfsg-3ubuntu0.2"}]}],"versions":["1.34+dfsg-1.2ubuntu1","1.34+dfsg-1.2ubuntu2","1.34+dfsg-1.3ubuntu1","1.34+dfsg-1.4","1.35+dfsg-2~build1","1.35+dfsg-2","1.35+dfsg-3","1.35+dfsg-3build1","1.35+dfsg-3ubuntu0.1"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.35+dfsg-3.1","1.35+dfsg-3.1build1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.35+dfsg-4ubuntu0.2"}]}],"versions":["1.35+dfsg-3.1build1","1.35+dfsg-3.1build2","1.35+dfsg-4","1.35+dfsg-4ubuntu0.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34+dfsg-1ubuntu0.1.22.04.4"}]}],"versions":["1.34+dfsg-1build1","1.34+dfsg-1build2","1.34+dfsg-1build3","1.34+dfsg-1ubuntu0.1.22.04.1","1.34+dfsg-1ubuntu0.1.22.04.2","1.34+dfsg-1ubuntu0.1.22.04.3"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.35+dfsg-3ubuntu0.2"}]}],"versions":["1.34+dfsg-1.2ubuntu1","1.34+dfsg-1.2ubuntu2","1.34+dfsg-1.3ubuntu1","1.34+dfsg-1.4","1.35+dfsg-2~build1","1.35+dfsg-2","1.35+dfsg-3","1.35+dfsg-3build1","1.35+dfsg-3ubuntu0.1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.35+dfsg-4ubuntu0.2"}]}],"versions":["1.35+dfsg-3.1build1","1.35+dfsg-3.1build2","1.35+dfsg-4","1.35+dfsg-4ubuntu0.1"]},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.35-7.1"}]}]},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.35-160000.3.1"}]}]},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.35-160000.4.1"}]}],"bundled":2}],"products":[{"vendor":"gnu","product":"tar"}],"references":[{"url":"https://github.com/i900008/vulndb/blob/main/Gnu_tar_vuln.md","tags":["Exploit","Third Party Advisory","web","article","report"]},{"url":"https://www.gnu.org/software/tar/","tags":["Product","Release Notes","web","article"]},{"url":"https://www.gnu.org/software/tar/manual/html_node/Security-rules-of-thumb.html","tags":["web"]},{"url":"https://www.gnu.org/software/tar/manual/html_node/Integrity.html","tags":["web"]},{"url":"https://lists.gnu.org/archive/html/bug-tar/2025-08/msg00012.html","tags":["web"]},{"url":"http://www.openwall.com/lists/oss-security/2025/11/01/6","tags":["web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-45582","tags":["web","advisory"]},{"url":"https://www.gnu.org/software/tar"},{"url":"https://github.com/advisories/GHSA-f93m-9mq4-2fjj"},{"url":"https://access.redhat.com/errata/RHSA-2026:0002","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-45582","tags":["report"]},{"url":"https://bugzilla.redhat.com/2379592","tags":["report"]},{"url":"https://errata.almalinux.org/10/ALSA-2026-0002.html","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2026:0067","tags":["advisory"]},{"url":"https://errata.almalinux.org/9/ALSA-2026-0067.html","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2026:70390","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-18477","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-18508","tags":["report"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-5704","tags":["report"]},{"url":"https://bugzilla.redhat.com/2455360","tags":["report"]},{"url":"https://bugzilla.redhat.com/2509735","tags":["report"]},{"url":"https://bugzilla.redhat.com/2509843","tags":["report"]},{"url":"https://errata.almalinux.org/8/ALSA-2026-70390.html","tags":["advisory"]},{"url":"https://docs.bell-sw.com/security/cves/CVE-2025-45582","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/tuxcare9.6esu/CLSA-2026-1769513855.html","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/almalinux9.2esu/CLSA-2026-1769598463.html","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2026-0401.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=36289","tags":["report"]},{"url":"https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ASLMG5TUYWS2IEKBCOWN5KZ2K55V366N/","tags":["web"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1091","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1092","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1093","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1094","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1095","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1096","tags":["advisory"]},{"url":"https://access.redhat.com/security/updates/classification/#moderate","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2379592","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_0002.json","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-45582","tags":["advisory","report"]},{"url":"https://www.gnu.org/software/tar/manual/html_node/Integrity.html#Integrity","tags":["article"]},{"url":"https://issues.redhat.com/browse/RHEL-136277","tags":["article"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_0067.json","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2026:0135","tags":["advisory"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_0135.json","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2026:0434","tags":["advisory"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_0434.json","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2026:0435","tags":["advisory"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_0435.json","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2455360","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2509735","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2509843","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_70390.json","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-5704","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-5704","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-18477","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-18477","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-18508","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-18508","tags":["advisory"]},{"url":"https://errata.rockylinux.org/RLSA-2026:0002","tags":["advisory"]},{"url":"https://errata.rockylinux.org/RLSA-2026:0067","tags":["advisory"]},{"url":"https://errata.rockylinux.org/RLSA-2026:70390","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20261177-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1246399","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2025-45582","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202620955-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202620959-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621002-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1246607","tags":["report"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621143-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202622289-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1261900","tags":["report"]},{"url":"https://bugzilla.suse.com/1265450","tags":["report"]},{"url":"https://bugzilla.suse.com/1267189","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2026-5704","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202622377-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20262615-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2025-45582","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-8510-1","tags":["advisory"]},{"url":"","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2025-45582","description":"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 -\u003e ../../../../../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 which \"tar xf\" is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages). NOTE: the official GNU Tar manual has an otherwise-empty directory for each \"tar xf\" in its Security Rules of Thumb; however, third-party advice leads users to run \"tar xf\" more than once into the same directory.","status":"published","published":"2025-07-11T00:00:00Z","modified":"2025-11-02T00:12:55.951Z","cvss":[{"version":"3.1","score":4.1,"vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:N/I:L/A:L","level":"medium","assessor":"cna"}],"cwes":["CWE-24"],"updated_at":"2026-11-02T14:32:36.385228Z"}],"euvd":[{"id":"EUVD-2025-21178","description":"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 -\u003e ../../../../../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 which \"tar xf\" is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages). NOTE: the official GNU Tar manual has an otherwise-empty directory for each \"tar xf\" in its Security Rules of Thumb; however, third-party advice leads users to run \"tar xf\" more than once into the same directory.","status":"published","published":"2025-07-11T00:00:00Z","modified":"2025-11-02T00:12:55Z","cvss":[{"version":"3.1","score":4.1,"vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:N/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T19:49:35.368666Z"}],"ghsa":[{"id":"GHSA-f93m-9mq4-2fjj","title":"GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR archives, with...","description":"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 -\u003e ../../../../../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 which \"tar xf\" is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages).","status":"published","published":"2025-07-11T18:30:34Z","modified":"2025-11-02T03:30:13Z","cvss":[{"version":"3.1","score":4.1,"vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:N/I:L/A:L","level":"medium"}],"cwes":["CWE-24"],"updated_at":"2026-11-02T15:04:17.06099Z"}],"nvd":[{"id":"CVE-2025-45582","description":"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 -\u003e ../../../../../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 which \"tar xf\" is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages). NOTE: the official GNU Tar manual has an otherwise-empty directory for each \"tar xf\" in its Security Rules of Thumb; however, third-party advice leads users to run \"tar xf\" more than once into the same directory.","status":"published","published":"2025-07-11T17:15:37.183Z","modified":"2026-06-17T09:25:34.87Z","cvss":[{"version":"3.1","score":4.1,"vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:N/I:L/A:L","level":"medium","assessor":"secondary"}],"cwes":["CWE-24"],"updated_at":"2026-11-02T14:11:18.285862Z"}],"osv":[{"id":"BELL-CVE-2025-45582","status":"published","published":"2025-07-15T06:00:46.541739Z","modified":"2025-08-06T01:38:21.558314Z","cvss":[{"version":"3.1","score":4.1,"vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:N/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T15:28:22.495824Z"},{"id":"JLSEC-2025-197","title":"GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR archives, with a...","description":"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 -\u003e ../../../../../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 which \"tar xf\" is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages). NOTE: the official GNU Tar manual has an otherwise-empty directory for each \"tar xf\" in its Security Rules of Thumb; however, third-party advice leads users to run \"tar xf\" more than once into the same directory.","status":"published","published":"2025-11-03T15:23:11.248Z","modified":"2026-07-23T22:30:17.639921616Z","cvss":[{"version":"3.1","score":4.1,"vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:N/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T15:47:17.805107Z"},{"id":"OESA-2026-1091","title":"tar security update","description":"GNU Tar provides the ability to create tar archives, as well as various other kinds of manipulation. For example, you can use Tar on previously created archives to extract files, to store additional files, or to update or list files which were already stored.\r\n\r\nSecurity Fix(es):\n\nGNU 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\u0026apos;s name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of \u0026quot;Member name contains \u0026apos;..\u0026apos;\u0026quot; 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 \u0026quot;x -\u0026gt; ../../../../../home/victim/.ssh\u0026quot; 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 which \u0026quot;tar xf\u0026quot; is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages). NOTE: the official GNU Tar manual has an otherwise-empty directory for each \u0026quot;tar xf\u0026quot; in its Security Rules of Thumb; however, third-party advice leads users to run \u0026quot;tar xf\u0026quot; more than once into the same directory.(CVE-2025-45582)","status":"published","published":"2026-01-16T11:10:08Z","modified":"2026-08-18T01:19:26.76350084Z","cvss":[{"version":"3.1","score":4.1,"vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:N/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T15:52:45.339366Z"},{"id":"OESA-2026-1092","title":"tar security update","description":"GNU Tar provides the ability to create tar archives, as well as various other kinds of manipulation. For example, you can use Tar on previously created archives to extract files, to store additional files, or to update or list files which were already stored.\r\n\r\nSecurity Fix(es):\n\nGNU 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\u0026apos;s name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of \u0026quot;Member name contains \u0026apos;..\u0026apos;\u0026quot; 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 \u0026quot;x -\u0026gt; ../../../../../home/victim/.ssh\u0026quot; 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 which \u0026quot;tar xf\u0026quot; is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages). NOTE: the official GNU Tar manual has an otherwise-empty directory for each \u0026quot;tar xf\u0026quot; in its Security Rules of Thumb; however, third-party advice leads users to run \u0026quot;tar xf\u0026quot; more than once into the same directory.(CVE-2025-45582)","status":"published","published":"2026-01-16T11:10:08Z","modified":"2026-08-18T01:19:27.32664803Z","cvss":[{"version":"3.1","score":4.1,"vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:N/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T15:52:45.339366Z"},{"id":"OESA-2026-1093","title":"tar security update","description":"GNU Tar provides the ability to create tar archives, as well as various other kinds of manipulation. For example, you can use Tar on previously created archives to extract files, to store additional files, or to update or list files which were already stored.\r\n\r\nSecurity Fix(es):\n\nGNU 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\u0026apos;s name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of \u0026quot;Member name contains \u0026apos;..\u0026apos;\u0026quot; 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 \u0026quot;x -\u0026gt; ../../../../../home/victim/.ssh\u0026quot; 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 which \u0026quot;tar xf\u0026quot; is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages). NOTE: the official GNU Tar manual has an otherwise-empty directory for each \u0026quot;tar xf\u0026quot; in its Security Rules of Thumb; however, third-party advice leads users to run \u0026quot;tar xf\u0026quot; more than once into the same directory.(CVE-2025-45582)","status":"published","published":"2026-01-16T11:10:08Z","modified":"2026-08-18T01:19:26.760223212Z","cvss":[{"version":"3.1","score":4.1,"vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:N/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T15:52:45.339366Z"},{"id":"OESA-2026-1094","title":"tar security update","description":"GNU Tar provides the ability to create tar archives, as well as various other kinds of manipulation. For example, you can use Tar on previously created archives to extract files, to store additional files, or to update or list files which were already stored.\r\n\r\nSecurity Fix(es):\n\nGNU 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\u0026apos;s name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of \u0026quot;Member name contains \u0026apos;..\u0026apos;\u0026quot; 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 \u0026quot;x -\u0026gt; ../../../../../home/victim/.ssh\u0026quot; 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 which \u0026quot;tar xf\u0026quot; is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages). NOTE: the official GNU Tar manual has an otherwise-empty directory for each \u0026quot;tar xf\u0026quot; in its Security Rules of Thumb; however, third-party advice leads users to run \u0026quot;tar xf\u0026quot; more than once into the same directory.(CVE-2025-45582)","status":"published","published":"2026-01-16T11:10:08Z","modified":"2026-08-18T01:19:26.995125913Z","cvss":[{"version":"3.1","score":4.1,"vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:N/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T15:52:45.339366Z"},{"id":"OESA-2026-1095","title":"tar security update","description":"GNU Tar provides the ability to create tar archives, as well as various other kinds of manipulation. For example, you can use Tar on previously created archives to extract files, to store additional files, or to update or list files which were already stored.\r\n\r\nSecurity Fix(es):\n\nGNU 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\u0026apos;s name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of \u0026quot;Member name contains \u0026apos;..\u0026apos;\u0026quot; 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 \u0026quot;x -\u0026gt; ../../../../../home/victim/.ssh\u0026quot; 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 which \u0026quot;tar xf\u0026quot; is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages). NOTE: the official GNU Tar manual has an otherwise-empty directory for each \u0026quot;tar xf\u0026quot; in its Security Rules of Thumb; however, third-party advice leads users to run \u0026quot;tar xf\u0026quot; more than once into the same directory.(CVE-2025-45582)","status":"published","published":"2026-01-16T11:10:08Z","modified":"2026-08-18T01:19:27.102447152Z","cvss":[{"version":"3.1","score":4.1,"vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:N/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T15:52:45.339366Z"},{"id":"OESA-2026-1096","title":"tar security update","description":"GNU Tar provides the ability to create tar archives, as well as various other kinds of manipulation. For example, you can use Tar on previously created archives to extract files, to store additional files, or to update or list files which were already stored.\r\n\r\nSecurity Fix(es):\n\nGNU 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\u0026apos;s name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of \u0026quot;Member name contains \u0026apos;..\u0026apos;\u0026quot; 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 \u0026quot;x -\u0026gt; ../../../../../home/victim/.ssh\u0026quot; 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 which \u0026quot;tar xf\u0026quot; is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages). NOTE: the official GNU Tar manual has an otherwise-empty directory for each \u0026quot;tar xf\u0026quot; in its Security Rules of Thumb; however, third-party advice leads users to run \u0026quot;tar xf\u0026quot; more than once into the same directory.(CVE-2025-45582)","status":"published","published":"2026-01-16T11:10:08Z","modified":"2026-08-18T01:19:27.078774627Z","cvss":[{"version":"3.1","score":4.1,"vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:N/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T15:52:45.339366Z"},{"id":"RHSA-2026:0002","title":"Red Hat Security Advisory: tar security update","status":"published","published":"2026-01-05T10:11:48Z","modified":"2026-09-23T10:04:42Z","cvss":[{"version":"3.1","score":5.6,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T15:53:17.634515Z"},{"id":"RHSA-2026:0067","title":"Red Hat Security Advisory: tar security update","status":"published","published":"2026-01-06T10:09:32Z","modified":"2026-09-23T10:04:43Z","cvss":[{"version":"3.1","score":5.6,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T15:53:17.634515Z"},{"id":"RHSA-2026:0135","title":"Red Hat Security Advisory: tar security update","status":"published","published":"2026-01-07T10:07:33Z","modified":"2026-09-23T10:04:43Z","cvss":[{"version":"3.1","score":5.6,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T15:53:17.634515Z"},{"id":"RHSA-2026:0434","title":"Red Hat Security Advisory: tar security update","status":"published","published":"2026-01-14T10:39:10Z","modified":"2026-09-23T10:04:52Z","cvss":[{"version":"3.1","score":5.6,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T15:53:18.066978Z"},{"id":"RHSA-2026:0435","title":"Red Hat Security Advisory: tar security update","status":"published","published":"2026-01-14T10:39:11Z","modified":"2026-09-23T10:04:53Z","cvss":[{"version":"3.1","score":5.6,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T15:53:18.066978Z"},{"id":"RHSA-2026:70390","title":"Red Hat Security Advisory: tar security, bug fix, and enhancement update","status":"published","published":"2026-09-23T10:15:22Z","modified":"2026-09-23T10:42:32.692411196Z","cvss":[{"version":"3.1","score":5.6,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T15:53:22.928316Z"},{"id":"RLSA-2026:0002","title":"Moderate: tar security update","description":"The GNU tar program can save multiple files in an archive and restore files from an archive.\n\nSecurity Fix(es):\n\n* tar: Tar path traversal (CVE-2025-45582)\n\nFor 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.","status":"published","published":"2026-01-05T09:08:12.588966Z","modified":"2026-01-05T09:44:54.258345Z","cvss":[{"version":"3.1","score":5.6,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T15:53:25.508922Z"},{"id":"RLSA-2026:0067","title":"Moderate: tar security update","description":"The GNU tar program can save multiple files in an archive and restore files from an archive.\n\nSecurity Fix(es):\n\n* tar: Tar path traversal (CVE-2025-45582)\n\nFor 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.","status":"published","published":"2026-01-06T09:04:05.906823Z","modified":"2026-01-06T09:29:55.3047Z","cvss":[{"version":"3.1","score":5.6,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T15:53:25.508922Z"},{"id":"RLSA-2026:70390","title":"Moderate: tar security, bug fix, and enhancement update","description":"The GNU tar program can save multiple files in an archive and restore files from an archive.\n\nSecurity Fix(es):\n\n* tar: Tar path traversal (CVE-2025-45582)\n\n* tar: tar: Hidden file injection via crafted archives (CVE-2026-5704)\n\n* tar: tar: TOCTOU in incremental dumpdir 'X' rename handling allows restore path escape (CVE-2026-18477)\n\n* tar: tar: --one-top-level hardlink targets not confined to top-level directory enabling arbitrary file overwrite (CVE-2026-18508)\n\nBug Fix(es) and Enhancement(s):\n\n* tar: --one-top-level with absolute path fails [rhel-8.10.z] (JIRA:Rocky Linux-144019)\n\nFor 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.","status":"published","published":"2026-09-24T06:01:09.673764Z","modified":"2026-09-24T06:30:02.6746523Z","cvss":[{"version":"3.1","score":5.6,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T15:53:26.449929Z"},{"id":"UBUNTU-CVE-2025-45582","description":"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 -\u003e ../../../../../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 which \"tar xf\" is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages). NOTE: the official GNU Tar manual has an otherwise-empty directory for each \"tar xf\" in its Security Rules of Thumb; however, third-party advice leads users to run \"tar xf\" more than once into the same directory.","status":"published","published":"2025-07-11T17:15:00Z","modified":"2026-07-22T20:46:40.337951581Z","cvss":[{"version":"3.1","score":4.1,"vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:N/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T16:55:50.31802Z"},{"id":"ALSA-2026:0002","title":"Moderate: tar security update","description":"The GNU tar program can save multiple files in an archive and restore files from an archive.  \n\nSecurity Fix(es):  \n\n  * tar: Tar path traversal (CVE-2025-45582)\n\n\nFor 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.\n","status":"published","published":"2026-01-05T00:00:00Z","modified":"2026-10-29T11:58:14.273052Z","updated_at":"2026-11-02T15:27:53.875139Z"},{"id":"ALSA-2026:0067","title":"Moderate: tar security update","description":"The GNU tar program can save multiple files in an archive and restore files from an archive.  \n\nSecurity Fix(es):  \n\n  * tar: Tar path traversal (CVE-2025-45582)\n\n\nFor 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.\n","status":"published","published":"2026-01-05T00:00:00Z","modified":"2026-10-29T11:30:28.08145468Z","updated_at":"2026-11-02T15:27:53.875139Z"},{"id":"ALSA-2026:70390","title":"Moderate: tar security, bug fix, and enhancement update","description":"The GNU tar program can save multiple files in an archive and restore files from an archive.  \n\nSecurity Fix(es):  \n\n  * tar: Tar path traversal (CVE-2025-45582)\n  * tar: tar: Hidden file injection via crafted archives (CVE-2026-5704)\n  * tar: tar: TOCTOU in incremental dumpdir 'X' rename handling allows restore path escape (CVE-2026-18477)\n  * tar: tar: --one-top-level hardlink targets not confined to top-level directory enabling arbitrary file overwrite (CVE-2026-18508)\n\n\nBug Fix(es) and Enhancement(s):  \n\n  * tar: --one-top-level with absolute path fails [almalinux-8.10.z] (JIRA:AlmaLinux-144019)\n\n\nFor 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.\n","status":"published","published":"2026-09-22T00:00:00Z","modified":"2026-10-29T11:02:29.621934812Z","updated_at":"2026-11-02T15:27:55.200553Z"},{"id":"AZL-65082","title":"CVE-2025-45582 affecting package tar 1.35-2","description":"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 -\u003e ../../../../../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 which \"tar xf\" is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages). NOTE: the official GNU Tar manual has an otherwise-empty directory for each \"tar xf\" in its Security Rules of Thumb; however, third-party advice leads users to run \"tar xf\" more than once into the same directory.","status":"published","published":"2025-07-11T17:15:37Z","modified":"2026-04-21T04:32:40.247947Z","updated_at":"2026-11-02T15:28:08.076947Z"},{"id":"AZL-65538","title":"CVE-2025-45582 affecting package tar 1.34-3","description":"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 -\u003e ../../../../../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 which \"tar xf\" is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages). NOTE: the official GNU Tar manual has an otherwise-empty directory for each \"tar xf\" in its Security Rules of Thumb; however, third-party advice leads users to run \"tar xf\" more than once into the same directory.","status":"published","published":"2025-07-11T17:15:37Z","modified":"2026-04-21T04:32:41.018463Z","updated_at":"2026-11-02T15:28:08.076947Z"},{"id":"CLSA-2026-1769513855","title":"tar: Fix of CVE-2025-45582","description":"- CVE-2025-45582: fixed path traversal vulnerability using malicious\n  archive extraction","status":"published","published":"2026-01-28T09:43:54Z","modified":"2026-06-01T00:32:40.304420544Z","updated_at":"2026-11-02T15:43:42.847264Z"},{"id":"CLSA-2026-1769598463","title":"tar: Fix of CVE-2025-45582","description":"- CVE-2025-45582: fixed path traversal vulnerability using malicious\n  archive extraction","status":"published","published":"2026-01-28T11:07:47Z","modified":"2026-06-01T00:31:40.293140682Z","updated_at":"2026-11-02T15:43:42.847264Z"},{"id":"MGASA-2026-0401","title":"Updated tar packages fix security vulnerabilities","description":"GNU Tar through 1.35 allows file overwrite via directory traversal in\ncrafted TAR archives, with a certain two-step process. (CVE-2025-45582)\nTar: toctou in incremental dumpdir 'x' rename handling allows restore\npath escape. (CVE-2026-18477)\nTar: --one-top-level hardlink targets not confined to top-level\ndirectory enabling arbitrary file overwrite. (CVE-2026-18508)\n","status":"published","published":"2026-09-14T16:26:35Z","modified":"2026-09-14T16:42:46.255057952Z","updated_at":"2026-11-02T15:49:43.795591Z"},{"id":"openSUSE-SU-2026:10743-1","title":"tar-1.35-7.1 on GA media","description":"These are all security issues fixed in the tar-1.35-7.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2026-05-10T00:00:00Z","modified":"2026-05-11T08:15:28.461292Z","updated_at":"2026-11-02T16:58:38.415593Z"},{"id":"openSUSE-SU-2026:20472-1","title":"Security update for tar","description":"This update for tar fixes the following issue:\n\nSecurity issue:\n\n- CVE-2025-45582: file overwrite via directory traversal in crafted TAR archives (bsc#1246399).\n\nNon security issue:\n\n- Fixes tar creating invalid tarballs when used with --delete (bsc#1246607)\n","status":"published","published":"2026-04-07T14:58:07Z","modified":"2026-04-10T18:24:09.089343Z","updated_at":"2026-11-02T16:58:41.463445Z"},{"id":"openSUSE-SU-2026:21070-1","title":"Security update for tar","description":"This update for tar fixes the following issues\n\n- CVE-2026-5704: crafted archives can be used to to hide file injection (bsc#1261900).\n- Fix --dereference/-h not working properly after CVE-2025-45582 fix (bsc#1265450).\n","status":"published","published":"2026-06-26T09:13:30Z","modified":"2026-06-30T18:24:39.271066833Z","updated_at":"2026-11-02T16:58:41.885092Z"},{"id":"SUSE-SU-2026:1177-1","title":"Security update for tar","description":"This update for tar fixes the following issue:\n\n- CVE-2025-45582: file overwrite via directory traversal in crafted TAR archives (bsc#1246399).\n","status":"published","published":"2026-04-02T15:00:45Z","modified":"2026-04-03T07:45:50.391383Z","updated_at":"2026-11-02T15:54:01.262144Z"},{"id":"SUSE-SU-2026:20955-1","title":"Security update for tar","description":"This update for tar fixes the following issue:\n\n- CVE-2025-45582: file overwrite via directory traversal in crafted TAR archives (bsc#1246399).\n","status":"published","published":"2026-04-01T09:39:25Z","modified":"2026-04-08T18:23:56.768335Z","updated_at":"2026-11-02T15:54:01.953589Z"},{"id":"SUSE-SU-2026:20959-1","title":"Security update for tar","description":"This update for tar fixes the following issue:\n\n- CVE-2025-45582: file overwrite via directory traversal in crafted TAR archives (bsc#1246399).\n","status":"published","published":"2026-04-01T10:05:58Z","modified":"2026-04-08T18:24:31.204148Z","updated_at":"2026-11-02T15:54:01.953589Z"},{"id":"SUSE-SU-2026:21002-1","title":"Security update for tar","description":"This update for tar fixes the following issue:\n\nSecurity issue:\n\n- CVE-2025-45582: file overwrite via directory traversal in crafted TAR archives (bsc#1246399).\n\nNon security issue:\n\n- Fixes tar creating invalid tarballs when used with --delete (bsc#1246607)\n","status":"published","published":"2026-04-07T14:59:15Z","modified":"2026-04-14T18:26:39.902522Z","updated_at":"2026-11-02T15:54:01.953589Z"},{"id":"SUSE-SU-2026:21143-1","title":"Security update for tar","description":"This update for tar fixes the following issue:\n\nSecurity issue:\n\n- CVE-2025-45582: file overwrite via directory traversal in crafted TAR archives (bsc#1246399).\n\nNon security issue:\n\n- Fixes tar creating invalid tarballs when used with --delete (bsc#1246607)\n","status":"published","published":"2026-04-07T14:59:15Z","modified":"2026-04-22T18:24:49.414651Z","updated_at":"2026-11-02T15:54:02.312556Z"},{"id":"SUSE-SU-2026:22289-1","title":"Security update for tar","description":"This update for tar fixes the following issues\n\n- CVE-2026-5704: crafted archives can be used to to hide file injection (bsc#1261900).\n- Fix --dereference/-h not working properly after CVE-2025-45582 fix (bsc#1265450).\n","status":"published","published":"2026-06-26T08:50:25Z","modified":"2026-06-30T18:24:27.493467242Z","updated_at":"2026-11-02T15:54:03.080707Z"},{"id":"SUSE-SU-2026:22377-1","title":"Security update for tar","description":"This update for tar fixes the following issues\n\n- CVE-2026-5704: crafted archives can be used to to hide file injection (bsc#1261900).\n- Fix --dereference/-h not working properly after CVE-2025-45582 fix (bsc#1265450).\n","status":"published","published":"2026-06-26T08:50:25Z","modified":"2026-07-02T18:24:15.040392181Z","updated_at":"2026-11-02T15:54:03.080707Z"},{"id":"SUSE-SU-2026:2615-1","title":"Security update for tar","description":"This update for tar fixes the following issues:\n\nUpgrade tar to version 1.34 (jsc#PED-16073).\n\nSecurity issues fixed:\n\n- CVE-2025-45582: file overwrite via directory traversal in crafted TAR archives (bsc#1246399).\n\nOther updates and bugfixes:\n\n* Changes from 1.28:\n  - New --one-top-level option: extract all files into a subdirectory named after the archive base name\n  - New --sort option: sort directory entries by name or inode when creating archives\n  - New exclusion options: --exclude-ignore, --exclude-ignore-recursive, and --exclude-vcs-ignores\n  - New checkpoint action: totals; extended checkpoint format specifiers\n  - Official tar(1) and rmt(8) manpages now provided upstream\n  - Refuse to read from or write archives to a tty device\n* Changes from 1.29:\n  - New --verbatim-files-from option: treat each line in a file list as a literal file name regardless of leading\n    dashes\n* Changes from 1.30:\n  - Member names containing '..' components are now skipped on extraction (security hardening)\n  - Erroneous use of position-sensitive options is now reported\n  - --numeric-owner now applies to private (pax) headers too\n  - Fixed --delay-directory-restore in several edge cases\n  - New --warnings=failed-read option to suppress unreadable-file warnings when combined with --ignore-failed-read\n* Changes from 1.32:\n  - POSIX extended format headers no longer include PID by default\n  - Wildcards in --exclude-vcs-ignore mode no longer match slashes\n  - Fixed --no-overwrite-dir option\n  - Fixed handling of chained renames in incremental backups\n  - Link counting works for file names supplied via -T\n* Changes from 1.33:\n  - Fix extraction over pipe\n  - Fix memory leak in read_header\n  - Fix extraction when . and .. are unreadable\n  - Gracefully handle duplicate symlinks when extracting\n  - Re-initialise supplementary groups when switching to user privileges\n","status":"published","published":"2026-06-24T09:02:36Z","modified":"2026-06-25T06:15:06.871826685Z","updated_at":"2026-11-02T15:54:04.519245Z"},{"id":"USN-8510-1","title":"tar vulnerability","description":"It was discovered that tar incorrectly handled symlinks when extracting\narchives. An attacker could possibly use this issue to overwrite arbitrary\nfiles.","status":"published","published":"2026-07-06T11:57:49Z","modified":"2026-07-06T20:34:34.654931584Z","updated_at":"2026-11-02T16:58:25.103481Z"}]}}