Apache Log4j Core: `verifyHostName` attribute silently ignored in TLS configuration
Published 10 Apr 2026 · Updated 10 Sept 2026
Is 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
Affected packages
- Affected
- >=2.12.0 <2.25.4
- Fixed in
- 2.25.4
mvn versions:use-dep-version -Dincludes=org.apache.logging.log4j:log4j-core -DdepVersion=2.25.4 -DforceVersion=true- Affected
- >=3.0.0-alpha1 <=3.0.0-beta3
- Fixed in
- No fix released
Details
The fix for CVE-2025-68161 was incomplete: it addressed hostname verification only when enabled via the `log4j2.sslVerifyHostName` system property, but not when configured through the `verifyHostName` attribute of the <Ssl> 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 <Ssl> element.
- The attacker can present a certificate issued by a CA trusted by the appender's configured trust store, or by the default Java trust store if none is configured.
This issue does not affect users of the HTTP appender, which uses a separate `verifyHostname` attribute that was not subject to this bug and verifies host names by default.
Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue.
Is GHSA-6hg6-v5c8-fphq in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.apache.logging.log4j:log4j-core, and gives you the command that fixes it.
More advisories for org.apache.logging.log4j:log4j-core
- MediumCVE-2026-34479Apache Log4j 1 to Log4j 2 bridge: silent log event loss in Log4j1XmlLayout due to unescaped XML 1.0 forbidden characters · 10 Apr 2026
- MediumCVE-2026-34480Apache Log4j Core: Silent log event loss in XmlLayout due to unescaped XML 1.0 forbidden characters · 10 Apr 2026
- MediumCVE-2026-34478Apache Log4j Core: log injection in `Rfc5424Layout` due to silent configuration incompatibility · 10 Apr 2026
- MediumCVE-2025-68161Apache Log4j does not verify the TLS hostname in its Socket Appender · 18 Dec 2025
- HighCVE-2023-26464Apache Log4j 1.x (EOL) allows Denial of Service (DoS) · 10 Mar 2023
- MediumCVE-2021-44832Improper Input Validation and Injection in Apache Log4j2 · 4 Jan 2022
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-34477
- Linkgithub.com/apache/logging-log4j2/pull/4075
- Packagegithub.com/apache/logging-log4j2
- Linklists.apache.org/thread/lkx8cl46t2bvkcwfcb2pd43ygc097lq4
- Linklogging.apache.org/cyclonedx/vdr.xml
- Linklogging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName
- Linklogging.apache.org/security.html#CVE-2026-34477
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.