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.
mvn versions:use-dep-version -Dincludes=org.apache.logging.log4j:log4j-core -DdepVersion=2.25.4 -DforceVersion=trueIs your project on an affected org.apache.logging.log4j:log4j-core?
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
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
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
Apache Log4j does not verify the TLS hostname in its Socket Appender
- Affected
- >=2.0-beta9 <2.25.3
- Fixed in
- 2.25.3
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
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
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
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
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
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
- org.apache.logging.log4j:log4j-core 2.10
- org.apache.logging.log4j:log4j-core 2.9
- org.apache.logging.log4j:log4j-core 2.8
- org.apache.logging.log4j:log4j-core 2.6
- org.apache.logging.log4j:log4j-core 2.5
- org.apache.logging.log4j:log4j-core 2.4
- org.apache.logging.log4j:log4j-core 2.26
- org.apache.logging.log4j:log4j-core 2.25
- org.apache.logging.log4j:log4j-core 2.24
- org.apache.logging.log4j:log4j-core 2.23
- org.apache.logging.log4j:log4j-core 2.22
- org.apache.logging.log4j:log4j-core 2.21
- All org.apache.logging.log4j:log4j-core advisories
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.