CloudLinux released 10.3 and 9.9 as stable on 16 November 2026, the same day AlmaLinux shipped 10.3 "Mauve Lion" and 9.9 "Chartreuse Bobcat". Both are minor releases, free for anyone with an active CloudLinux license, and both arrive through a normal dnf update.
Most cPanel and Plesk servers will take them without drama. The changes worth reading first are the new kernels, the fapolicyd and authselect behaviour changes, and Podman 6 if you run containers.
Versions at a glance
| CloudLinux 10.3 | CloudLinux 9.9 | |
|---|---|---|
| Base | AlmaLinux 10.3 | AlmaLinux 9.9 |
| Kernel | 6.12.0-264.16.1.el10_3 | 5.14.0-741.22.1.el9_9 |
| LVE module | kmod-lve-2.1-82.el10 | kmod-lve-2.1-82.1.el9 |
| Install media | No ISO, convert AlmaLinux with cldeploy | ISO, or convert with cldeploy |
| Support until | May 2035 | May 2032 |
Both kernels are the upstream AlmaLinux builds without a CloudLinux rebuild, with the LVE module rebuilt for the new kernel ABI and Secure Boot support. AlmaLinux says it restored CVE fixes that RHEL dropped between point releases: 36 in the 10.3 kernel and 44 in the 9.9 kernel. Both releases are x86_64 only.
Upgrade a server
On CloudLinux 10.2:
dnf clean all && dnf update
On CloudLinux 9.8, cloudlinux-release 9.9 rolls out in batches over about two weeks, and dnf update picks it up when your batch arrives. To move now, CloudLinux gives:
dnf --enablerepo=cloudlinux-rollout-8-bypass install cloudlinux-release
dnf update
Reboot into the new kernel, then confirm:
uname -r
rpm -q cloudlinux-release kmod-lve
/etc/os-release still reports AlmaLinux on 10.x. That is expected. CloudLinux recommends testing on a non-production server first, and on a fleet that advice is worth following for the two changes below.
What else is new
- ModSecurity returns on 10. 10.3 ships ModSecurity 2.9.14 with OWASP CRS 4.22.0, absent since 10.0. CRS 4 reorganises the rules, so exclusions written for CRS 3.3 need reviewing. cPanel servers run ModSecurity from EasyApache 4 instead, so this matters most on panel-less boxes. Our ModSecurity rule set comparison covers the CRS trade-offs.
- Podman 6 on 10. Vendor defaults move to
/usr/share/containers, while/etc/containersstill wins. Upstream removes CNI, slirp4netns (replaced by pasta), cgroups v1, and iptables-based rules, so test any containerised workloads. - Toolchains. GCC Toolset 16, LLVM 22, Rust 1.97, and a Node.js 26 stream on both. GCC 16 defaults to C++20, so customers compiling older code may need
-std=gnu++17. - Security packages. OpenSSL 3.5.9 and SELinux policy 42.1.27 on 10.3, crypto-policies updates on both.
Should you move to 10 yet
If you are on 9, 9.9 is a routine update. Moving from 9 to 10 is still a fresh install plus account transfer, covered in migrating CloudLinux 8 or 9 to CloudLinux OS 10. For a new server, install CloudLinux on cPanel from AlmaLinux 10.3 with cldeploy.
Does upgrading to CloudLinux 10.3 cost extra?+
Is there a CloudLinux 10.3 ISO?+
Why does /etc/os-release say AlmaLinux after installing CloudLinux 10?+
Do I need to reboot after updating to CloudLinux 9.9 or 10.3?+
Next steps
- Compare editions and per-server cost in CloudLinux license tiers explained.
- Confirm the new TuxCare ELS repositories for alt-* packages are enabled while you're updating.
- Watch for new resource faults after the reboot by reading LVE Manager statistics.