Log interception via missing TLS hostname verification
Published Dec 18, 2025 · Updated Dec 18, 2025
Certificate validation in Apache Log4j Core 2.0-beta9 through 2.25.2 allows man-in-the-middle attackers to intercept log traffic. SSLSocketManager creates the TLS socket without setting an endpoint-identification algorithm, so a trusted certificate for another host is accepted. Exploitation requires the Socket Appender to use TLS, traffic interception or redirection, and a certificate chaining to its trust store.
Summary
What happened
Certificate validation in Apache Log4j Core 2.0-beta9 through 2.25.2 allows man-in-the-middle attackers to intercept log traffic. SSLSocketManager creates the TLS socket without setting an endpoint-identification algorithm, so a trusted certificate for another host is accepted. Exploitation requires the Socket Appender to use TLS, traffic interception or redirection, and a certificate chaining to its trust store.
The record
- CVE
- CVE-2025-68161
- Published
- Dec 18, 2025
- Updated
- Dec 18, 2025
- Vendor
- The Apache Software Foundation
- Product
- Apache Log4j Core
- Classifications
- CWE-297, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 18, 2025CVE publishedPublication date reported by the CVE source.
- Dec 18, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0-beta9 <2.25.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo