How severe is CVE-2025-67030?

CVE-2025-67030 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2025-67030?

CVE-2025-67030 affects the following packages: org.codehaus.plexus:plexus-utils (Maven), org.codehaus.plexus:plexus-utils (Maven). Ecosystems affected: Maven.

How do I fix CVE-2025-67030?

Update org.codehaus.plexus:plexus-utils to 4.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-67030 is resolved across your whole dependency graph.

How do I detect CVE-2025-67030 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.codehaus.plexus:plexus-utils, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-67030 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2025-67030?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-67030 can be triaged on real exposure rather than presence alone.

Is CVE-2025-67030 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-67030 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-67030?

CVE-2025-67030 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 50th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-67030?

CVE-2025-67030 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2025-67030 published, and has it been updated?

CVE-2025-67030 was published on March 25, 2026 and was last updated on September 18, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2025-67030 — plexus-utils

HIGHFix: codehaus-plexus/plexus-utils@6d780b3

CVE-2025-67030 is a high-severity (CVSS 8.8) Path Traversal vulnerability in org.codehaus.plexus:plexus-utils. A fix is available for org.codehaus.plexus:plexus-utils — see the affected versions and patch details below.

Plexus-Utils has a Directory Traversal vulnerability in its extractFile method

Also known asGHSA-6fmv-xxpf-w3cw

Published

Mar 25, 2026

Updated

Sep 18, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Sep 21, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-67030.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs50th percentile — riskier than 50% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2025-67030 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

2 pkgs affected

☕org.codehaus.plexus:plexus-utils☕org.codehaus.plexus:plexus-utils

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.codehaus.plexus:plexus-utils`	≥ 4.0.0&&< 4.0.3	4.0.3`org.codehaus.plexus:plexus-utils:4.0.3`
☕Maven	`org.codehaus.plexus:plexus-utils`	all versions	3.6.1`org.codehaus.plexus:plexus-utils:3.6.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.codehaus.plexus:plexus-utils, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.codehaus.plexus:plexus-utils to 4.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-67030 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-67030 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2025-67030. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Product	Fixed in	Advisory
Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14	`plexus-utils`	RHSA-2026:17668
Red Hat build of Quarkus 3.20.6	`plexus-utils`	RHSA-2026:7109
Red Hat build of Quarkus 3.27.3	`plexus-utils`	RHSA-2026:7380
Red Hat Enterprise Linux 10	`plexus-utils-0:3.5.1-9.el10_2`	RHSA-2026:38514
Red Hat Enterprise Linux 10.0 Extended Update Support	`plexus-utils-0:3.5.1-8.el10_0.1`	RHSA-2026:35991
Red Hat Enterprise Linux 8	`maven:3.8-8100020260520141024.b249b32d`	RHSA-2026:40841
Red Hat Enterprise Linux 8	`javapackages-tools:201801-8100020260520141124.88f2bc72`	RHSA-2026:41948
Red Hat Enterprise Linux 8.8 Telecommunications Update Service	`maven:3.8-8080020260615155417.a1d5b3e2`	RHSA-2026:35996

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-67030 in your dependencies?

O3 Security finds CVE-2025-67030 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works