CVE-2025-68161 affects the Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2. The appender fails to verify the hostname in the peer's TLS certificate, even when hostname verification is explicitly enabled through the verifyHostName configuration attribute or log4j2.sslVerifyHostName system property. An attacker able to intercept or redirect the connection and present a certificate issued by a trusted certification authority may impersonate the log receiver and intercept or redirect log traffic. Version 2.25.3 corrected the system-property-controlled verification, but the configuration-attribute path remained vulnerable; that incomplete fix is tracked as CVE-2026-34477 and corrected in version 2.25.4.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 2 candidates as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
60 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An earlier Apache Log4j Core hostname-verification vulnerability. Its fix addressed verification enabled through the log4j2.sslVerifyHostName system property but failed to address the verifyHostName XML configuration attribute. That remaining issue is identified separately as CVE-2026-34477.
A TLS hostname-verification flaw in Apache Log4j Core's Socket Appender can allow a man-in-the-middle attacker to intercept or redirect log traffic. Exploitation requires the attacker to intercept or redirect traffic between the client and log receiver and present a certificate issued by a trusted certification authority. Apache Log4j Core 2.25.3 fixes the issue; using a private or restricted trust root is an alternative mitigation. The reference reports available exploits but does not report exploitation in the wild.
A vulnerability in Oracle Enterprise Manager Cloud Control addressed by the September 15, 2026 patch release; no further technical details are provided.
A potential Apache Log4j library vulnerability affecting SAP NetWeaver AS Java.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.