Is org.apache.commons:commons-collections4 4.0 vulnerable?

Maven · 1 release from 4.0.0 to 4.0.0 · latest org.apache.commons:commons-collections4 is 4.6.0 · checked 18 Nov 2026

Yes: 2 known advisories

Yes. org.apache.commons:commons-collections4 4.0.0, the last 4.0 release, is affected by 2 known security advisories (1 critical, 1 high), including CVE-2015-7501, CVE-2015-6420. Upgrade to 4.1 or later to fix all of them.

Upgrade with:mvn versions:use-dep-version -Dincludes=org.apache.commons:commons-collections4 -DdepVersion=4.1 -DforceVersion=true

Is your project on an affected org.apache.commons:commons-collections4?

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.apache.commons:commons-collections4 4.0.0

  • CriticalCVE-2015-7501GHSA-fjq5-5j5f-mvxh13 May 2022

    Deserialization of Untrusted Data in Apache commons collections

    Affected
    <4.1
    Fixed in
    4.1
  • HighCVE-2015-6420GHSA-6hgm-866r-3cjv15 Jun 2020

    Insecure Deserialization in Apache Commons Collection

    Affected
    <4.1
    Fixed in
    4.1

Which of your client projects are still on org.apache.commons:commons-collections4 4.0?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.apache.commons:commons-collections4 version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other org.apache.commons:commons-collections4 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.