Is org.apache.logging.log4j:log4j-core 2.7 vulnerable?

Maven · 1 release from 2.7.0 to 2.7.0 · latest org.apache.logging.log4j:log4j-core is 2.26.1 · checked 18 Nov 2026

Yes: 9 known advisories

Yes. org.apache.logging.log4j:log4j-core 2.7.0, the last 2.7 release, is affected by 9 known security advisories (3 critical, 1 high, 4 medium, 1 low), including CVE-2021-45046, CVE-2021-44228, CVE-2017-5645. Upgrade to 2.25.4 or later to fix all of them.

Upgrade with:mvn versions:use-dep-version -Dincludes=org.apache.logging.log4j:log4j-core -DdepVersion=2.25.4 -DforceVersion=true

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

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.logging.log4j:log4j-core 2.7.0

  • MediumCVE-2026-34479GHSA-h383-gmxw-35v210 Apr 2026

    Apache Log4j 1 to Log4j 2 bridge: silent log event loss in Log4j1XmlLayout due to unescaped XML 1.0 forbidden characters

    Affected
    >=2.7 <2.25.4 · >=3.0.0-beta1 <=3.0.0-beta2
    Fixed in
    2.25.4
  • MediumCVE-2026-34480GHSA-3pxv-7cmr-fjr410 Apr 2026

    Apache Log4j Core: Silent log event loss in XmlLayout due to unescaped XML 1.0 forbidden characters

    Affected
    >=2.0-alpha1 <2.25.4 · >=3.0.0-alpha1 <=3.0.0-beta3
    Fixed in
    2.25.4
  • MediumCVE-2025-68161GHSA-vc5p-v9hr-52mj18 Dec 2025

    Apache Log4j does not verify the TLS hostname in its Socket Appender

    Affected
    >=2.0-beta9 <2.25.3
    Fixed in
    2.25.3
  • MediumCVE-2021-44832GHSA-8489-44mv-ggj84 Jan 2022

    Improper Input Validation and Injection in Apache Log4j2

    Affected
    >=2.0-beta7 <2.3.2 · >=2.4 <2.12.4 · >=2.13.0 <2.17.1
    Fixed in
    2.3.2, 2.12.4, 2.17.1
  • HighCVE-2021-45105GHSA-p6xc-xr62-6r2g18 Dec 2021

    Apache Log4j2 vulnerable to Improper Input Validation and Uncontrolled Recursion

    Affected
    >=2.4.0 <2.12.3 · >=2.13.0 <2.17.0 · <2.3.1
    Fixed in
    2.3.1, 2.12.3, 2.17.0
  • CriticalCVE-2021-45046GHSA-7rjr-3q55-vv3314 Dec 2021

    Incomplete fix for Apache Log4j vulnerability

    Affected
    >=2.13.0 <2.16.0 · >=2.4.0 <2.12.2 · <2.3.1
    Fixed in
    2.3.1, 2.12.2, 2.16.0
  • CriticalCVE-2021-44228GHSA-jfh8-c2jp-5v3q10 Dec 2021

    Remote code injection in Log4j

    Affected
    >=2.13.0 <2.15.0 · >=2.0-beta9 <2.3.1 · >=2.4 <2.12.2
    Fixed in
    2.3.1, 2.12.2, 2.15.0
  • 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

Which of your client projects are still on org.apache.logging.log4j:log4j-core 2.7?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.apache.logging.log4j:log4j-core 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-core 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.