Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-vc5p-v9hr-52mj

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

CVSS 6.3 MediumEPSS 0.0077 · 56th percentile

Published by the GitHub Advisory Database at 18 Dec 2025, 21:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.apache.logging.log4j:log4j-coreMaven>=2.0-beta9, <2.25.32.25.3
Identifiers
GHSA-vc5p-v9hr-52mj · CVE-2025-68161
Weakness (CWE)
CWE-297
Tags
Published
18 Dec 2025
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not verify the TLS hostname of the peer certificate, even when verifyHostName or log4j2.sslVerifyHostName is set to true. An attacker who can intercept or redirect traffic between the client and the log receiver, and who holds a certificate from a authority trusted by the appender's trust store, can intercept or redirect log traffic. Upgrade to log4j-core 2.25.3, which fixes the issue; alternatively, configure the Socket Appender to use a private or restricted trust root.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.3 Medium 4.0 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 CNA (apache)
  • CISA KEV Not listed.
  • EPSS 0.0077, the 56th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:17 UTC First seen by agentprime
  2. 31 Oct 2026, 14:17 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.