About This Patch

Entrust CSP Vault version 10.6.1-P1 contains critical bug fixes mainly for an external security issue documented as eMudhra Intermediate CA Key Compromise. Entrust has already sent out a security bulletin for this.

Fixed Issues

  • This patch removes the affected eMudhra and Sectigo (AAA Certificate Services) root certificates, and the intermediates issued under them, from every certificate trust store on the appliance, including the operating systems.
    After the patch is applied, the appliance no longer trusts certificates issued under those roots.
  • Fixes an appliance two-factor authentication validation issue that allows invalid OTP values to enable HOTP or TOTP without successful verification.
  • Fixed an issue that prevented retrieval of keys across regions for AZURE_LOCAL keysets.
  • Fixed AES-CBC decryption failures for OCI HYOK keys when using an HSM with keyset caching disabled.
  • Enables importing of AWS native keys with multiple on-demand rotations into CSP Vault for CloudKeys for inventory, without allowing upload, deletion, or rotation operations.
  • Added a workaround for CVE-2026-98432 by blocking incoming IPv4 TCP packets containing IP options.

Installation Requirements

This patch can be applied to Entrust CSP Vault version 10.6.1.

Installation Procedure

  1. Sign on to the CSP Vault Management webGUI with Security Admin privileges.
  2. In the top right, click the Appliance Management link.
  3. In the top menu bar, click Cluster and make sure the Status of the cluster is Healthy. If it is not, you must resolve those issues before you can upgrade the cluster.
  4. In the top menu bar, click Settings.
  5. In the System Settings section, click System Upgrade.
  6. Click Browse, navigate to the Entrust ISO upgrade file, and click Open.
    Important: CSP Vault now has separate ISO files for installation and upgrade. Please ensure that you use the ISO upgrade file.
  7. Click Upload File. If the Upload File button is not active, make sure that you have selected an ISO file and that the cluster is healthy.
    After CSP Vault uploads and validates the ISO file, CSP Vault begins the automatic upgrade process by copying the ISO file from the current node to all of the other CSP Vault nodes in the cluster. After the ISO file has been copied, CSP Vault displays a Success message. Click Close to continue with the upgrade.
    CSP displays a status message stating that the upgrade is in process along with a Cancel Upgrade button in case you want to stop the process.
    During this time you can continue to use CSP Vault as normal, including changing all configuration options and adding or removing VMs. When CSP Vault is ready to upgrade all nodes in the cluster, it displays the Finish Upgrade button.
  8. Click Finish Upgrade.
    Note: Ensure you are still on the same node where you clicked Upgrade File.
    CSP Vault  displays a message stating that the cluster will be put into maintenance mode during this procedure and that all nodes will be rebooted. While in maintenance mode, CSP Vault can still service key requests from the registered VMs, but no CSP Vault configuration changes can be made and no new VMs can be added.
  9. Click Proceed.
    CSP Vault displays a status message stating that the cluster nodes are being rebooted. It may take a while for this process to run on all nodes except for the current node. When all of the other nodes have been upgraded and are back online, CSP Vault reboots the current node to finish the upgrade process on that node. At this point, you will be automatically logged out of the CSP Vault Management webGUI on that node. You can monitor the progress on the CSP Vault Management webGUI of the other nodes. This may take a while to complete.
    When any node is being upgraded, if you have access to the CSP Vault  System Console, you can view the upgrade messages.
    Note: When CSP Vault reboots the current node, you may see a message that the application cannot connect to the server, then browser page may display a "connection refused" message. Wait a few moments for the node to finish rebooting, then refresh your browser page. You should see the CSP Vault Login page.
  10. To verify the upgrade, return to Settings > System Upgrade and verify the settings for Current Version and Previous Version.


Post Upgrade Verification Steps

A. Check custom certificates you uploaded to the appliance

Most customers will not need to do anything in this section. It applies only if you have uploaded a CA certificate/chain that comes from eMudhra, or from Sectigo (formerly Comodo) through AAA Certificate Services. The patch does not change the certificates you uploaded yourself, so check them as described below.


B. Custom CA certificates you uploaded

  1. List where you have uploaded the CA certificates. Typical places are Active Directory / LDAP, the OpenID Connect identity provider, KMIP, Syslog, SMTP, HTTPS proxy, ESXi Secrets in Secrets Vault.
  2. Open each certificate, either where it is shown or from your own copy and follow its chain up to the top-level root.
  3. A certificate is affected if any certificate in its chain shows AAA Certificate Services, eMudhra or emSign as its subject or issuer.
  4. For each affected certificate, ask your certificate provider, or the owner of that service (your LDAP server, identity provider, mail server and so on), for a certificate chain under a different root. Upload it to the same place.
  5. Check that each connection still works, for example with a test login, a test email or syslog message, or a KMIP client connection.


C. Web server custom CA certificates (ports 443 and 8443)

These cannot be checked by viewing them on the appliance. Use the commands below. Check them even if you think your certificate provider is not affected: Sectigo certificates often chain to AAA Certificate Services.

  1. From any Linux or macOS machine with OpenSSL that can reach the appliance, run both commands for each node, replacing <node-fqdn> with the node's host name:
    openssl s_client -connect <node-fqdn>:443 -servername <node-fqdn> </dev/null 2>/dev/null | grep -i -E 'AAA Certificate Services|emSign|eMudhra'
     
    openssl s_client -connect <node-fqdn>:8443 -servername <node-fqdn> </dev/null 2>/dev/null | grep -i -E 'AAA Certificate Services|emSign|eMudhra'
  2. If neither command prints anything on any node, the web server certificates are not affected, and no action is needed.
  3. If either command prints a line:
    1. Get your server certificate, its private key, and a new chain that does not include those certificates.
    2. Go to Clusters > Actions > Use Self-Signed Certificate.
    3. Install your custom certificate again with the new chain.
    4. Run the commands in Step 1 again. They should not print anything.