Summary
RSA Authentication Manager includes Oracle Java SE, which uses a default trust store (cacerts). Oracle has issued Security Alert CVE-2026-114820, which removes trust in the following root certificate authorities from that trust store:
- emsignrootcag1
- emsignrootcag2
- emsigneccrootcag3
- Comodoaaaca
The bundled cacerts files in the affected versions of Authentication Manager still contain these root CAs.
The following RSA Authentication Manager packages contain the updated Oracle Java SE builds that resolve this issue:
- RSA Authentication Manager 8.9 Patch 6 or later patches
- RSA Authentication Manager 8.9 web-tier server Patch 6 or later web-tier patches
Affected Products
- RSA Authentication Manager 8.9 Patch 5 and earlier versions
- Earlier versions of RSA Authentication Manager, including 8.8 and 8.7 SP2
Impact
RSA Authentication Manager's own trust stores do not contain the affected root CAs. Core Authentication Manager services use the Authentication Manager trust store, not the Java default trust store. These services include the Security Console, Operations Console, Self-Service Console, authentication, and RADIUS.
The affected root CAs exist only in the Oracle Java SE default cacerts file bundled with the appliance and the Web Tier. Customers are affected only if their deployment relies on certificates issued by eMudhra (emSign), or on legacy Sectigo chains anchored to the Comodo AAA root.
Certificates issued by other certificate authorities, such as DigiCert, are not affected.
Severity Rating for CVE-2026-114820
Critical, CVSS 3.1 base score 9.1
For an explanation of Severity Ratings, refer to the RSA Vulnerability Disclosure Policy. RSA recommends all customers take into account both the base score and any relevant temporal and environmental scores which may impact the potential severity associated with a particular security vulnerability.
Action Required
Recommended: Upgrade to AM 8.9 Patch 6
RSA recommends all customers upgrade at the earliest opportunity to RSA Authentication Manager 8.9 Patch 6.
Patch 6 includes updated Oracle Java SE builds that no longer include the affected root CAs.
Patch 6 and the updated Web Tier are available for download through the following links:
- RSA Authentication Manager 8.9 Patch 6 Download
- RSA Authentication Manager 8.9 Web-Tier Server Patch 6 Download
For patch details and installation instructions, see RSA Authentication Manager 8.9 Patches and Hotfixes Readme.
RSA only provides patches, including Oracle Java SE updates, for the latest released version of Authentication Manager. Customers who cannot upgrade to 8.9 Patch 6 can apply a temporary mitigation to remove the affected root CAs from the bundled Java trust stores manually as detailed below.
Apply a Temporary Mitigation
Before You Begin
- Make sure your deployment does not rely on certificates issued by eMudhra (emSign) or chained to the Comodo AAA root.
- Take a VM snapshot or backup of each instance.
- Perform these steps on the primary instance and on every replica instance.
Perform the following steps on the Authentication Manager appliance:
- Log on to the appliance as rsaadmin using SSH or the console, then switch to root using the following command:
sudo su - - Back up the Java trust store and remove the affected aliases using the following command:
cd /opt/rsa/am/appserver/jdk/jre/lib/security
cp -p cacerts cacerts.bak
for a in emsignrootcag1 emsignrootcag2 emsigneccrootcag3 comodoaaaca; do
/opt/rsa/am/appserver/jdk/bin/keytool -delete -alias $a -keystore cacerts -storepass changeit
done - If the file /opt/rsa/am/utils/standalone_java/lib/security/cacerts exists, repeat the backup and removal for it:
cd /opt/rsa/am/utils/standalone_java/lib/security
cp -p cacerts cacerts.bak for a in emsignrootcag1 emsignrootcag2 emsigneccrootcag3 comodoaaaca; do
/opt/rsa/am/utils/standalone_java/bin/keytool -delete -alias $a -keystore cacerts -storepass changeit
done
A message that an alias "does not exist" means it is already absent. You can ignore it. - Restart Authentication Manager services using the following command:
/opt/rsa/am/server/rsaserv restart all
Perform the following steps on the Web-Tier server:
- Repeat the backup and alias removal for the Java trust store under the web-tier installation directory.
- Restart the web-tier services.
The trust store is at the following path:
<webtier_install_dir>/appserver/jdk/jre/lib/security/cacerts
If that path is not present, use the following path:
<webtier_install_dir>/appserver/jdk/lib/security/cacerts
On Windows, run keytool.exe from <webtier_install_dir>\appserver\jdk\bin in an Administrator command prompt.
Verification
For each trust store, run the following command:
<jdk>/bin/keytool -list -keystore <path>/cacerts -storepass changeit -alias emsignrootcag1
The result should report that the alias does not exist. Repeat the check for the other three aliases.
Rollback
To roll back, restore cacerts.bak over cacerts in each location, then restart services.
Note: Applying a later Authentication Manager patch may replace the bundled Java runtime. RSA Authentication Manager 8.9 Patch 6 and later patches include the updated trust store; therefore, no manual steps are required after you upgrade.
EOPS Policy
RSA has a defined End of Primary Support policy associated with all major versions. Please refer to the Product Version Life Cycle for additional details.
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.
Related Articles
RSA Identity Governance and Lifecycle 7.0.1 P02 Review and Rules processing failing 18Number of Views How to set cookie expiration times 25Number of Views RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities 38Number of Views How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. 903Number of Views RSA-2026-21: Critical Security Update for RSA Authentication Manager 32Number of Views