--- title: "[5.1] CCM - October 07, 2026" slug: "5-1-ccm-october-07-2026" updated: 2026-10-27T16:10:57Z published: 2026-10-27T16:10:57Z canonical: "support.fortanix.com/5-1-ccm-october-07-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.1] CCM - October 07, 2026 This article provides an overview of new features, improvements and bug fixes, and known issues in the Fortanix Confidential Computing Manager (CCM) 5.1 release. > [!NOTE] > NOTE > > For AMD SEV-SNP and Intel TDX applications, Graphics Processing Unit (GPU) attestation verification is limited to single NVIDIA Hopper GPU instances and multiple NVIDIA Blackwell GPU instances only. ## 1. New Features - Fortanix CCM on-premises now supports Secure Model Distribution for **Confidential VM** applications on **AMD SEV-SNP** and **Intel TDX** platforms. You can now: ![](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/Screenshot (4418).png?sv=2026-02-06&spr=https&st=2026-11-17T03%3A06%3A48Z&se=2026-11-17T04%3A06%3A48Z&sr=b&sp=r&sig=67WYDFMKh%2FlO8tjZjIxTZJFWO3YHXDzt%2FHlkdqx5ySg%3D) - Create **Confidential VM** applications and application builds. - Configure **Application Configuration** for these applications. - Create and run **Workflows** for these applications. - Create **Collaboration Groups** and **Collaboration Workflows** for these applications. - Fortanix CCM SaaS now supports configuring an account-level **Security patching grace period** in **Settings → Security Policy** for Intel SGX, Intel TDX (including GPU), and AMD SEV-SNP. Set the grace period value between 0 to 365 days (default: 42 days) to define how long nodes have to apply patches after a vendor discloses a vulnerability. ![](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/Screenshot (4454).png?sv=2026-02-06&spr=https&st=2026-11-17T03%3A06%3A48Z&se=2026-11-17T04%3A06%3A48Z&sr=b&sp=r&sig=LrWToZclDW6MvPP0lcgHmafHp0L0wKThY%2FPxyVsK%2F8I%3D) *For more information, refer to* [*TCB Grace Period*](/v1/docs/tcb-grace-period)*.* ## 2. Improvements - Improved the Fortanix Nitro Converter environment variable handling by validating environment variables against an allowlist before passing them to the enclave. ## 3. Bug Fix - Fixed an issue where running Fortanix CCM workflows with the same application, but different build versions could cause certificate requests to fail due to incorrect workflow-version validation. ## 4. Known Issues - The Nitro workflow may fail to retrieve its workflow configuration and return a `401 Unauthorized` error with the message `Failed requesting workflow config response`. ## 5. Installation - For the corresponding version of the Fortanix Armor Kubernetes Operator Helm Chart, click [*here*](/v1/docs/fortanix-armor-kubernetes-operator-28-0-oct-7-2026). - Download the latest Fortanix Node Agent Software from [*here*](/v1/docs/fortanix-node-agent-software). - Download the latest Fortanix Attestation Client from [*here*](/v1/docs/fortanix-attestation-client). ## 6. Limitations Fortanix has a fair usage policy in this Early Customer Access Program. Hence, Fortanix has limited the resources one can create per account. Therefore, it is expected to observe a resource creation failure message once you have reached the maximum limit. To report an issue or bug, visit [New Requests](https://fortanix.zendesk.com/hc/en-us/requests). ## Attachments - [CCM_5.1_Release_Note.pdf](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/CCM_5.1_Release_Note.pdf)