Skip to main content
CVE-2025-68161VulnerabilityPublished Updated

Microsoft · Apache Log4j Core: Missing TLS hostname verification in Socket appender

Affects MicrosoftSource GCVE Database

0
Compare
Authoritative record:CVE-2025-68161· Medium 6.3

Not known to be exploited · CVSS 6.3 Medium : upgrade to 2.25.3 when convenient.

Data as of 17 Nov 2026, 10:20 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 16 Nov 2026.

What to do

Upgrade org.apache.logging.log4j/log4j-core to 2.25.3.

Affected software

ProductAffectedFixed in
Mavenorg.apache.logging.log4j/log4j-corepkg:maven/org.apache.logging.log4j/log4j-coreOther threatsAffected
  • =3.0.0-alpha1
  • <2.25.3
Fixed in
  • 2.25.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

To determine the support lifecycle for your software, see the Microsoft Support Lifecycle: https://support.microsoft.com/lifecycle

References

Community reviews

Loading reviews…