org.apache.logging.log4j:log4j vulnerabilities
Apache Log4j Parent
- Registry
- Maven
- Latest
- 2.26.1
- License
- Apache-2.0
2 known advisories
The latest version, 2.26.1, is not affected by any of them. Projects on older versions may be.
Update to the latest version:
mvn versions:use-dep-version -Dincludes=org.apache.logging.log4j:log4j -DdepVersion=2.26.1 -DforceVersion=trueIs your project on an affected org.apache.logging.log4j:log4j?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for org.apache.logging.log4j:log4j
Improper validation of certificate with host mismatch in Apache Log4j SMTP appender
- Affected
- >=2.13.0 <2.13.2 · >=2.4.0 <2.12.3 · <2.3.2
- Fixed in
- 2.3.2, 2.12.3, 2.13.2
Deserialization of Untrusted Data in Log4j
- Affected
- >=2.0 <2.8.2
- Fixed in
- 2.8.2
Is your org.apache.logging.log4j:log4j version vulnerable?
- org.apache.logging.log4j:log4j 2.26No known advisories in 2.26.1
- org.apache.logging.log4j:log4j 2.25No known advisories in 2.25.5
- org.apache.logging.log4j:log4j 2.24No known advisories in 2.24.3
- org.apache.logging.log4j:log4j 2.23No known advisories in 2.23.1
- org.apache.logging.log4j:log4j 2.22No known advisories in 2.22.1
- org.apache.logging.log4j:log4j 2.21No known advisories in 2.21.1
Which of your client projects still run an old org.apache.logging.log4j:log4j?
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.