Skip to main content
MEDIUM

CVE-2025-45582

CVSS v3

4.1

MEDIUM

EPSS Score

0.5 %

exploit probability, as of 2026-10-19

CISA KEV

No

known exploited

Exploitation

—

SSVC status

Get an alert for each new CVE published for tar.

Set up CVE WatchFree account · no credit card

Affected and fixed versions

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • tarAlmaLinux:10all versions · fixed in 2:1.35-9.el10_1
  • tarAlmaLinux:9all versions · fixed in 2:1.34-9.el9_7
  • tarAlmaLinux:8all versions · fixed in 2:1.30-13.el8_10

Vendor advisories

  • CVE-2025-45582 Red Hat Product Security75 products fixed · 5 known affected

    tar: Tar path traversal

    tar.src as a component of Red Hat Enterprise Linux 6 · tar.src as a component of Red Hat Enterprise Linux 7 · io.syndesis-syndesis-ui as a component of Red Hat Fuse 7

  • RHSA-2026:70390 Red Hat Product Security13 products fixed

    Red Hat Security Advisory: tar security, bug fix, and enhancement update

  • RHSA-2026:1858 Red Hat Product Security3 products fixed

    Red Hat Security Advisory: Red Hat Ceph Storage

  • RHSA-2026:1652 Red Hat Product Security4 products fixed

    Red Hat Security Advisory: Red Hat Ceph Storage

  • RHSA-2026:0685 Red Hat Product Security4 products fixed

    Red Hat Security Advisory: Red Hat Update Infrastructure 5 security update

  • RHSA-2026:0435 Red Hat Product Security4 products fixed

    Red Hat Security Advisory: tar security update

5 more advisories

Full record on NVD

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 -> ../../../../../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.

Technical details

CVSS v3 Vector
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:N/I:L/A:L
Published
2025-07-11
Last Modified
2025-11-02

Frequently asked questions

What is CVE-2025-45582?

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 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.

Is CVE-2025-45582 actively exploited?

Active exploitation of CVE-2025-45582 has not been confirmed. Its EPSS score was 0.5% on 2026-10-19, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2025-45582?

CVE-2025-45582 has a CVSS v3 base score of 4.1 (MEDIUM severity), with vector string CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:N/I:L/A:L.

Running tar? Hear about its next vulnerability

CVE Watch matches each new CVE to the vendors and products you list (vendor and product, not the version) and puts it in your alerts with its KEV and EPSS status.

Get alerts for this productCISA KEV additions, October 2026Search CVEs

Already have an account? Open CVE WatchNo credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database