CloudLinux changes package signature key: deadline 1 December 2026

CloudLinux has announced via its official blog that from 1 December 2026, all new packages for CloudLinux 7, 8 and 9 will be signed exclusively with the new GPG key. For those managing these servers, the deadline is actionable: if you fail to update the cloudlinux-release package in time, you will stop receiving updates after that date.\n\n## Who needs to take action\n\nAccording to CloudLinux, intervention is only required on servers running an obsolete version of cloudlinux-release. The new key is distributed within that package, so a server that has already received updates normally already has it.\n\nTo check the installed version:\n\n\nrpm -q cloudlinux-release\n\n\nThe new key is available from these versions onwards, according to official documentation:\n\n| CloudLinux | Minimum version with the new key |\n|---|---|\n| CloudLinux 9 | cloudlinux-release-9.6-2 |\n| CloudLinux 8 | cloudlinux-release-8.10-8 |\n| CloudLinux 7 | cloudlinux-release-7.9-2.12 |\n\nIf the installed version is lower than the one listed for your release, it must be updated before 1 December 2026.\n\n## How to update and verify\n\nCloudLinux recommends these steps:\n\n\nyum update cloudlinux-release\n\n\nTo confirm that the new key is installed:\n\n\nrpm -q gpg-pubkey --qf '%{SUMMARY}\\n' | grep 'CloudLinux Extension Signer'\n\n\nIf the command returns a line, the key is present and the server is ready. If it returns nothing, the key is not yet installed.\n\n## What happens after the deadline\n\nA server without the new key will fail signature verification on CloudLinux packages and stop receiving updates. Updating the cloudlinux-release package resolves the issue even after the deadline, returning the server to regular update delivery.\n\nFor questions or issues, CloudLinux directs you to their support team, as indicated in the official blog post.