Skip to content
Noroxi
NVD / CVE Program· CNA mitre

CVE-2025-45582: GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR archives, with a certain two-step process.

Noroxi assessment

Priority: Monitor (action score 16/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.49% (FIRST EPSS).
  • Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
  • Fixed version: tar (AlmaLinux:10) 2:1.35-9.el10_1; tar (AlmaLinux:8) 2:1.30-13.el8_10; tar (AlmaLinux:9) 2:1.34-9.el9_7.

Low priority for now. Upgrade to tar (AlmaLinux:10) 2:1.35-9.el10_1; tar (AlmaLinux:8) 2:1.30-13.el8_10; tar (AlmaLinux:9) 2:1.34-9.el9_7 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 4.1 · v3.1—No exploit Fix available
Published
Jul 11, 2025
Updated
Jun 17, 2026
EPSS
0.4% · 42th percentile

Report tools

JSON

Action score

16

Monitor

Low priority for now.

CVSS
16 / 40 · 4.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · mitre
4.1
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-45582

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
gnutar

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • gnu tarbefore 1.35

Versions reported by the vendor

Affected version ranges reported by the assigning authority (mitre). Independent of NVD's CPE analysis and usually ahead of it.

  • GNU Tar

    • up to and including 1.35affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10tarbefore 2:1.35-9.el10_12:1.35-9.el10_1
AlmaLinux:8tarbefore 2:1.30-13.el8_102:1.30-13.el8_10
AlmaLinux:9tarbefore 2:1.34-9.el9_72:1.34-9.el9_7
openSUSE:Leap 15.6tarbefore 1.34-150000.3.37.11.34-150000.3.37.1
openSUSE:Leap 16.0tarbefore 1.35-160000.4.11.35-160000.4.1
openSUSE:Leap 16.0tarbefore 1.35-160000.3.11.35-160000.3.1
openSUSE:Tumbleweedtarbefore 1.35-7.11.35-7.1
Red Hat:enterprise_linux_eus:10.0tarbefore 2:1.35-7.el10_0.22:1.35-7.el10_0.2
Red Hat:enterprise_linux:10.1tarbefore 2:1.35-9.el10_12:1.35-9.el10_1
Red Hat:enterprise_linux:10.1tar-debuginfobefore 2:1.35-9.el10_12:1.35-9.el10_1
Red Hat:enterprise_linux:10.1tar-debugsourcebefore 2:1.35-9.el10_12:1.35-9.el10_1
Red Hat:enterprise_linux:8::baseostarbefore 2:1.30-13.el8_102:1.30-13.el8_10
Red Hat:enterprise_linux:8::baseostar-debuginfobefore 2:1.30-13.el8_102:1.30-13.el8_10
Red Hat:enterprise_linux:8::baseostar-debugsourcebefore 2:1.30-13.el8_102:1.30-13.el8_10
Red Hat:enterprise_linux:9::baseostarbefore 2:1.34-9.el9_72:1.34-9.el9_7
Red Hat:enterprise_linux:9::baseostar-debuginfobefore 2:1.34-9.el9_72:1.34-9.el9_7
Red Hat:enterprise_linux:9::baseostar-debugsourcebefore 2:1.34-9.el9_72:1.34-9.el9_7
Red Hat:rhel_eus:9.4::baseostarbefore 2:1.34-6.el9_4.32:1.34-6.el9_4.3
Red Hat:rhel_eus:9.4::baseostar-debuginfobefore 2:1.34-6.el9_4.32:1.34-6.el9_4.3
Red Hat:rhel_eus:9.4::baseostar-debugsourcebefore 2:1.34-6.el9_4.32:1.34-6.el9_4.3
Red Hat:rhel_eus:9.6::baseostarbefore 2:1.34-7.el9_6.22:1.34-7.el9_6.2
Rocky Linux:10tarbefore 2:1.35-9.el10_12:1.35-9.el10_1
Rocky Linux:8tarbefore 2:1.30-13.el8_102:1.30-13.el8_10
Rocky Linux:9tarbefore 2:1.34-9.el9_72:1.34-9.el9_7

+6

Same product

gnu: all records

Other highest-scoring records for the same primary product.

  • CVE-2005-2541Tar 1.15.1 does not properly warn the user when extracting setuid or setgid files, which may allow local users or remote attackers to gain p
    41Plan
  • CVE-2016-6321Directory traversal vulnerability in the safer_name_suffix function in GNU tar 1.14 through 1.29 might allow remote attackers to bypass an i
    35Monitor
  • CVE-2007-4476Buffer overflow in the safer_name_suffix function in GNU tar has unspecified attack vectors and impact, resulting in a "crashing stack."
    34Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2022-48303Jan 30, 2023 · GNU Tar through 1.34 has a one-byte out-of-bounds read that results in use of uninitialized memory for a conditional jump.
    22Monitor
  • ← EarlierCVE-2023-39804Mar 27, 2024 · In GNU tar before 1.35, mishandled extension attributes in a PAX archive can lead to an application crash in xheader.c.
    24Monitor
  • Later →CVE-2026-5704Apr 6, 2026 · Tar: tar: hidden file injection via crafted archives
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
almalinux:tar2:1.35-9.el10_1 · AlmaLinux:10Package registry (OSV)
opensuse:tar1.34-150000.3.37.1 · openSUSE:Leap 15.6Package registry (OSV)
red hat:tar2:1.35-9.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:tar-debuginfo2:1.35-9.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:tar-debugsource2:1.35-9.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
rocky linux:tar2:1.35-9.el10_1 · Rocky Linux:10Package registry (OSV)
suse:tar1.34-150000.3.37.1 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
low · data or configuration can be modified
Availability
low · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Local
Attack complexity
High
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality impact
None
Integrity impact
Low
Availability impact
Low

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:N/I:L/A:L

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records