CVE-2025-45582

MEDIUMNVD 4.14.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 4.1 from GitHub Security Advisory published 2025-07-11. NVD baseline CVSS 4.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated
4.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 4.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
4.1
EG Score
4.1MEDIUMmedium confidence
EG Risk
34
EG Risk 34/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity41% × 45%
The EG Score, 4.1 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
40th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 11, 2025

Last Modified

November 2, 2025

References (6)

Vendor Advisories for CVE-2025-45582(10)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(9)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhceph/rhceph-7-rhel9:17695084552026-02-03redhat
redhatrhceph/rhceph-8-rhel9:17695123832026-02-02redhat
redhatrhui5/rhua-rhel9:17683770122026-01-15redhat
redhattar-2:1.34-7.el9_6.22026-01-12redhat
redhattar-2:1.34-6.el9_4.32026-01-12redhat
redhatdiscovery/discovery-ui-rhel9:17679045732026-01-08redhat
redhattar-2:1.35-7.el10_0.22026-01-06redhat
redhattar-2:1.35-9.el10_12026-01-05redhat
redhattar-2:1.34-9.el9_72026-01-05redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 30× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 89 of 171 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 11 repeat rows among the latest 100 are merged into the row they repeat. The 82 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  2. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  3. 2026-10-13 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  4. 2026-10-12 17:03 UTCEG score recompute
  5. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  6. 2026-10-11 20:36 UTCEG score recompute
  7. 2026-10-11 18:48 UTCEG score recompute
  8. 2026-10-11 15:24 UTCEG score recompute
  9. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  10. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  11. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  12. 2026-10-08 17:10 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  13. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  15. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  16. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  17. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  18. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  19. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  21. 2026-09-27 13:45 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  22. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  23. 2026-09-26 00:25 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  24. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  25. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.4% · 38th percentile
Show 64 more
  1. 2026-09-21 21:06 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  2. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  3. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  4. 2026-09-17 19:29 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  5. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  6. 2026-09-15 03:09 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  7. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  8. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  9. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  10. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  11. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  12. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  13. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  14. 2026-09-05 15:28 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  15. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  16. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  17. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  18. 2026-09-01 04:38 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  19. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  20. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  21. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  22. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  23. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  24. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  25. 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  26. 2026-08-24 09:22 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  27. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  28. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  29. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  30. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  31. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  32. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  33. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  34. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  35. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  36. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  37. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  38. 2026-08-11 13:41 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  39. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  40. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  41. 2026-08-08 16:36 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  42. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  43. 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  44. 2026-08-04 15:09 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  45. 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  46. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  47. 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  48. 2026-08-01 04:15 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  49. 2026-07-30 16:27 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  50. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  51. 2026-07-28 15:35 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  52. 2026-07-26 14:54 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  53. 2026-07-25 14:17 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  54. 2026-07-24 14:17 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  55. 2026-07-23 14:18 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  56. 2026-07-23 02:56 UTCEG score recompute
  57. 2026-07-22 14:07 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  58. 2026-07-21 15:24 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  59. 2026-07-20 17:07 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  60. 2026-07-19 14:30 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  61. 2026-07-19 02:28 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  62. 2026-07-18 10:04 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  63. 2026-07-16 17:02 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  64. 2026-07-15 16:57 UTCEPSS rescoreEPSS 0.4% · 34th percentile

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-45582?
CVE-2025-45582 is a medium-severity vulnerability; its CVE record was published on July 11, 2025. 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,…
When was the CVE record for CVE-2025-45582 published?
The CVE record for CVE-2025-45582 was published on July 11, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 2, 2025; the record at its source may have been updated since.
Is CVE-2025-45582 actively exploited?
CVE-2025-45582 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-45582?
CVE-2025-45582 has a CVSS v3 base score of 4.1 (NVD).
How do I remediate CVE-2025-45582?
A fix for CVE-2025-45582 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-45582 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-45582

Explore →

Is Your Infrastructure Affected by CVE-2025-45582?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs