CVE-2025-68161: Apache Log4j Core · Improper Validation of Certificate with Host Mismatch
Affects Apache Log4j CoreSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 2.25.3 when convenient.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.25.3
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 18 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Upgrade org.apache.logging.log4j/log4j-core to 2.25.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Mavenorg.apache.logging.log4j/log4j-corepkg:maven/org.apache.logging.log4j/log4j-coreOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Apache Log4j Core to version 2.25.3, which contains the official fix for this vulnerability. Alternatively, configure the Socket Appender to use a private or restricted trust root to limit the set of trusted certificates. Patch status is confirmed by the vendor advisory. No other mitigations are indicated.
Description
Apache Log4j Core versions 2.0-beta9 through 2.25.2 contain a vulnerability in the Socket Appender where TLS hostname verification is not properly performed, even if configured to do so. This flaw can allow a man-in-the-middle attacker to intercept or redirect log traffic if they can present a trusted certificate and intercept network traffic. The issue is addressed in version 2.25.3. Users can alternatively mitigate by restricting the trust root to limit trusted certificates.
References
- github.com/apache/logging-log4j2/pull/4002 (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/systemproperties.html (opens in a new tab)
- logging.apache.org/log4j/2.x/manual/appenders/network.html (opens in a new tab)
- lists.apache.org/thread/xr33kyxq3sl67lwb61ggvm1fzc8k7dvx (opens in a new tab)
- openwall.com/lists/oss-security/2025/12/18/1 (opens in a new tab)
- lists.debian.org/debian-lts-announce/2026/01/msg00015.html (opens in a new tab)