Is org.apache.logging.log4j:log4j-core 2.17 vulnerable?
Maven · 3 releases from 2.17.0 to 2.17.2 · latest org.apache.logging.log4j:log4j-core is 2.26.1 · checked 18 Nov 2026
Yes: 4 known advisories
Yes. org.apache.logging.log4j:log4j-core 2.17.2, the last 2.17 release, is affected by 4 known security advisories (4 medium), including CVE-2026-34479, CVE-2026-34480, CVE-2026-34477. 1 more affects earlier 2.17.x releases. 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.17.2
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 Core: `verifyHostName` attribute silently ignored in TLS configuration
- Affected
- >=2.12.0 <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
Fixed within 2.17.x, affecting earlier releases
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
Every org.apache.logging.log4j:log4j-core 2.17.x release
Affected: 2.17.0 to 2.17.2. Latest org.apache.logging.log4j:log4j-core: 2.26.1.
| Version | Known advisories |
|---|---|
| org.apache.logging.log4j:log4j-core 2.17.2 | CVE-2026-34479, CVE-2026-34480, CVE-2026-34477, CVE-2025-68161 |
| org.apache.logging.log4j:log4j-core 2.17.1 | CVE-2026-34479, CVE-2026-34480, CVE-2026-34477, CVE-2025-68161 |
| org.apache.logging.log4j:log4j-core 2.17.0 | CVE-2026-34479, CVE-2026-34480, CVE-2026-34477, CVE-2025-68161, CVE-2021-44832 |
Which of your client projects are still on org.apache.logging.log4j:log4j-core 2.17?
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.20
- org.apache.logging.log4j:log4j-core 2.19
- org.apache.logging.log4j:log4j-core 2.18
- org.apache.logging.log4j:log4j-core 2.16
- org.apache.logging.log4j:log4j-core 2.15
- org.apache.logging.log4j:log4j-core 2.14
- 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.