Is org.apache.logging.log4j:log4j-core 2.25 vulnerable?
Maven · 6 releases from 2.25.0 to 2.25.5 · latest org.apache.logging.log4j:log4j-core is 2.26.1 · checked 18 Nov 2026
No known advisories in the last release
org.apache.logging.log4j:log4j-core 2.25.5, the last 2.25 release, has no known advisories. 5 advisories affect earlier 2.25.x releases, so update to 2.25.5.
mvn versions:use-dep-version -Dincludes=org.apache.logging.log4j:log4j-core -DdepVersion=2.25.5 -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
Fixed within 2.25.x, affecting earlier releases
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: log injection in `Rfc5424Layout` due to silent configuration incompatibility
- Affected
- >=2.21.0 <2.25.4 · >=3.0.0-beta1 <=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
Every org.apache.logging.log4j:log4j-core 2.25.x release
Affected: 2.25.0 to 2.25.3. 2.25.4 and later are not affected. Latest org.apache.logging.log4j:log4j-core: 2.26.1.
| Version | Known advisories |
|---|---|
| org.apache.logging.log4j:log4j-core 2.25.5 | None |
| org.apache.logging.log4j:log4j-core 2.25.4 | None |
| org.apache.logging.log4j:log4j-core 2.25.3 | CVE-2026-34479, CVE-2026-34480, CVE-2026-34478, CVE-2026-34477 |
| org.apache.logging.log4j:log4j-core 2.25.2 | CVE-2026-34479, CVE-2026-34480, CVE-2026-34478, CVE-2026-34477, CVE-2025-68161 |
| org.apache.logging.log4j:log4j-core 2.25.1 | CVE-2026-34479, CVE-2026-34480, CVE-2026-34478, CVE-2026-34477, CVE-2025-68161 |
| org.apache.logging.log4j:log4j-core 2.25.0 | CVE-2026-34479, CVE-2026-34480, CVE-2026-34478, CVE-2026-34477, CVE-2025-68161 |
Which of your client projects are still on org.apache.logging.log4j:log4j-core 2.25?
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.