Updated: 16 November 2026 · Applies to: CloudLinux OS 8 and 9 (dnf 4), with or without cPanel; commands checked on AlmaLinux 9.8
The CloudLinux Network (CLN) portal shows security errata for a server when some installed packages are older than the fixed versions in the repositories. To clear them, install the pending security updates with dnf upgrade --security. On a cPanel server, part of the list is expected: cPanel excludes some operating system packages from dnf and supplies its own builds of them, so those entries go away through cPanel updates, not through dnf.
1. See which security updates are pending
Run this on the server as root to get the same picture CLN has:
dnf updateinfo summary
dnf updateinfo list --security
Output on a test system (lab example, AlmaLinux 9.8, shortened):
Updates Information Summary: available
11 Security notice(s)
1 Critical Security notice(s)
5 Important Security notice(s)
5 Moderate Security notice(s)
Each line of the list names the advisory, its severity and the package version that fixes it. Advisory names differ by distribution; on CloudLinux they come from CloudLinux's own repositories.
2. Install the security updates
dnf upgrade --security
Or install every pending update, which also covers the security ones:
dnf upgrade
If you only want security fixes on a regular schedule, see How to Install Only Security Updates with yum and dnf.
3. Check the exclude line (cPanel servers)
If errata stay listed after the upgrade, look for an exclude= line. On CloudLinux 8 and 9, /etc/yum.conf is a link to /etc/dnf/dnf.conf, so one line covers both commands:
grep -E '^exclude' /etc/yum.conf
Packages that match this line are invisible to dnf: it will not list or install updates for them. In a test, adding exclude=openssl* made dnf check-update openssl report nothing, while the same check with excludes switched off showed the pending update:
dnf check-update --disableexcludes=all openssl
Output (lab example):
openssl.x86_64 1:3.5.8-2.el9_8 baseos
cPanel adds such a line on purpose. The excluded names are operating system packages (for example the web server, PHP, Exim, Dovecot and FTP server packages) that cPanel replaces with its own builds, such as the EasyApache ea- packages, and keeps up to date itself. Do not remove the exclude line or force those packages in with --disableexcludes: cPanel puts the line back on its next update, and the operating system versions can conflict with cPanel's own. See How to Exclude or Skip a Package in yum and dnf Updates for how the exclude line works.
4. Let cPanel update its own packages
Errata for packages on the exclude line are cleared by keeping cPanel current. Automatic cPanel updates do this; to run one now:
/usr/local/cpanel/scripts/upcp
Those entries in CLN can be treated as covered as long as cPanel updates run and succeed. If cPanel updates fail, fix that first, because then those packages are really out of date.
5. Kernel errata
A new kernel package only protects the server after a reboot into it, so kernel errata can stay listed until you reboot. With KernelCare, fixes are applied to the running kernel without a reboot; see WHM or cPanel is asking for a reboot while KernelCare is used.
6. Give CLN time to refresh
CLN shows what the server reported at its last check-in, so the errata list can lag behind the server for a while after you update. Compare with the dnf updateinfo list --security output on the server, which is always current.
Need a hand keeping a CloudLinux or cPanel server patched? Our engineers handle this through cPanel server management.
Official documentation: CloudLinux Network dashboard and cPanel, the upcp script.