--- title: "[5.11] DSM Clients - November 16, 2026" slug: "5-11-dsm-clients-november-16-2026" updated: 2026-11-19T11:28:00Z published: 2026-11-19T11:28:00Z canonical: "support.fortanix.com/5-11-dsm-clients-november-16-2026" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.fortanix.com/llms.txt > Use this file to discover all available pages before exploring further. # [5.11] DSM Clients - November 16, 2026 ## 1. Overview This article provides an overview of the new features, improvements, and bug fixes in the Fortanix Data Security Manager (DSM) Clients 5.11 release. ## 2. Client New Features, Improvements, and Bug Fixes - Upgraded KMIP to version 3.0 to support ML-DSA key pair generation, signing, and verification (JIRA: PM-741). - Updated `CKA_PARAMETER_SET` error handling in PKCS#11 to maintain compatibility with OpenSSL during EC key generation **(JIRA: PROD-11791)**. - Fixed HMG Client binary permissions to ensure it has the required executable permission **(JIRA: PROD-11757)**. - Added support for retrieving certificate objects in **X.509** or **Raw** formats through the KMIP **GET** operation **(JIRA: PM-777)**. - Added Ed448 EC Edwards curve support in PKCS#11 for key pair generation, signature generation, and signature verification **(JIRA: PM-759)**. - Added support for the KMIP Extractable attribute to control key extraction permissions **(JIRA: PM-737)**. - Added support for **ML-DSA** key pair generation, signing, signature verification, and key factory operations in the Fortanix JCE provider **(JIRA: PM-633** and **PM-775)**. *For more information, refer to* [*Java Cryptography Extension (JCE) Provider*](/v1/docs/fortanix-dsm-clients-java-cryptography-extension-jce-provider#1318-generate-dsa-keys)*.* - Fixed an issue where sdkms-cli authentication using the `--username` argument failed in DSM 5.10 when using username and password authentication **(JIRA: ES-676)**. ## 3. DSM Accelerator New Features, Improvements, and Bug Fixes DSM Accelerator Webservice version - **1.37.2991** - **DSM Accelerator Webservice:** - Added ML-DSA support in DSM Accelerator Webservice to enable quantum-safe application integration for signature generation and signature verification that aligns with DSM post-quantum cryptography support for exportable keys **(JIRA: PM-705)**. *For more information, refer to the* [*DSM Accelerator Webservice Developer Guide*](/v1/docs/dsm-accelerator-webservice-developer-guide#822-signing-and-verification-using-mldsa-keys)*.* ## 4. Security Fixes - Updated the CA certificates package and the certificates bundled in the SGX binary in DSM client and DSM Accelerator to address the eMudhra intermediate CA certificate compromise **(JIRA: SI-129)**. *For more information, refer to the* [*eMudhra Intermediate CA Compromise advisory*](https://emudhra.we-have-a-problem.com/)*.* - Updated the Linux kernel used in DSM Accelerator Nitro enclaves to 6.6.161 to address [CVE-2026-98432](https://nvd.nist.gov/vuln/detail/cve-2026-98432), a use-after-free vulnerability in the IPv4 TCP networking subsystem that could potentially lead to denial of service (DoS) or remote code execution **(SI-131)**. - Updated the DSM Accelerator base images to set the APT `Acquire::Retries` configuration to `0`, addressing CVE-2026-109518 **(SI-133)**. ## 5. Fortanix Data Security Manager Accelerator Performance Statistics ### 5.1 Runtime Environment > [!NOTE] > NOTE > > The following table lists the standard recommended runtime environment. You can choose a higher configuration for better performance. > > DSM Accelerator was run in the runtime environment listed below for performance testing. | **Item** | **Specification** | | --- | --- | | Number of Cores | 4 | | CPU | Intel(R) Xeon(R) CPU E5-2673 v4 @ 2.30GHz | | RAM | 2 GiB | | VM Type | Standard D4ds v4 Azure VM | | Docker Runtime Configuration | `sudo docker run -d --network host --memory=1g --memory-swap=2g --log-driver json-file --log-opt max-size=100m` | --- ### 5.2 DSM Accelerator Webservice > [!NOTE] > NOTE > > The performance numbers below are captured with a single node; if you need higher performance or throughput, then Fortanix recommends adding multiple nodes. | **Key Types and Operations** | **Throughput (Operations/second on a 1-node cluster re-using a single TLS session)** | | --- | --- | | AES 256: CBC Encryption/Decryption | 19,801/19,625 | | AES 256: GCM Encryption/Decryption | 20,099/19,855 | | AES 256: FPE Encryption/Decryption | 9,271/9,241 | --- ### 5.3 Additional Modes | **Key Types and Operations** | **Throughput (Operations/second on a 1-node cluster re-using a single TLS session)** | | --- | --- | | AES 256: CBCNOPAD Encryption/Decryption | 20,051/19,782 | | AES 256: CFB Encryption/Decryption | 20,183/19,717 | | AES 256: CTR Encryption/Decryption | 20,094/19,829 | | AES 256: OFB Encryption/Decryption | 20,197/19,919 | | AES 256: CCM Encryption/Decryption | 20,025/19,714 |