Skip to main content
No exploitation reportedFix available

CVE-2025-68161

No exploitation reported by the sources we read.

  • Published2025-12-18
  • Fixed in2.25.3
  • WeaknessCWE-295 · CWE-297

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2025-12-1821:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-11-03 15:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2025-68161?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2025-68161?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD · OSV
Apache Log4j
BranchAffectedFixed in
2.x≥ 2.0.1, < 2.25.32.25.3
2.x≥ 2.0-beta9, < 2.25.32.25.3
2.0= 2.0no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As apache, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Apache Software Foundation Apache Log4j Coreother versions: not affected

    package org.apache.logging.log4j:log4j-corehttps://repo.maven.apache.org/maven2

    Affected
    • ≥ 2.0-beta9, < 2.25.3fixed in 2.25.3maven
    • ≥ 3.0.0-alpha1, ≤ 3.0.0-beta3no fix statedmaven

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-04-10

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • activemqCleanStartall versions · fixed in 6.2.8-r2
  • airflow-2MinimOSall versions · fixed in 2.11.2-r0and 2 other packages
  • airflow-3Wolfiall versions · fixed in 3.2.0-r0
  • airflow-3MinimOSall versions · fixed in 3.2.0-r0and 2 other packages
  • airflow-3Chainguardall versions · fixed in 3.2.0-r0
  • airflow-3-bitnami-compatWolfiall versions · no fixed version listed
  • akhqWolfiall versions · fixed in 0.27.0-r1
  • akhqMinimOSall versions · fixed in 0.28.0-r0and 1 other package

194 more package ranges on OSV.dev

Vendor advisories

  • CVE-2025-68161 Red Hat Product Security165 known affected

    Apache Log4j: Apache Log4j Core: Information disclosure via missing TLS hostname verification

    log4j-core as a component of Logging Subsystem for Red Hat OpenShift · openshift-logging/elasticsearch-operator-bundle as a component of Logging Subsystem for Red Hat OpenShift · openshift-logging/elasticsearch-proxy-rhel9 as a component of Logging Subsystem for Red Hat OpenShift · +162 more

Full record on NVD

Fix

  1. Update Apache Log4j to 2.25.3
  2. No fix available, says the vendor Red Hat Product Security CVE-2025-68161 · 165 productsFix deferred

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub
Metasploit modules
none listed
Metasploit Framework

Sources

  • CISA-ADPSSVC decisionnone2025-12-18
  • OpenCVESSVC decisionnone—
  • CNACVSS 4.06.3known since 2026-10-23
  • NVDCVSS 3.14.8read 2026-10-23
  • CNAweakness (CWE)CWE-297known since 2026-10-23
  • NVDweakness (CWE)CWE-295read 2026-10-23
  • FIRST EPSSEPSS score0.8 %2026-11-03
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryMODERATE2025-12-19

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
CVSS 4.0 vector
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Published
2025-12-18
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-vc5p-v9hr-52mj

Frequently asked questions

What is CVE-2025-68161?

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.

Is CVE-2025-68161 actively exploited?

Active exploitation of CVE-2025-68161 has not been confirmed. Its EPSS score was 0.8% on 2026-11-03, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2025-68161?

CVE-2025-68161 has a CVSS v3 base score of 4.8 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N.

Running Apache Log4j? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record