Is org.apache.logging.log4j:log4j 2.13 vulnerable?

Maven · 4 releases from 2.13.0 to 2.13.3 · latest org.apache.logging.log4j:log4j is 2.26.1 · checked 18 Nov 2026

No known advisories in the last release

org.apache.logging.log4j:log4j 2.13.3, the last 2.13 release, has no known advisories. 1 advisory affects earlier 2.13.x releases, so update to 2.13.3.

Update within 2.13:mvn versions:use-dep-version -Dincludes=org.apache.logging.log4j:log4j -DdepVersion=2.13.3 -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

Fixed within 2.13.x, affecting earlier releases

  • 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

Every org.apache.logging.log4j:log4j 2.13.x release

Affected: 2.13.0 to 2.13.1. 2.13.2 and later are not affected. Latest org.apache.logging.log4j:log4j: 2.26.1.

VersionKnown advisories
org.apache.logging.log4j:log4j 2.13.3None
org.apache.logging.log4j:log4j 2.13.2None
org.apache.logging.log4j:log4j 2.13.1CVE-2020-9488
org.apache.logging.log4j:log4j 2.13.0CVE-2020-9488

Which of your client projects are still on org.apache.logging.log4j:log4j 2.13?

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

Other org.apache.logging.log4j:log4j 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.