VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.codehaus.plexus:plexus-utils: vulnerability history, versions and safety

org.codehaus.plexus:plexus-utils is a package in the Maven ecosystem. Vulert records 4 vulnerabilities for it across 83 releases, from May 2022 to Mar 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded C1 H2 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 25 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all org.codehaus.plexus:plexus-utils vulnerabilities

Vulert verdict on org.codehaus.plexus:plexus-utils 4.1.0 i

Updated on 22 Oct 2026

Good news: 4.1.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 4.

Package health score 69/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

What to do: Stay on 4.1.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 4.1.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 4.1.0 — unaffected i
  • Vulnerabilities on record 4 over 3 years · 1 in the last year i
  • Latest disclosure 25 Mar 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 329 packages i
  • Stars 42 i
  • OpenSSF scorecard 4/10 i
  • Last release 2 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by Maven Central, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for org.codehaus.plexus:plexus-utils, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
3.6.2 19 Aug 2026 H1 Apache-2.0 Yes Details →
4.1.0 19 Aug 2026 none Apache-2.0 — Details →
3.6.1 01 Apr 2026 H1 Apache-2.0 Yes Details →
4.0.3 27 Mar 2026 none Apache-2.0 — Details →
3.6.0 15 Dec 2024 H1 Apache-2.0 Yes Details →
4.0.2 23 Sep 2024 H1 Apache-2.0 Yes Details →
4.0.1 13 Apr 2024 H1 Apache-2.0 Yes Details →
4.0.0 22 May 2023 H1 Apache-2.0 Yes Details →
3.5.1 02 Mar 2023 H1 Apache-2.0 Yes Details →
3.5.0 23 Oct 2022 H1 Apache-2.0 Yes Details →
3.4.2 17 May 2022 H1 Apache-2.0 Yes Details →
3.3.1 27 Dec 2021 H1 Apache-2.0 Yes Details →
3.4.1 27 Aug 2021 H1 Apache-2.0 Yes Details →
3.4.0 29 Jul 2021 H1 Apache-2.0 Yes Details →
3.3.0 11 Oct 2019 H1 Apache-2.0 Yes Details →
3.2.1 10 Jul 2019 H1 Apache-2.0 Yes Details →
3.2.0 10 Mar 2019 H1 Apache-2.0 Yes Details →
3.1.1 21 Dec 2018 H1 Apache-2.0 Yes Details →
3.1.0 03 Aug 2017 H1 Apache-2.0 Yes Details →
3.0.24 07 May 2016 H1 Apache-2.0 Yes Details →
3.0.23 04 May 2016 H2 M1 Apache-2.0 Yes Details →
3.0.22 07 Apr 2015 H2 M1 Apache-2.0 Yes Details →
3.0.21 14 Nov 2014 H2 M1 Apache-2.0 Yes Details →
3.0.20 18 Oct 2014 H2 M1 Apache-2.0 Yes Details →
3.0.19 18 Oct 2014 H2 M1 Apache-2.0 Yes Details →
3.0.18 27 Sep 2014 H2 M1 Apache-2.0 Yes Details →
3.0.17 27 Jan 2014 H2 M1 Apache-2.0 Yes Details →
3.0.16 21 Dec 2013 H2 M1 Apache-2.0 Yes Details →
3.0.15 19 Aug 2013 C1 H2 M1 Apache-2.0 Yes Details →
3.0.14 06 Aug 2013 C1 H2 M1 Apache-2.0 Yes Details →
3.0.13 04 Aug 2013 C1 H2 M1 Apache-2.0 Yes Details →
3.0.12 01 Aug 2013 C1 H2 M1 Apache-2.0 Yes Details →
3.0.11 31 Jul 2013 C1 H2 M1 Apache-2.0 Yes Details →
3.0.10 28 Nov 2012 C1 H2 M1 Apache-2.0 Yes Details →
3.0.9 18 Nov 2012 C1 H2 M1 Apache-2.0 Yes Details →
3.0.8 20 Sep 2012 C1 H2 M1 Apache-2.0 Yes Details →
3.0.7 16 Sep 2012 C1 H2 M1 Apache-2.0 Yes Details →
3.0.6 15 Sep 2012 C1 H2 M1 Apache-2.0 Yes Details →
3.0.5 20 Aug 2012 C1 H2 M1 Apache-2.0 Yes Details →
3.0.4 06 Aug 2012 C1 H2 M1 Apache-2.0 Yes Details →
3.0.3 01 Aug 2012 C1 H2 M1 Apache-2.0 Yes Details →
3.0.2 09 Jul 2012 C1 H2 M1 Apache-2.0 Yes Details →
3.0.1 05 May 2012 C1 H2 M1 Apache-2.0 Yes Details →
3.0 23 Jun 2011 C1 H2 M1 non-standard Yes Details →
2.1 09 Jun 2011 C1 H2 M1 non-standard Yes Details →
2.0.7 03 Mar 2011 C1 H2 M1 Apache-2.0 Yes Details →
2.0.6 09 Feb 2011 C1 H2 M1 Apache-2.0 Yes Details →
2.0.5 25 Apr 2010 C1 H2 M1 Apache-2.0 Yes Details →
2.0.4 22 Apr 2010 C1 H2 M1 Apache-2.0 Yes Details →
2.0.3 06 Apr 2010 C1 H2 M1 Apache-2.0 Yes Details →
2.0.2 29 Mar 2010 C1 H2 M1 Apache-2.0 Yes Details →
2.0.1 19 Oct 2009 C1 H2 M1 Apache-2.0 Yes Details →
2.0.0 22 Sep 2009 C1 H2 M1 Apache-2.0 Yes Details →
1.5.15 05 Jun 2009 C1 H2 M1 Apache-2.0 Yes Details →
1.5.14 05 Jun 2009 C1 H2 M1 Apache-2.0 Yes Details →
1.5.13 05 Jun 2009 C1 H2 M1 Apache-2.0 Yes Details →
1.5.12 29 May 2009 C1 H2 M1 Apache-2.0 Yes Details →
1.5.11 29 May 2009 C1 H2 M1 Apache-2.0 Yes Details →
1.5.10 26 May 2009 C1 H2 M1 Apache-2.0 Yes Details →
1.5.9 28 Apr 2009 C1 H2 M1 Apache-2.0 Yes Details →
1.5.8 09 Feb 2009 C1 H2 M1 Apache-2.0 Yes Details →
1.5.7 16 Jan 2009 C1 H2 M1 Apache-2.0 Yes Details →
1.5.6 01 Aug 2008 C1 H2 M1 Apache-2.0 Yes Details →
1.5.5 03 Jul 2008 C1 H2 M1 Apache-2.0 Yes Details →
1.5.4 18 Jun 2008 C1 H2 M1 Apache-2.0 Yes Details →
1.5.3 13 Jun 2008 C1 H2 M1 Apache-2.0 Yes Details →
1.5.2 13 Jun 2008 C1 H2 M1 Apache-2.0 Yes Details →
1.5.1 21 Feb 2008 C1 H2 M1 Apache-2.0 Yes Details →
1.5 18 Feb 2008 C1 H2 M1 Apache-2.0 Yes Details →
1.4.9 19 Dec 2007 C1 H2 M1 Apache-2.0 Yes Details →
1.4.8 27 Nov 2007 C1 H2 M1 Apache-2.0 Yes Details →
1.4.7 16 Oct 2007 C1 H2 M1 Apache-2.0 Yes Details →
1.4.6 13 Sep 2007 C1 H2 M1 Apache-2.0 Yes Details →
1.4.5 31 Jul 2007 C1 H2 M1 Apache-2.0 Yes Details →
1.4.4 21 Jul 2007 C1 H2 M1 Apache-2.0 Yes Details →
1.4.3 13 Jul 2007 C1 H2 M1 Apache-2.0 Yes Details →
1.4.2 20 May 2007 C1 H2 M1 Apache-2.0 Yes Details →
1.4.1 10 Mar 2007 C1 H2 M1 Apache-2.0 Yes Details →
1.4 09 Jan 2007 C1 H2 M1 — Yes Details →
1.4-alpha-1 11 Dec 2006 C1 H2 M1 — Yes Details →
1.3 29 Sep 2006 C1 H2 M1 — Yes Details →
1.2 19 Apr 2006 C1 H2 M1 — Yes Details →
1.1 12 Jan 2006 C1 H2 M1 — Yes Details →
1.0.5 07 Dec 2005 C1 H2 M1 — Yes Details →
1.0.4 11 Oct 2005 C1 H2 M1 — Yes Details →

All 85 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2023 2
  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for org.codehaus.plexus:plexus-utils

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-1000487: OS Command Injection in Plexus-utils 9.8 critical 3.0.16 13 May 2022
CVE-2022-4244: Directory Traversal Vulnerability in org.codehaus.plexus:plexus-utils 7.5 high 3.0.24 25 Sep 2023
CVE-2022-4245: XML Injection Vulnerability in org.codehaus.plexus:plexus-utils 4.3 medium 3.0.24 25 Sep 2023
CVE-2025-67030: Plexus-Utils Directory Traversal Vulnerability in extractFile Method N/A high 4.0.3 25 Mar 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About org.codehaus.plexus:plexus-utils

Is org.codehaus.plexus:plexus-utils safe to use?

Vulert records 4 vulnerabilities for org.codehaus.plexus:plexus-utils in Maven: 1 critical, 2 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is org.codehaus.plexus:plexus-utils's Vulert package health score?

Vulert scores org.codehaus.plexus:plexus-utils 69/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of org.codehaus.plexus:plexus-utils affected?

No. 4.1.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of org.codehaus.plexus:plexus-utils should I use?

4.1.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does org.codehaus.plexus:plexus-utils have?

4 vulnerabilities are recorded for org.codehaus.plexus:plexus-utils in the Maven ecosystem: 1 critical, 2 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.codehaus.plexus:plexus-utils vulnerabilities disclosed?

1 vulnerability was recorded for org.codehaus.plexus:plexus-utils in the last 12 months, and the oldest entry in this database dates to 13 May 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of org.codehaus.plexus:plexus-utils are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor org.codehaus.plexus:plexus-utils for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.codehaus.plexus:plexus-utils version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.