Servers and applications
CVE-2026-34477
The fix for CVE-2025-68161 https://logging.apache.org/security.html#CVE-2025-68161 was incomplete: it addressed hostname verification only when enabled via the log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName system property, but not when configured through the verifyHostName…
- Severity
- Medium 6.3
- Published
- 10 Apr 2026
- Last changed
- 26 Oct 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 2.25.4
- Exploit chance
- 0.6% in the next 30 daysHigher than 47% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · Only under certain conditions · No login needed · No user action needed
- Attacker can
- Read some data
- CVSS vector
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X- Sources
- NVD
Description
The fix for CVE-2025-68161 https://logging.apache.org/security.html#CVE-2025-68161 was incomplete: it addressed hostname verification only when enabled via the log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName system property, but not when configured through the verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName attribute of the element.
Although the verifyHostName configuration attribute was introduced in Log4j Core 2.12.0, it was silently ignored in all versions through 2.25.3, leaving TLS connections vulnerable to interception regardless of the configured value.
A network-based attacker may be able to perform a man-in-the-middle attack when all of the following conditions are met:
- An SMTP, Socket, or Syslog appender is in use.
- TLS is configured via a nested element.
Affected software
| Software | Affected versions |
|---|---|
Apache Log4jServers and applications · cpe:a:apache:log4j |
All 7 release lines
|
About Apache Log4j
Java library for logging
- GitHub stars
- 3,645GitHub, 15 Nov 2026
- Forks
- 1,761GitHub, 15 Nov 2026
- Latest release
- rel/2.26.1GitHub, 15 Nov 2026
- Released
- 2 Jul 2026GitHub
- Developer
- Apache Software FoundationWikidata
- License
- Apache Software License 2.0Wikidata
- Written in
- JavaWikidata
- First published on GitHub
- 12 Jun 2013GitHub
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 2 | 2.26.1 | Yes |
| 2.12 | 2.12.4 | Ended 14 Dec 2021 |
| 2.3 | 2.3.2 | Ended 20 Sept 2015 |
| 1 | 1.2.17 | Ended 15 Oct 2015 |
From endoflife.date.
Vulnerabilities in Apache Log4j
- In our list
- 20
- Published in the last 12 months
- 7
- Critical, last 12 months
- 0
- High, last 12 months
- 0
- Known exploited
- 2
- CVE-2026-49844Improper encoding of non-finite floating-point values during MapMessage JSON serialization in Apache Log4j API produces output that is not valid JSON. This issue affects Apache Log4j API versions 2.13.1 through 2.25.4 and version 2.26.0. The fix for CVE-2026-34481 did not cover all code paths: when a MapMessage contains a non-finite IEEE 754 value (NaN, Infinity, or -Infinity),…Medium 6.3 10 Jul 2026
- CVE-2026-34481Apache Log4j's JsonTemplateLayout https://logging.apache.org/log4j/2.x/manual/json-template-layout.html , in versions up to and including 2.25.3, produces invalid JSON output when log events contain non-finite floating-point values (NaN, Infinity, or -Infinity), which are prohibited by RFC 8259. This may cause downstream log processing systems to reject or fail to index affected records. An…Medium 6.3 10 Apr 2026
- CVE-2026-34480Apache Log4j Core's XmlLayout https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout , in versions up to and including 2.25.3, fails to sanitize characters forbidden by the XML 1.0 specification https://www.w3.org/TR/xml/#charsets producing invalid XML output whenever a log message or MDC value contains such characters. The impact depends on the StAX implementation in use: * JRE…Medium 6.9 10 Apr 2026
- CVE-2026-34479The Log4j1XmlLayout from the Apache Log4j 1-to-Log4j 2 bridge fails to escape characters forbidden by the XML 1.0 standard, producing malformed XML output. Conforming XML parsers are required to reject documents containing such characters with a fatal error, which may cause downstream log processing systems to drop or fail to index affected records. Two groups of users are affected: * Those…Medium 6.9 10 Apr 2026
- CVE-2026-34478Apache Log4j Core's Rfc5424Layout https://logging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout , in versions 2.21.0 through 2.25.3, is vulnerable to log injection via CRLF sequences due to undocumented renames of security-relevant configuration attributes. Two distinct issues affect users of stream-based syslog services who configure Rfc5424Layout directly: * The newLineEscape…Medium 6.9 10 Apr 2026
- CVE-2025-68161The Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not perform TLS hostname verification of the peer certificate, even when the verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName configuration attribute or the log4j2.sslVerifyHostName…Medium 6.3 18 Dec 2025