CVE-2025-67030

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.7%, top 51% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

Directory Traversal vulnerability in the extractFile method of org.codehaus.plexus.util.Expand in plexus-utils before 6d780b3378829318ba5c2d29547e0012d5b29642. This allows an attacker to execute arbitrary code

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

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
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

March 25, 2026

Last Modified

August 24, 2026

Advisory Details (5)

Auto-updated May 1, 2026
No patch confirmed yet.
generic

Fix Zip Slip vulnerability in archive extraction by Copilot · Pull Request #296 · codehaus-plexus/plexus-utils · GitHub

https://github.com/codehaus-plexus/plexus-utils/pull/296
generic

Fix directory traversal vulnerability in Expand.extractFile by Copilot · Pull Request #295 · codehaus-plexus/plexus-utils · GitHub

https://github.com/codehaus-plexus/plexus-utils/pull/295
generic

directory traversal still in org.codehaus.plexus.util.Expand · Issue #294 · codehaus-plexus/plexus-utils · GitHub

https://github.com/codehaus-plexus/plexus-utils/issues/294
generic

Fix Zip Slip vulnerability in archive extraction (#296) · codehaus-plexus/plexus-utils@6d780b3 · GitHub

https://github.com/codehaus-plexus/plexus-utils/commit/6d780b3378829318ba5c2d29547e0012d5b29642

Patch Availability(14)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatjavapackages-tools:201801-8100020260520141124.88f2bc722026-07-20redhat
redhatmaven:3.8-8100020260520141024.b249b32d2026-07-16redhat
redhatplexus-utils-0:3.3.0-14.el9_82026-07-13redhat
redhatplexus-utils-0:3.5.1-9.el10_22026-07-13redhat
redhatmaven:3.9-9080020260520135357.470dcefd2026-07-13redhat
redhatmaven:3.9-9060020260612145814.470dcefd2026-07-06redhat
redhatplexus-utils-0:3.3.0-10.el9_2.22026-07-06redhat
redhatplexus-utils-0:3.3.0-10.el9_4.22026-07-06redhat
redhatmaven:3.8-8080020260615155417.a1d5b3e22026-07-06redhat
redhatplexus-utils-0:3.3.0-13.el9_6.12026-07-06redhat
redhatplexus-utils-0:3.5.1-8.el10_0.12026-07-06redhat
redhateap8-yasson-0:3.0.4-5.redhat_00007.1.el9eap2026-05-18redhat
redhateap8-yasson-0:3.0.4-5.redhat_00007.1.el8eap2026-05-18redhat
redhatplexus-utils2026-05-18redhat

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.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
plexus-utils23.3.0-1, 3.3.0-2, 3.3.0-3, 3.3.1-1, 3.4.2-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
plexus-utils23.4.2-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
plexus-utils23.4.2-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
plexus-utils23.4.2-1
Maven(1)
PackageVulnerable rangeFixed inDependents
org.codehaus.plexus:plexus-utils1.0.4 ... 3.6.0 (78 versions)3.6.1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 67× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 195 total refreshes for this CVE.

  1. 2026-08-25 13:48 UTCEPSS rescore
  2. 2026-08-24 14:16 UTCEPSS rescore
  3. 2026-08-24 13:31 UTCVendor advisory
  4. 2026-08-24 12:27 UTCEG score recompute
  5. 2026-08-24 12:27 UTCVendor advisory
  6. 2026-08-23 00:18 UTCEPSS rescore
  7. 2026-08-21 23:48 UTCEPSS rescore
  8. 2026-08-20 22:55 UTCEPSS rescore
  9. 2026-08-19 17:03 UTCEPSS rescore
  10. 2026-08-18 13:47 UTCEPSS rescore
  11. 2026-08-17 13:46 UTCEPSS rescore
  12. 2026-08-17 12:13 UTCEG score recompute
  13. 2026-08-17 12:13 UTCVendor advisory
  14. 2026-08-16 14:55 UTCEPSS rescore
  15. 2026-08-16 10:14 UTCEG score recompute
  16. 2026-08-16 10:14 UTCVendor advisory
  17. 2026-08-16 02:13 UTCEPSS rescore
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-15 01:29 UTCEPSS rescore
  20. 2026-08-14 19:29 UTCVendor advisory
  21. 2026-08-14 06:32 UTCEG score recompute
  22. 2026-08-14 06:32 UTCVendor advisory
  23. 2026-08-13 21:59 UTCEPSS rescore
  24. 2026-08-13 00:30 UTCEG score recompute
  25. 2026-08-13 00:30 UTCVendor advisory
Show 75 more
  1. 2026-08-12 13:50 UTCEPSS rescore
  2. 2026-08-12 12:14 UTCVendor advisory
  3. 2026-08-11 20:53 UTCEG score recompute
  4. 2026-08-11 20:53 UTCVendor advisory
  5. 2026-08-11 13:42 UTCEPSS rescore
  6. 2026-08-11 03:56 UTCEG score recompute
  7. 2026-08-11 03:56 UTCVendor advisory
  8. 2026-08-10 23:59 UTCEPSS rescore
  9. 2026-08-10 06:44 UTCVendor advisory
  10. 2026-08-09 18:24 UTCEG score recompute
  11. 2026-08-09 18:24 UTCVendor advisory
  12. 2026-08-09 13:46 UTCEPSS rescore
  13. 2026-08-09 13:46 UTCEPSS rescore
  14. 2026-08-09 06:07 UTCEG score recompute
  15. 2026-08-09 06:07 UTCVendor advisory
  16. 2026-08-08 16:36 UTCEPSS rescore
  17. 2026-08-08 04:47 UTCVendor advisory
  18. 2026-08-07 16:27 UTCEG score recompute
  19. 2026-08-07 16:27 UTCVendor advisory
  20. 2026-08-07 16:26 UTCEPSS rescore
  21. 2026-08-06 18:51 UTCEG score recompute
  22. 2026-08-06 18:51 UTCVendor advisory
  23. 2026-08-06 13:46 UTCEPSS rescore
  24. 2026-08-06 00:57 UTCEG score recompute
  25. 2026-08-06 00:57 UTCVendor advisory
  26. 2026-08-05 19:17 UTCEPSS rescore
  27. 2026-08-05 19:17 UTCEPSS rescore
  28. 2026-08-04 15:09 UTCEPSS rescore
  29. 2026-08-04 12:35 UTCEG score recompute
  30. 2026-08-04 12:35 UTCVendor advisory
  31. 2026-08-04 10:37 UTCEPSS rescore
  32. 2026-08-03 23:40 UTCEG score recompute
  33. 2026-08-03 23:40 UTCVendor advisory
  34. 2026-08-03 10:35 UTCEPSS rescore
  35. 2026-08-02 15:28 UTCEG score recompute
  36. 2026-08-02 15:28 UTCVendor advisory
  37. 2026-08-02 02:26 UTCEPSS rescore
  38. 2026-08-01 04:15 UTCEPSS rescore
  39. 2026-07-30 16:27 UTCEPSS rescore
  40. 2026-07-30 01:30 UTCEPSS rescore
  41. 2026-07-28 15:35 UTCEPSS rescore
  42. 2026-07-27 14:12 UTCEPSS rescore
  43. 2026-07-26 14:54 UTCEPSS rescore
  44. 2026-07-26 14:54 UTCEPSS rescore
  45. 2026-07-25 14:17 UTCEPSS rescore
  46. 2026-07-24 14:17 UTCEPSS rescore
  47. 2026-07-24 14:17 UTCEPSS rescore
  48. 2026-07-23 14:18 UTCEPSS rescore
  49. 2026-07-23 14:18 UTCEPSS rescore
  50. 2026-07-23 03:01 UTCEG score recompute
  51. 2026-07-22 14:08 UTCEPSS rescore
  52. 2026-07-21 15:24 UTCEPSS rescore
  53. 2026-07-20 17:08 UTCEPSS rescore
  54. 2026-07-19 14:30 UTCEPSS rescore
  55. 2026-07-19 14:30 UTCEPSS rescore
  56. 2026-07-19 02:28 UTCEPSS rescore
  57. 2026-07-18 10:04 UTCEPSS rescore
  58. 2026-07-18 10:04 UTCEPSS rescore
  59. 2026-07-17 05:54 UTCOSV refresh
  60. 2026-07-16 17:02 UTCEPSS rescore
  61. 2026-07-15 16:57 UTCEPSS rescore
  62. 2026-07-15 16:57 UTCEPSS rescore
  63. 2026-07-15 01:59 UTCEPSS rescore
  64. 2026-07-15 01:59 UTCEPSS rescore
  65. 2026-07-13 22:29 UTCEPSS rescore
  66. 2026-07-13 06:12 UTCEPSS rescore
  67. 2026-07-12 05:46 UTCEPSS rescore
  68. 2026-07-11 08:27 UTCEPSS rescore
  69. 2026-07-09 19:09 UTCEPSS rescore
  70. 2026-07-08 15:15 UTCEPSS rescore
  71. 2026-07-07 13:46 UTCEPSS rescore
  72. 2026-07-06 16:27 UTCEPSS rescore
  73. 2026-07-06 16:27 UTCEPSS rescore
  74. 2026-07-06 02:23 UTCEPSS rescore
  75. 2026-07-06 02:23 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-67030?
CVE-2025-67030 is a high vulnerability published on March 25, 2026. Directory Traversal vulnerability in the extractFile method of org.codehaus.plexus.util.Expand in plexus-utils before 6d780b3378829318ba5c2d29547e0012d5b29642. This allows an attacker to execute arbitrary code
When was CVE-2025-67030 disclosed?
CVE-2025-67030 was first published in the National Vulnerability Database on March 25, 2026, with the most recent update on August 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-67030 actively exploited?
CVE-2025-67030 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 51.0% of all scored CVEs.
What is the CVSS score of CVE-2025-67030?
CVE-2025-67030 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2025-67030?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-67030, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-67030

Explore →

Is Your Infrastructure Affected by CVE-2025-67030?

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