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

RSA-2026-20: RSA Governance & Lifecycle Product Security Update for ActiveMQ Vulnerabilities

 

RSA Identifier: RSA-2026-20

 

CVE Identifier: CVE-2026-42588, CVE-2026-45505, CVE-2026-49157, CVE-2026-42253, CVE-2026-46605

 

Severity:

  • HIGH (CVE-2026-49157, CVE-2026-45505, CVE-2026-42588)
  • Medium (CVE-2026-46605, CVE-2026-42253)

 

Severity Rating:

  • CVSS: 3.1 - 8.8 High /AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (CVE-2026-49157)
  • CVSS: 3.1 - 8.8 High /AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (CVE-2026-45505)
  • CVSS: 3.1 - 8.1 High /AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N (CVE-2026-42588)
  • CVSS: 3.1 - 6.1 Medium /AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N (CVE-2026-42253)
  • CVSS: 3.1 - 4.3 Medium /AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L (CVE-2026-46605)

 

Affected Products:

  • RSA Governance & Lifecycle 8.0.0 P02 and later, using AFX Server (Access Fulfillment Express)

 

Summary

These CVEs are associated with management interface and broker exposure risks and may allow unauthorized access or remote exploitation in environments where the broker or its management endpoints are reachable. However, in this deployment, the broker is not remotely exposed, the web console has been disabled, and the Jolokia endpoint is not enabled. Access is limited to the local system and the AFX-only path, which substantially reduces the exposure and exploitation of risk.

 

This issue affects:

  • ActiveMQ versions prior to 5.19.4
  • ActiveMQ versions from 6.0.0 up to (but not including) 6.2.3

 

Mitigations implemented as part of RSA G&L 8.0.0 P11 HF01 patch:

  • Disabled the ActiveMQ web console
  • Disabled /api/jolokia
  • Confirmed no remote broker access is exposed

 

Details

  • For CVE-2026-49157, CVE-2026-45505 and CVE-2026-42588: These vulnerabilities are associated with ActiveMQ broker management and endpoint exposure. In the most common exploitation scenarios, an authenticated attacker who can reach the broker management surface may be able to abuse a vulnerable administrative or discovery path to trigger the loading of external resources or application context data, potentially leading to code execution or unauthorized broker manipulation. The risk increases when management endpoints are exposed to untrusted networks or when broker administrative interfaces remain enabled. Given the existing controls in the RSA G&L environment, including the disablement of the ActiveMQ web console and the /api/jolokia endpoint, the lack of remote broker access, and the fact that access is limited to the local system and AFX-only connectivity, the effective exposure surface is significantly reduced. As a result, the risk in RSA G&L environment is considered low.
  • For CVE-2026-46605 and CVE-2026-42253: These issues relate to broker management or configuration exposure, where an attacker with access to an exposed ActiveMQ administrative path could potentially trigger unsafe processing or remote resource loading behavior, depending on the specific endpoint and configuration in use. In a typical deployment, exploitation requires reachability to the management interface and, in some cases, authenticated access.

In the RSA G&L environment, these interfaces are not remotely accessible, the ActiveMQ console has been disabled, and the Jolokia endpoint is not enabled. Broker access is restricted to the local system and AFX-only connectivity, which limits the attack surface substantially. Based on these controls, the overall impact is considered low in RSA G&L deployment.

 

Impact

In the RSA G&L 8.0.0 P11 HF01 and later environment, the ActiveMQ web console and the /api/jolokia endpoint are disabled or otherwise not accessible externally, and the broker is restricted to local-only access with AFX-only connectivity. This configuration limits access to the local system and prevents remote exploitation over the network. As a result, exploitation would require local system access in addition to any existing authentication and authorization controls, significantly reducing the exposure surface.

The referenced ActiveMQ vulnerabilities therefore present a limited risk in this environment because the management interfaces are not remotely reachable and the broker is not exposed to external networks.

Overall impact in the application is LOW.

 

Resolution

A full remediation for the above vulnerabilities requires upgrading Apache ActiveMQ to a higher version (5.19.4 or later). This needs JDK version to be 11 or higher.

RSA is planning the following actions:

  • Upgrade the Java runtime environment for AFX to version 17+.
  • Post migration, adopt ActiveMQ 5.19.4 or later including fixes for the above CVE's.

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

Until full remediation is available, follow the steps below:

  • Apply RSA G&L 8.0.0 P11 HF01 or later patch where web console for Apache ActiveMQ has been disabled and access is limited to the local system.
  • Restrict server access to authorized personnel only.
  • Ensure that system hardening and access control policies are in place.
  • Carry out periodic review of configuration and access controls.

 

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