CVE-2025-68161
Apache Log4j Core: Missing TLS hostname verification in Socket appender
Reported by apache · Published December 18, 2025
The Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not perform TLS hostname verification of the peer certificate, even when the verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName configuration attribute or the log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName system property is set to true. This issue may allow a man-in-the-middle attacker to intercept or redirect log traffic under the following conditions: * The attacker is able to intercept or redirect network traffic between the client and the log receiver. * The attacker can present a server certificate issued by a certification authority trusted by the Socket Appender’s configured trust store (or by the default Java trust store if no custom trust store is configured). Users are advised to upgrade to Apache Log4j Core version 2.25.3, which addresses this issue. As an alternative mitigation, the Socket Appender may be configured to use a private or restricted trust root to limit the set of trusted certificates.
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Apache Software Foundation | Apache Log4j Core | 2.0-beta9, 3.0.0-alpha1 |
| chainguard | celeborn-0.5 | 0 |
| chainguard | elasticsearch-9.1 | 0 |
| wolfi | flink-2.2 | 0 |
| chainguard | neo4j-2025.09 | 0 |
| chainguard | spark-4.0 | 0 |
| chainguard | confluent-kafka | 0 |
| chainguard | apache-hop-fips | 0 |
| wolfi | kserve-modelmesh | 0 |
| wolfi | flink-2.0 | 0 |
| wolfi | confluent-kafka | 0 |
| chainguard | confluent-kafka-jre-bcfips | 0 |
| chainguard | sonarqube | 0 |
| wolfi | neo4j-5.26 | 0 |
| chainguard | py3-vllm-cuda-12.4 | 0 |
| Maven | org.apache.logging.log4j:log4j-core | 2.0-beta9 |
| chainguard | elasticsearch-8.19 | 0 |
| wolfi | airflow-3 | 0 |
| wolfi | kafka-4.0 | 0 |
| chainguard | wso2is | 0 |
…and 107 more
Timeline
- Dec 18, 2025 CVE Published
- Dec 19, 2025 EPSS Score (30 in total, the first dated here)
- Mar 17, 2026 Security Advisory (9 in total, the first dated here)
- Mar 26, 2026 Coalition ESS Score (2 in total, the first dated here)
- Aug 11, 2026 Distribution Patch (4 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-68161
vulnetix vdb fixes CVE-2025-68161
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-68161/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- patch
- vendor-advisory
- vendor-advisory
- related
- related
- vendor-advisory
- https://nvd.nist.gov/vuln/detail/CVE-2025-68161 advisory
- https://github.com/advisories/GHSA-vc5p-v9hr-52mj advisory
- https://github.com/apache/logging-log4j2/commit/3b93748497e1adbbd027fda8a5e7268ec5d0d578 patch
- https://github.com/apache/logging-log4j2 url
- http://www.openwall.com/lists/oss-security/2025/12/18/1 url
- https://lists.debian.org/debian-lts-announce/2026/01/msg00015.html url