Apache Log4j up to 2.25.2 Socket Appender certificate host validation

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Apache Log4j up to 2.25.2. Affected by this issue is some unknown functionality of the component Socket Appender. Performing a manipulation results in certificate host validation. This vulnerability is reported as CVE-2025-68161. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.
Details
A vulnerability classified as problematic has been found in Apache Log4j up to 2.25.2. This affects some unknown functionality of the component Socket Appender. The manipulation with an unknown input leads to a certificate host validation vulnerability. CWE is classifying the issue as CWE-297. The product communicates with a host that provides a certificate, but the product does not properly ensure that the certificate is actually associated with that host. This is going to have an impact on integrity. The summary by CVE is:
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.
The weakness was disclosed by Samuli Leinonen. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2025-68161 since 12/16/2025. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 03/19/2026). MITRE ATT&CK project uses the attack technique T1587.003 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 279430 (Linux Distros Unpatched Vulnerability : CVE-2025-68161), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 2.25.3 eliminates this vulnerability.
The vulnerability is also documented in the databases at Tenable (279430), EUVD (EUVD-2025-204312) and CERT Bund (WID-SEC-2025-2897). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Debian Linux
- SUSE Linux
- SUSE openSUSE
- IBM Sterling Connect:Direct
- Apache log4j
- IBM App Connect Enterprise
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.apache.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.2VulDB Meta Temp Score: 4.2
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 4.8
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Certificate host validationCWE: CWE-297 / CWE-295 / CWE-287
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 279430
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2025-68161
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Log4j 2.25.3
Timeline
12/16/2025 CVE reserved12/18/2025 Advisory disclosed
12/18/2025 VulDB entry created
03/19/2026 VulDB entry last update
Sources
Vendor: apache.orgAdvisory: github.com
Researcher: Samuli Leinonen
Status: Confirmed
CVE: CVE-2025-68161 (🔒)
GCVE (CVE): GCVE-0-2025-68161
GCVE (VulDB): GCVE-100-337437
EUVD: 🔒
CERT Bund: WID-SEC-2025-2897 - Apache log4j: Schwachstelle ermöglicht Offenlegung von Informationen
Entry
Created: 12/18/2025 22:12Updated: 03/19/2026 22:49
Changes: 12/18/2025 22:12 (68), 12/20/2025 01:08 (7), 12/20/2025 03:46 (1), 12/21/2025 01:06 (2), 01/12/2026 09:56 (1), 01/12/2026 19:19 (11), 01/24/2026 09:06 (1), 03/19/2026 22:49 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.