CVE-2026-34477: Apache Log4j Core · Improper Validation of Certificate with Host Mismatch
Affects Apache Log4j CoreSource CVE Database V5
Mentioned vulnerabilities
Not known to be exploited · CVSS 6.3 Medium : upgrade to 2.25.4 when convenient.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.25.4
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade Apache to 2.25.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software FoundationApache Log4j Core | Affected
| Fixed in
|
MavenApache Software Foundation/org.apache.logging.log4j:log4j-corepkg:maven/Apache Software Foundation/org.apache.logging.log4j:log4j-coreOther threats | Affected
| Fixed in
|
Mavenorg.apache.logging.log4j/log4j-corepkg:maven/org.apache.logging.log4j/log4j-coreOther threats | Affected
| Fixed in– |
CPE configurations (1)
cpe:2.3:a:apache:log4j:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should upgrade to Apache Log4j Core version 2.25.4, which corrects the improper hostname verification issue. No other mitigations are specified or required as the fix is available. Patch status is confirmed by the vendor advisory recommending this upgrade.
Description
CVE-2026-34477 is a vulnerability in Apache Log4j Core affecting versions from 2.12.0 through 2.25.3. It involves improper validation of TLS certificates when hostname verification is configured via the <Ssl> element's verifyHostName attribute, which was silently ignored in these versions. This flaw allows a network attacker to potentially perform man-in-the-middle attacks if certain conditions are met, such as using SMTP, Socket, or Syslog appenders with TLS configured and the attacker presenting a trusted certificate. The issue does not affect the HTTP appender, which verifies hostnames correctly. Users are advised to upgrade to version 2.25.
References
- github.com/apache/logging-log4j2/pull/4075 (opens in a new tab)
- logging.apache.org/security.html (opens in a new tab)
- logging.apache.org/cyclonedx/vdr.xml (opens in a new tab)
- logging.apache.org/log4j/2.x/manual/appenders/network.html (opens in a new tab)
- lists.apache.org/thread/lkx8cl46t2bvkcwfcb2pd43ygc097lq4 (opens in a new tab)