Is org.codehaus.plexus:plexus-utils 3.0 vulnerable?
Maven · 25 releases from 3.0.0 to 3.0.24 · latest org.codehaus.plexus:plexus-utils is 4.2.0 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. org.codehaus.plexus:plexus-utils 3.0.24, the last 3.0 release, is affected by 1 known security advisory (1 high), including CVE-2025-67030. 3 more affect earlier 3.0.x releases. Upgrade to 3.6.1 or later to fix all of them.
mvn versions:use-dep-version -Dincludes=org.codehaus.plexus:plexus-utils -DdepVersion=3.6.1 -DforceVersion=trueIs your project on an affected org.codehaus.plexus:plexus-utils?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting org.codehaus.plexus:plexus-utils 3.0.24
Plexus-Utils has a Directory Traversal vulnerability in its extractFile method
- Affected
- >=4.0.0 <4.0.3 · <3.6.1
- Fixed in
- 3.6.1, 4.0.3
Fixed within 3.0.x, affecting earlier releases
plexus-codehaus vulnerable to directory traversal
- Affected
- <3.0.24
- Fixed in
- 3.0.24
codehaus-plexus vulnerable to XML injection
- Affected
- <3.0.24
- Fixed in
- 3.0.24
OS Command Injection in Plexus-utils
- Affected
- <3.0.16
- Fixed in
- 3.0.16
Every org.codehaus.plexus:plexus-utils 3.0.x release
Affected: 3.0.0 to 3.0.24. Latest org.codehaus.plexus:plexus-utils: 4.2.0.
| Version | Known advisories |
|---|---|
| org.codehaus.plexus:plexus-utils 3.0.24 | CVE-2025-67030 |
| org.codehaus.plexus:plexus-utils 3.0.23 | CVE-2025-67030, CVE-2022-4244, CVE-2022-4245 |
| org.codehaus.plexus:plexus-utils 3.0.22 | CVE-2025-67030, CVE-2022-4244, CVE-2022-4245 |
| org.codehaus.plexus:plexus-utils 3.0.21 | CVE-2025-67030, CVE-2022-4244, CVE-2022-4245 |
| org.codehaus.plexus:plexus-utils 3.0.20 | CVE-2025-67030, CVE-2022-4244, CVE-2022-4245 |
| org.codehaus.plexus:plexus-utils 3.0.19 | CVE-2025-67030, CVE-2022-4244, CVE-2022-4245 |
| org.codehaus.plexus:plexus-utils 3.0.18 | CVE-2025-67030, CVE-2022-4244, CVE-2022-4245 |
| org.codehaus.plexus:plexus-utils 3.0.17 | CVE-2025-67030, CVE-2022-4244, CVE-2022-4245 |
| org.codehaus.plexus:plexus-utils 3.0.16 | CVE-2025-67030, CVE-2022-4244, CVE-2022-4245 |
| org.codehaus.plexus:plexus-utils 3.0.15 | CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487 |
| org.codehaus.plexus:plexus-utils 3.0.14 | CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487 |
| org.codehaus.plexus:plexus-utils 3.0.13 | CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487 |
| org.codehaus.plexus:plexus-utils 3.0.12 | CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487 |
| org.codehaus.plexus:plexus-utils 3.0.11 | CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487 |
| org.codehaus.plexus:plexus-utils 3.0.10 | CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487 |
| org.codehaus.plexus:plexus-utils 3.0.9 | CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487 |
| org.codehaus.plexus:plexus-utils 3.0.8 | CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487 |
| org.codehaus.plexus:plexus-utils 3.0.7 | CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487 |
| org.codehaus.plexus:plexus-utils 3.0.6 | CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487 |
| org.codehaus.plexus:plexus-utils 3.0.5 | CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487 |
| org.codehaus.plexus:plexus-utils 3.0.4 | CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487 |
| org.codehaus.plexus:plexus-utils 3.0.3 | CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487 |
| org.codehaus.plexus:plexus-utils 3.0.2 | CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487 |
| org.codehaus.plexus:plexus-utils 3.0.1 | CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487 |
| org.codehaus.plexus:plexus-utils 3.0.0 | CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487 |
Which of your client projects are still on org.codehaus.plexus:plexus-utils 3.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.codehaus.plexus:plexus-utils version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other org.codehaus.plexus:plexus-utils versions
- org.codehaus.plexus:plexus-utils 3.3
- org.codehaus.plexus:plexus-utils 3.2
- org.codehaus.plexus:plexus-utils 3.1
- org.codehaus.plexus:plexus-utils 2.1
- org.codehaus.plexus:plexus-utils 2.0
- org.codehaus.plexus:plexus-utils 1.5
- org.codehaus.plexus:plexus-utils 4.2
- org.codehaus.plexus:plexus-utils 4.1
- org.codehaus.plexus:plexus-utils 4.0
- org.codehaus.plexus:plexus-utils 3.6
- org.codehaus.plexus:plexus-utils 3.5
- org.codehaus.plexus:plexus-utils 3.4
- All org.codehaus.plexus:plexus-utils advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.