[5.4] Patch 3 - February 27, 2026

Fortanix Data Security Manager (DSM) 5.4.2914.3426 release provides an overview of resolved issues. 

This release is superseded by the April 20, 2026, release.

WARNING

• If you want to upgrade Fortanix DSM to version 5.4.2914.3426, your current DSM version must be at least 5.0 patch 5*, 5.2 patch 2*, or 5.4 patch 2*.

• Downgrade from 5.4.2914.3426 to any prior version is not supported due to Kernel upgrades.

*The minimum required version is specific to your current major.minor version. You must first upgrade to the required patch level within your current version before proceeding to version 5.4.2914.3426.

NOTE

• The Fortanix DSM cluster upgrade must be done with Fortanix Support on call. Please reach out to Fortanix support if you are planning an upgrade.

• The customer's BIOS version must be checked by Fortanix Support before the Fortanix DSM software upgrade. If required, the BIOS version should be upgraded to the latest version and verified by Fortanix Support for a smooth upgrade.

• If your Fortanix DSM version is 5.2 or later, then the HSM Gateway version must also be 5.2 or later. Similarly, if the HSM Gateway version is 5.2 or later, then your Fortanix DSM version must be 5.2 or later.

1. Bug Fixes

• Fixed an issue where Fortanix DSM system administrators were unable to access and delete disabled DSM accounts using the System Administration → Accounts page (JIRA: ES-595).

• Fixed an issue where certificate repair (certutil -repairstore) failed for private keys imported into a Fortanix DSM FIPS-backed group because the CNG provider could not locate and bind the certificate to the corresponding private key (JIRA: ES-596).

• Fixed an issue where the System Administration → Users view continuously refreshed, preventing administrators from selecting or managing users in System Administration mode (JIRA: ES-600).

2. Known Issues

• When using an external load balancer configured with HTTP-based health checks on port 4445 (for example, GET /sys/v1/health or /health), the endpoint returns an HTTP 404 (Not Found) response starting from DSM version 5.2.

• On VMware nodes, /etc/resolv.conf may be cleared after a reboot, resulting in missing nameserver entries. Although the /etc/network/interfaces configuration is correct, any manual updates to /etc/resolv.conf are overwritten after a reboot or when the CoreDNS pod restarts (JIRA: RODE-373).

  Workaround:

  Perform the following steps:

  1. Run sudo apt purge netplan.io.

  2. If the file is removed or CoreDNS continues to have issues, manually update the nameserver entries in /etc/resolv.conf.

  3. Restart networking: sudo systemctl restart networking.

  4. Delete the CoreDNS pods to allow them to restart.

For a complete list of new features, enhancements to existing features, other improvements, bug fixes, and known issues, refer to the full description of the DSM 5.4 release notes.