Apache Log4j Core: Missing TLS hostname verification in Socket appender

Summary

The 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 https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName system property is set to true. This issue may allow a man-in-the-middle attacker to intercept or redirect log traffic under the following conditions: • The attacker is able to intercept or redirect network traffic between the client and the log receiver. • The attacker can present a server certificate issued by a certification authority trusted by the Socket Appender’s configured trust store (or by the default Java trust store if no custom trust store is configured). Users are advised to upgrade to Apache Log4j Core version 2.25.3, which addresses this issue. As an alternative mitigation, the Socket Appender may be configured to use a private or restricted trust root to limit the set of trusted certificates.

Timeline

1. Dec 18, 2025, 8:47 PM UTCCVE published
2. Dec 18, 2025, 9:34 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: partial

3. Apr 10, 2026, 4:18 PM UTCRecord last updated

Affected versions

• org.apache.logging.log4j:log4j-core

  From 2.0-beta9 · fixed in 2.25.3; From 3.0.0-alpha1 · through 3.0.0-beta3

• org.apache.logging.log4j:log4j-coreMaven

  From 2.0-beta9 · fixed in 2.25.3

References 6