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=true

Is your project on an affected org.apache.logging.log4j:log4j?

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

Security advisories for org.apache.logging.log4j:log4j

  • LowCVE-2020-9488GHSA-vwqq-5vrc-xw9h5 Jun 2020

    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
  • CriticalCVE-2017-5645GHSA-fxph-q3j8-mv876 Jan 2020

    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?

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.