commons-collections:commons-collections vulnerabilities
- Registry
- Maven
- Latest
- 20040616
2 known advisories
The latest version, 20040616, is not affected by any of them. Projects on older versions may be.
Update to the latest version:
mvn versions:use-dep-version -Dincludes=commons-collections:commons-collections -DdepVersion=20040616 -DforceVersion=trueIs your project on an affected commons-collections:commons-collections?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for commons-collections:commons-collections
Deserialization of Untrusted Data in Apache commons collections
- Affected
- <3.2.2
- Fixed in
- 3.2.2
Insecure Deserialization in Apache Commons Collection
- Affected
- <3.2.2
- Fixed in
- 3.2.2
Is your commons-collections:commons-collections version vulnerable?
Which of your client projects still run an old commons-collections:commons-collections?
NPMscan reads the pom.xml, build.gradle and gradle.lockfile in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Maven packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Maven registry.