🛡️ CVE-2025-68161 on Debian — apache-log4j2
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.
Distribution advisory
This page covers CVE-2025-68161 as tracked by Debian, for the package apache-log4j2. No fixed version has been recorded for this distribution yet.
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is high, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality low, integrity low, availability none.
Weakness class
DEBIAN-CVE-2025-68161 is classified as CWE-297: Improper Validation of Certificate with Host Mismatch. 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.
Affected software
DEBIAN-CVE-2025-68161 is recorded against 1 package.
- apache-log4j2
Timeline and source
Published on 18 December 2025 and last revised on 4 August 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
CVE-2025-68161 on other distributions
Each distribution ships its own build and its own fixed version. Pick the one you run:
Details
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| apache-log4j2 | — | — |
References
Similar Threats
- Unknown DEBIAN-CVE-2026-49844
- Unknown DEBIAN-CVE-2026-34479
- Unknown DEBIAN-CVE-2026-34480
- Unknown DEBIAN-CVE-2026-34481
- Unknown DLA-4444-1
Vulnerability Monitoring
Track new vulnerabilities in apache-log4j2
DEBIAN-CVE-2025-68161 is rated CVSS 4.8 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.
Set Up Free Alerts →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.