Security Bulletin
Summary
There is a vulnerability in the Apache log4j library used by IBM APM Internet Service Monitoring Agent.
Vulnerability Details
CVEID: CVE-2025-68161
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#SslC… configuration attribute or the log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j… 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.
CWE: CWE-297: Improper Validation of Certificate with Host Mismatch
CVSS Source: NVD
CVSS Base score: 4.8
CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N)
Affected Products and Versions
| Affected Product(s) | Version(s) |
| IBM APM Internet Service Monitoring Agent | 08.22.01.00 - 08.23.05.00 |
Remediation/Fixes
This CVE is fixed in Log4j version 2.25.3. To resolve the issue, replace the existing Log4j 2.19.0 JARs in agent candlehome with the latest 2.25.3 JARs.
Steps to update Log4j:
1. Download and extract the official Apache Log4j 2.25.3 package:
https://downloads.apache.org/logging/log4j/2.25.3/apache-log4j-2.25.3-bin.zip
2. Back up and remove the existing Log4j JARs from the following locations:
Linux:
$ISMHOME/platform/linux2x86_64/bin/
Windows:
%ISMHOME%\platform\win64\bin\
3. Copy the new Log4j 2.25.3 JARs into the same directory.
4. Update the hardcoded classpath to reference the new JAR version:
Linux:
$ISMHOME/platform/linux2x86_64/bin/ISMXMLGeneratorLauncher.sh
Windows:
%ISMHOME%\platform\win64\bin\ISMXMLGeneratorLauncher.bat
Replace all references from 2.19.0 to 2.25.3.
5. Restart the ISM Agent and monitor the processes.
6. To apply the change, create at least one new ISM profile and deploy it.
Workarounds and Mitigations
None
Get Notified about Future Security Bulletins
References
Acknowledgement
Change History
03 Feb 2026: Initial Publication
*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.
Disclaimer
According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES ""AS IS"" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY. In addition to other efforts to address potential vulnerabilities, IBM periodically updates the record of components contained in our product offerings. As part of that effort, if IBM identifies previously unidentified packages in a product/service inventory, we address relevant vulnerabilities regardless of CVE date. Inclusion of an older CVEID does not demonstrate that the referenced product has been used by IBM since that date, nor that IBM was aware of a vulnerability as of that date. We are making clients aware of relevant vulnerabilities as we become aware of them. "Affected Products and Versions" referenced in IBM Security Bulletins are intended to be only products and versions that are supported by IBM and have not passed their end-of-support or warranty date. Thus, failure to reference unsupported or extended-support products and versions in this Security Bulletin does not constitute a determination by IBM that they are unaffected by the vulnerability. Reference to one or more unsupported versions in this Security Bulletin shall not create an obligation for IBM to provide fixes for any unsupported or extended-support products or versions.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
03 February 2026
Initial Publish date:
03 February 2026
UID
ibm17259490