RSA-2026-19: RSA Governance & Lifecycle Product Security Update for Log4j Vulnerabilities
Last Modified: 2026-11-09

RSA-2026-19: RSA Governance & Lifecycle Product Security Update for Log4j Vulnerabilities

 

RSA Identifier: RSA-2026-19

 

CVE Identifier: CVE-2026-34480, CVE-2025-68161

 

Severity:

  • HIGH (CVE-2026-34480)
  • Medium (CVE-2025-68161)

 

Severity Rating:

  • CVSS: 3.1 - 8.8 High /AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N (CVE-2026-34480)
  • CVSS: 3.1 – 4.8 Medium /AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N (CVE-2025-68161)

 

Affected Products:

  • RSA Governance & Lifecycle 8.0.0 P02 and later.

 

Summary

Apache Log4j Core contains multiple vulnerabilities and hardening gaps that affect specific logging configurations.

  • CVE-2026-34480: In Log4j Core versions up to and including 2.25.3, XmlLayout does not properly sanitize characters that the XML 1.0 specification forbids. If such characters occur in a log message or MDC value, Log4j can generate malformed XML. Depending on the StAX implementation, the logging event can also fail.
  • CVE-2025-68161: Log4j Core's SocketAppender does not correctly perform TLS hostname verification, even when hostname verification is enabled. This affects versions 2.0-beta9 through 2.25.2, so every version before 2.25.3, and it is fixed in version 2.25.3. Under the required network and certificate conditions, a man-in-the-middle attacker could intercept or redirect remote log traffic
  • FilteredObjectInputStream Deserialization Bypass in Apache Log4j: A bypass of the allowlist in FilteredObjectInputStream has been reported. No official CVE or vendor-issued patch has been assigned. Apache classifies allowlist bypasses in this class as hardening gaps or non-findings rather than product vulnerabilities. Apache also states that Log4j does not deserialize data as part of normal logging. Exploitation requires an application that actually deserializes Java-serialized Log4j events from an untrusted or attacker-influenced source. Achieving code execution additionally depends on suitable gadget classes being available on the JVM.

 

Impact

The reported Log4j findings affect specific logging or deserialization configurations rather than normal Log4j logging in all deployments. CVE-2025-68161 requires the Log4j SocketAppender TLS path, CVE-2026-34480 requires XmlLayout, and the FilteredObjectInputStream finding requires an application to deserialize serialized Log4j events. Based on the previously documented G&L configuration using PatternLayout with local file-only appenders rather than XmlLayout or network appenders, the first two vulnerable paths were assessed as not exposed. The deserialization finding should likewise be assessed by verifying that G&L does not deserialize Java-serialized Log4j events from untrusted sources.

G&L is currently assessed as not exploitable, overall impact on the application is LOW.

 

Resolution

The Apache Log4j Core must be upgraded to version 2.25.4 or later to remediate CVE-2026-34480 and CVE-2025-68161. Continue using the local file-based PatternLayout logging, without SocketAppender/XmlLayout, and do not deserialize untrusted Java-serialized Log4j events.

RSA is planning the following action(s):

  • Upgrade the Apache Log4j Core to version 2.25.4 or later

These changes are under review and will be delivered in a future release.

 

Severity Rating

For an explanation of Severity Ratings, refer to the Security Advisories Severity Rating knowledge base article. RSA recommends all customers consider both the base score and any relevant temporal and environmental scores which may impact the potential severity associated with a security vulnerability.

 

Legal Information

Read and use the information in this RSA Security Advisory to assist in avoiding any situation that might arise from the problems described herein. If you have any questions regarding this advisory, contact RSA Technical Support. RSA Security LLC and its affiliates, including without limitation, distribute RSA Security Advisories in order to bring to the attention of users of the affected RSA products important security information. RSA recommends that all users determine the applicability of this information to their individual situations and take appropriate action. The information set forth herein is provided "as is" without warranty of any kind. RSA disclaims all warranties, either express or implied, including the warranties of merchantability, fitness for a particular purpose, title, and non-infringement. In no event shall RSA, its affiliates, or its suppliers, be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits, or special damages, even if RSA, its affiliates, or its suppliers have been advised of the possibility of such damages. Some jurisdictions do not allow the exclusion or limitation of liability for consequential or incidental damages, so the foregoing limitation may not apply.

Security