How severe is GHSA-6fmv-xxpf-w3cw?

No CVSS score has been assigned to GHSA-6fmv-xxpf-w3cw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6fmv-xxpf-w3cw?

GHSA-6fmv-xxpf-w3cw affects the following packages: org.codehaus.plexus:plexus-utils (Maven), org.codehaus.plexus:plexus-utils (Maven). Ecosystems affected: Maven.

How do I fix GHSA-6fmv-xxpf-w3cw?

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 GHSA-6fmv-xxpf-w3cw is resolved across your whole dependency graph.

How do I detect GHSA-6fmv-xxpf-w3cw 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-6fmv-xxpf-w3cw 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 GHSA-6fmv-xxpf-w3cw?

O3 pinpoints whether GHSA-6fmv-xxpf-w3cw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-6fmv-xxpf-w3cw actively exploited in the wild?

No public exploit code has been indexed for GHSA-6fmv-xxpf-w3cw 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 type of vulnerability is GHSA-6fmv-xxpf-w3cw?

GHSA-6fmv-xxpf-w3cw 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 GHSA-6fmv-xxpf-w3cw published, and has it been updated?

GHSA-6fmv-xxpf-w3cw was published on March 25, 2026 and was last updated on April 8, 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

GHSA-6fmv-xxpf-w3cw

GHSA-6fmv-xxpf-w3cw is a Path Traversal vulnerability in org.codehaus.plexus:plexus-utils. O3 Security confirms whether GHSA-6fmv-xxpf-w3cw is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

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

Also known asCVE-2025-67030

Published

Mar 25, 2026

Updated

Apr 8, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

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
☕Maven	`org.codehaus.plexus:plexus-utils`	all versions	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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 GHSA-6fmv-xxpf-w3cw 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 pinpoints whether GHSA-6fmv-xxpf-w3cw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-6fmv-xxpf-w3cw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-6fmv-xxpf-w3cw in your dependencies?

O3 detects GHSA-6fmv-xxpf-w3cw across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works