log4j-core-2.25.1.jar: 1 vulnerabilities (highest severity is: 4.0)

[mend-bolt-for-github]

Vulnerable Library - log4j-core-2.25.1.jar

A versatile, industrial-grade, and reference implementation of the Log4j API. It bundles a rich set of components to assist various use cases: Appenders targeting files, network sockets, databases, SMTP servers; Layouts that can render CSV, HTML, JSON, Syslog, etc. formatted outputs; Filters that can be configured using log event rates, regular expressions, scripts, time, etc. It contains several extension points to introduce custom components, if needed.

Library home page: https://logging.apache.org/log4j/2.x/

Path to dependency file: /artemis-java-template/pom.xml

Path to vulnerable library: /artemis-java-template/pom.xml

Vulnerabilities

Vulnerability	Severity	CVSS	Dependency	Type	Fixed in (log4j-core version)	Remediation Possible**
CVE-2025-68161	Medium	4.0	log4j-core-2.25.1.jar	Direct	2.25.3	❌

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2025-68161

Vulnerable Library - log4j-core-2.25.1.jar

A versatile, industrial-grade, and reference implementation of the Log4j API. It bundles a rich set of components to assist various use cases: Appenders targeting files, network sockets, databases, SMTP servers; Layouts that can render CSV, HTML, JSON, Syslog, etc. formatted outputs; Filters that can be configured using log event rates, regular expressions, scripts, time, etc. It contains several extension points to introduce custom components, if needed.

Library home page: https://logging.apache.org/log4j/2.x/

Path to dependency file: /artemis-java-template/pom.xml

Path to vulnerable library: /artemis-java-template/pom.xml

Dependency Hierarchy:

• ❌ log4j-core-2.25.1.jar (Vulnerable Library)

Found in base branch: main

Vulnerability Details

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.

Publish Date: 2025-12-18

URL: CVE-2025-68161

CVSS 3 Score Details (4.0)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: High
  • Privileges Required: None
  • User Interaction: None
  • Scope: Changed
• Impact Metrics:
  • Confidentiality Impact: Low
  • Integrity Impact: None
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2025-12-17

Fix Resolution: 2.25.3

Step up your Open Source Security Game with Mend here