CVE-2025-68161: Apache Log4j does not verify the TLS hostname in its Socket Appender

CVE-2025-68161 · Severity: medium · CVSS 4 · Published 2025-12-18

Apache Log4j does not verify the TLS hostname in its Socket Appender

Technologies: org.apache.logging.log4j:log4j-core (Maven). Vendors: Maven.

Quick answers

Is CVE-2025-68161 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-68161 being exploited in the wild.
How severe is CVE-2025-68161?
Medium severity, with a CVSS score of 4, published 18 December 2025.
Which products and versions are affected?
org.apache.logging.log4j:log4j-core (Maven) ECOSYSTEM:introduced=2.0-beta9,fixed=2.25.3.
Is there a fix for CVE-2025-68161?
Yes. org.apache.logging.log4j:log4j-core (Maven): upgrade to 2.25.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-68161?
Check whether you run org.apache.logging.log4j:log4j-core (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.apache.logging.log4j:log4j-core (Maven): upgrade to 2.25.3 or later
    # set org.apache.logging.log4j:log4j-core to 2.25.3 in your pom.xml or build.gradle

Affected products

  • org.apache.logging.log4j:log4j-core (Maven) ECOSYSTEM:introduced=2.0-beta9,fixed=2.25.3

Identifiers

  • CVE-2025-68161
  • GHSA-vc5p-v9hr-52mj

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.