--- title: "[5.2] CCM - November 10, 2026" slug: "5-2-ccm-november-10-2026" updated: 2026-11-16T15:46:09Z published: 2026-11-16T15:46:09Z canonical: "support.fortanix.com/5-2-ccm-november-10-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.2] CCM - November 10, 2026 This article provides an overview of new features and bug fixes in the Fortanix Confidential Computing Manager (CCM) 5.2 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 - Added support for deploying the Fortanix Node Agent as a container in Kubernetes using DaemonSets and Helm charts. The DaemonSet ensures that one Node Agent pod runs on each eligible Trusted Execution Environment (TEE)-enabled AMD SEV-SNP or Intel TDX node. This provides an alternative to host-level installation while retaining TEE device access, attestation, and communication with Fortanix CCM. *For more information, refer to the following articles:* - [*Enroll a Compute Node Using the Helm Chart for AMD-SEV SNP*](/v1/docs/fortanix-ccm-enroll-a-compute-node-bare-metal-amd-sev-snp#40-enroll-a-compute-node-using-the-helm-chart) - [*Enroll a Compute Node Using the Helm Chart for Intel TDX*](/v1/docs/fortanix-ccm-enroll-a-compute-node-bare-metal-intel-tdx#40-enroll-a-compute-node-using-the-helm-chart) - **Support for Confidential Container – Enclave OS and CoCo Applications:** Added support for Confidential Container- Enclave OS and Confidential Container- CoCo applications in Fortanix CCM on-premises deployments. Users can now select either **Confidential Container - CoCo** or **Confidential Container - Enclave OS** as the application type and choose **AMD SEV-SNP** or **Intel TDX** as the underlying confidential-computing platform when registering the workloads. ![](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/image(199).png?sv=2026-02-06&spr=https&st=2026-11-17T03%3A34%3A56Z&se=2026-11-17T04%3A34%3A56Z&sr=b&sp=r&sig=LE1VBp2zXOAfoPlPOnWsq7hCQhrFuUlOXFTzNATGY3g%3D) ![](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/image(197).png?sv=2026-02-06&spr=https&st=2026-11-17T03%3A34%3A56Z&se=2026-11-17T04%3A34%3A56Z&sr=b&sp=r&sig=9dhq2amSdtpo08TOvTSkU3rAPWI0IUkc2TwUNUcHBeQ%3D) *For more information, refer to the following articles:* - [*Add Confidential Container - CoCo Applications*](/v1/docs/fortanix-ccm-add-application#80-confidential-container-coco-applications) - [*Add Confidential Container – Enclave OS Applications*](/v1/docs/fortanix-ccm-add-application#40-confidential-container-enclave-os-application) - Fortanix CCM on-premises 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/image(196).png?sv=2026-02-06&spr=https&st=2026-11-17T03%3A34%3A56Z&se=2026-11-17T04%3A34%3A56Z&sr=b&sp=r&sig=jYTdGIZB1ZP9g7qWdFSNoBN4tESeGtipWYNyjZLNX7M%3D) *For more information, refer to* [*TCB Grace Period*](/v1/docs/tcb-grace-period)*.* ## 2. Bug Fixes - Fixed an issue where application certificate issuance for Azure Confidential VMs (CVMs) could fail with a `MissingJwtKey` attestation validation error. The grace period for the Microsoft Azure Attestation (MAA) endpoint, Azure CVM, and ACI is now extended to 21 months. ## 3. Enclave OS Improvements and Bug Fixes (SaaS only) - Updated the Nitro converter and its dependent base images to set the APT `Acquire::Retries` configuration to `0`, addressing CVE-2026-109518. - Updated the Linux kernel used in the 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. - Updated Web PKI root certificates and CA certificates used by the Nitro-converted applications to further secure communication with Fortanix CCM. - Fixed an issue where certificate issuance failures were not reported back to the host, resulting in a generic enclave failure error. ## 4. Installation - For the corresponding version of the Fortanix Armor Kubernetes Operator Helm Chart, click [*here*](/v1/docs/fortanix-armor-kubernetes-operator-28-1-nov-10-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). ## 5. 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.2_Release_Note.pdf](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/CCM_5.2_Release_Note.pdf)