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.

Upgrade with:mvn versions:use-dep-version -Dincludes=org.codehaus.plexus:plexus-utils -DdepVersion=3.6.1 -DforceVersion=true

Is your project on an affected org.codehaus.plexus:plexus-utils?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

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

  • HighCVE-2025-67030GHSA-6fmv-xxpf-w3cw25 Mar 2026

    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

  • HighCVE-2022-4244GHSA-g6ph-x5wf-g33725 Sept 2023

    plexus-codehaus vulnerable to directory traversal

    Affected
    <3.0.24
    Fixed in
    3.0.24
  • MediumCVE-2022-4245GHSA-jcwr-x25h-x5fh25 Sept 2023

    codehaus-plexus vulnerable to XML injection

    Affected
    <3.0.24
    Fixed in
    3.0.24
  • CriticalCVE-2017-1000487GHSA-8vhq-qq4p-grq313 May 2022

    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.

VersionKnown advisories
org.codehaus.plexus:plexus-utils 3.0.24CVE-2025-67030
org.codehaus.plexus:plexus-utils 3.0.23CVE-2025-67030, CVE-2022-4244, CVE-2022-4245
org.codehaus.plexus:plexus-utils 3.0.22CVE-2025-67030, CVE-2022-4244, CVE-2022-4245
org.codehaus.plexus:plexus-utils 3.0.21CVE-2025-67030, CVE-2022-4244, CVE-2022-4245
org.codehaus.plexus:plexus-utils 3.0.20CVE-2025-67030, CVE-2022-4244, CVE-2022-4245
org.codehaus.plexus:plexus-utils 3.0.19CVE-2025-67030, CVE-2022-4244, CVE-2022-4245
org.codehaus.plexus:plexus-utils 3.0.18CVE-2025-67030, CVE-2022-4244, CVE-2022-4245
org.codehaus.plexus:plexus-utils 3.0.17CVE-2025-67030, CVE-2022-4244, CVE-2022-4245
org.codehaus.plexus:plexus-utils 3.0.16CVE-2025-67030, CVE-2022-4244, CVE-2022-4245
org.codehaus.plexus:plexus-utils 3.0.15CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487
org.codehaus.plexus:plexus-utils 3.0.14CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487
org.codehaus.plexus:plexus-utils 3.0.13CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487
org.codehaus.plexus:plexus-utils 3.0.12CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487
org.codehaus.plexus:plexus-utils 3.0.11CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487
org.codehaus.plexus:plexus-utils 3.0.10CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487
org.codehaus.plexus:plexus-utils 3.0.9CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487
org.codehaus.plexus:plexus-utils 3.0.8CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487
org.codehaus.plexus:plexus-utils 3.0.7CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487
org.codehaus.plexus:plexus-utils 3.0.6CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487
org.codehaus.plexus:plexus-utils 3.0.5CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487
org.codehaus.plexus:plexus-utils 3.0.4CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487
org.codehaus.plexus:plexus-utils 3.0.3CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487
org.codehaus.plexus:plexus-utils 3.0.2CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487
org.codehaus.plexus:plexus-utils 3.0.1CVE-2025-67030, CVE-2022-4244, CVE-2022-4245, CVE-2017-1000487
org.codehaus.plexus:plexus-utils 3.0.0CVE-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

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.