AlmaLinux OS 9.9 and 10.3 released: ModSecurity is back

10 min read

Half a year after 9.8 and 10.2, two releases have again come out at the same time: on 16 November 2026, the AlmaLinux OS Foundation made available the stable versions of AlmaLinux OS 10.3 ‘Mauve Lion’ and AlmaLinux OS 9.9 ‘Chartreuse Bobcat’. The most important news for server operators: the ModSecurity web application firewall is back in the 10 branch, the container tools have moved to Podman 6, PHP 8.4 has arrived on the 9 branch, and both kernels include security fixes that are missing from the corresponding RHEL kernel.

  AlmaLinux 9.9 AlmaLinux 10.3
Code name Chartreuse Bobcat Mauve Lion
Kernel 5.14.0-741.22.1.el9_9 6.12.0-264.16.1.el10_3
Architectures x86_64, aarch64, ppc64le, s390x x86_64, x86_64_v2, aarch64, ppc64le, s390x, i686 (user packages only)
Kernel fixes not in RHEL 44 CVEs 36 CVEs
End of security updates 31 May 2032 31 May 2035

AlmaLinux 10.3 ‘Mauve Lion’

ModSecurity is back

For web server operators, this is the most important new feature of the release: the ModSecurity web application firewall (mod_security) and the OWASP Core Rule Set (mod_security_crs) are part of the distribution again. AlmaLinux 8 and 9 included them, but they were missing from 10.0–10.2.

The version jump is a big one: AlmaLinux 9 ships ModSecurity 2.9.6 with CRS 3.3.5, while 10.3 ships 2.9.14 with CRS 4.22.0. CRS 4 is not a simple update but a reorganisation of the rule set, so if you are moving your own rules and exclusions over from an AlmaLinux 9 server, review them before they see live traffic.

dnf install mod_security mod_security_crs
systemctl restart httpd

Podman 6: container settings move out of /etc

The container tools were updated together (podman 6.1.1, buildah 1.45.0, skopeo 1.24.0, crun 1.30.1, netavark and aardvark-dns 2.1.0), and the default settings have moved from the /etc/containers directory to /usr/share/containers. Whatever you have written under /etc/containers is kept after the update and still overrides the defaults. The rootful and rootless storage settings now have separate drop-in directories, so the defaults for rootless containers can be set under /etc/containers/containers.rootless.conf.d/ without touching rootful containers.

Podman 6 drops several old components, so on a machine that runs containers, check the following before you update:

  • CNI networking has been removed; Netavark is the only network backend
  • the BoltDB database backend has been removed; Podman uses SQLite
  • in rootless networking, pasta has replaced slirp4netns
  • cgroups v1 is no longer supported
  • firewall rules are handled by nftables instead of iptables

As the components have to be updated together, the containers-common package conflicts with podman older than 6, buildah older than 1.44 and skopeo older than 1.23. If you are also choosing between Docker and Podman, our guide to installing Docker covers AlmaLinux too.

New versions

Area Versions
New packages Node.js 26.12.1, .NET 11 (preview), ModSecurity 2.9.14 with OWASP CRS 4.22.0, IGVM 0.4.0, Intel QPL 1.9.0, libzpc 2.0.1 (IBM Z)
Compilers and toolkits GCC Toolset 16 (gcc 16.2.1, binutils 2.46), LLVM Toolset 22.1.8, Rust Toolset 1.97.1, Go 1.27, system compiler: GCC 14.4.1
Debugging and logging GDB 17.2, Valgrind 3.27.1, SystemTap 5.5, bpftrace 0.26.1, PCP 7.1.5, Grafana 12.4.3, rsyslog 8.2604.0
Security OpenSSL 3.5.9, OpenSSH 9.9p1, SELinux-policy 42.1.27, SSSD 2.13.1, crypto-policies 20260811, audit 4.2.1, fapolicyd 2.0.1, Keylime 7.14, Libreswan 5.4
Network NetworkManager 1.58.0, iproute 7.0.0, ethtool 6.19, BIND 9.18.33, FRR 10.6.1
Containers and virtualisation podman 6.1.1, buildah 1.45.0, skopeo 1.24.0, libvirt 12.5.0, QEMU-KVM 10.1.0, bootc 1.17.1
Miscellaneous systemd 257, glibc 2.39, Samba 4.24.5, Mesa 26.1.1, Cockpit 366.1.1, Pacemaker 3.0.3, Valkey 8.1.10

Quantum-safe encryption continues to spread as well: audit 4.2 can use quantum-safe TLS for remote logging, and Libreswan 5.4 offers ML-KEM key exchange for IPsec VPNs.

What carries over from earlier 10.x releases

The differences between AlmaLinux 10 and RHEL 10 remain in 10.3:

  • Btrfs: support introduced in 10.1; the system can also boot from a Btrfs volume
  • CRB repository enabled by default
  • x86_64_v2 version for older processors, with matching EPEL packages
  • i686 user packages for 32-bit programs and CI pipelines (there is no installable 32-bit system or kernel)
  • KVM on IBM POWER, frame pointers by default and SPICE support
  • Legacy hardware: drivers for Adaptec, Dell PERC, HP, Mellanox, QLogic, Emulex, LSI and Broadcom controllers that were disabled upstream still recognise these devices

AlmaLinux 9.9 ‘Chartreuse Bobcat’

From a web perspective, the most important new feature of 9.9 is that PHP 8.4 and Node.js 26 have arrived as new module streams. PHP 8.4 was previously only available in AlmaLinux 10.2, so servers staying on the 9 branch can now run it from an operating system package as well. You can enable the module like this:

dnf module reset php
dnf module enable php:8.4
dnf install php php-fpm php-mysqlnd

Our article Installing Apache and PHP on AlmaLinux 9 covers setting up Apache and PHP, and we have written about the changes in newer PHP versions in What’s new in PHP 8.5.

Area Versions
New module streams and packages PHP 8.4, Node.js 26, .NET 11, Intel QPL 1.9.0, oci-delta 0.3.0
Compilers and toolkits GCC Toolset 16 (gcc 16.2.1, binutils 2.46; GCC Toolset 15 remains available), LLVM Toolset 22.1.8, Rust Toolset 1.97.1, Go 1.27
Debugging and logging GDB 17.2, Valgrind 3.27.1, SystemTap 5.5, elfutils 0.195, bpftrace 0.26.1, BCC 0.36.1, rsyslog 8.2604.0
Security SELinux-policy 38.1.86, SSSD 2.9.9, crypto-policies 20260714, fapolicyd 2.0.1, authselect 1.2.7, Keylime 7.14.3, clevis 23, opencryptoki 3.27.0
Network NetworkManager 1.54.4, ethtool 6.19, BIND 9.16.50, unbound 1.26.1, OpenLDAP 2.6.13
Containers and virtualisation podman 5.8.5, buildah 1.43.4, crun 1.29.1, QEMU-KVM 10.1.0, bootc 1.16.9, ostree 2026.4
Miscellaneous systemd 252, glibc 2.34, Samba 4.24.5, Mesa 26.1.1, Cockpit 366.1, 389-ds-base 2.9.0, Pacemaker 2.1.11, Valkey 8.1.10

opencryptoki 3.27 also handles ML-DSA and ML-KEM quantum-safe key types. On the 9 branch, Podman stays in the 5.8 series; the Podman 6 changes only affect 10.3.

9.9 also keeps the kernel fix that 9.8 received ahead of RHEL by decision of ALESCo (AlmaLinux Engineering Steering Committee): the ‘proc: fix a dentry lock race between release_task and lookup’ fix stops systemd and ps from using an unnecessary amount of processor time when processes terminate. RHEL 9.9 has not picked up this fix either, so AlmaLinux continues to carry it itself.

Changes affecting both releases

These are worth checking before you update, as they also affect existing settings:

  • authselect: group merging is no longer the default. If your system assembles group memberships from several sources (for example local files and SSSD), turn it back on after the update: authselect enable-feature with-group-merging.
  • fapolicyd 2.0 instead of 1.4: the file access policy daemon now makes decisions in parallel, and updates the policy together with the trust database in a single transaction. As every program start on a hardened system goes through it, try your existing rules on a test machine first.
  • GCC Toolset 16: the default C++ standard is gnu++20 instead of gnu++17. If your project is not ready for this yet, compile with the -std=gnu++17 switch. The system’s default compiler does not change.

Security fixes

Both releases include fixes for the vulnerabilities AlmaLinux has written about since the beta versions:

  • PwnEscape (CVE-2026-99999)
  • PHP2Shell (CVE-2026-109618, CVE-2026-109619), see our PHP2Shell article
  • ZDI-CAN-33367
  • CVE-2026-98432
  • CVE-2026-98276

The kernel is more interesting: the AlmaLinux team compared the new kernels with the last kernels of 9.8 and 10.2, and found fixes that were still in the old kernel but not in the new one. The last RHEL 9.8 kernel included fixes for 43 CVEs, and the last RHEL 10.2 kernel for 30 CVEs, that are missing from the RHEL 9.9 and 10.3 kernels respectively. So that the update does not bring back vulnerabilities that had already been fixed, AlmaLinux put these back into its own kernels. On top of these, at the community’s request, fixes that were never in RHEL have also been added (including CVE-2026-98276 above): 1 CVE in 9.9 and 6 CVEs in 10.3.

In total, the AlmaLinux 9.9 kernel thus includes fixes for 44 CVEs and the 10.3 kernel for 36 CVEs that are still missing from the corresponding RHEL kernel. The most severe have a CVSS score of 8.8 (for example the missing validation of the KVM SEV guest GHCB area and a bug in ipvlan). The full list with scores is in the release notes.

Installation images and other images

The installation ISOs are available in all three usual variants (boot, minimal, dvd) on the mirrors and via torrent. The Live Media, Generic Cloud and OpenNebula images became available on release day, the rest (AWS, Azure, Google Cloud, Oracle Cloud, container, LXC/LXD, Vagrant, WSL) during the day, and the Raspberry Pi images will follow shortly after. AlmaLinux now serves the Vagrant boxes from its own catalogue.

AlmaLinux 9.9 (x86_64):

wget https://repo.almalinux.org/almalinux/RPM-GPG-KEY-AlmaLinux-9
gpg --import RPM-GPG-KEY-AlmaLinux-9
wget https://repo.almalinux.org/almalinux/9.9/isos/x86_64/CHECKSUM
gpg --verify CHECKSUM
sha256sum AlmaLinux-9.9-x86_64-boot.iso

AlmaLinux 10.3 (for the current machine’s architecture):

wget https://repo.almalinux.org/almalinux/RPM-GPG-KEY-AlmaLinux-10
gpg --import RPM-GPG-KEY-AlmaLinux-10
wget https://repo.almalinux.org/almalinux/10.3/isos/$(uname -m)/CHECKSUM
gpg --verify CHECKSUM
sha256sum AlmaLinux-10.3-$(uname -m)-boot.iso

For 9.9, a ‘Good signature’ line should appear for the ‘AlmaLinux OS 9’ key (fingerprint BF18 AC28 7617 8908 D6E7 1267 D36C B86C B86B 3716), and for 10.3 for the ‘AlmaLinux OS 10’ key (fingerprint EE6D B7B9 8F5B F5ED D9DA 0DE5 DEE5 C11C C2A1 E572), and the calculated SHA256 sum must match the one in the CHECKSUM file. For the x86_64_v2 ISO, enter the directory name x86_64_v2 by hand in place of $(uname -m).

Update

On an existing AlmaLinux 9 or 10 system, the update is the usual command:

dnf upgrade -y

On an AlmaLinux 10 machine that runs containers, review the Podman 6 changes above first, and on a hardened system the fapolicyd rules. Users of the beta versions switch to the stable release by replacing the release packages (on the 9.9 beta, 9 goes into the file name instead of 10):

dnf install https://repo.almalinux.org/almalinux/almalinux-{release,repos,gpg-keys}-latest-10.$(uname -m).rpm
dnf upgrade -y

For major version upgrades (8 → 9, 9 → 10), our ELevate guide can help.

The full list of changes can be found in the release notes for AlmaLinux 9.9 and 10.3, as well as in the release notes for RHEL 9.9 and RHEL 10.3.

How long will they be supported?

Active support for AlmaLinux 9 runs until 31 May 2027, with security updates available until 31 May 2032; active support for AlmaLinux 10 runs until 31 May 2030, with security updates available until 31 May 2035. Previous releases in the two series:

If you’d like to try the new AlmaLinux on your own machine, you can install it with full root access on a KVM VPS server, and for heavier workloads you can also choose a dedicated server. Our cPanel hosting servers run CloudLinux OS, which is closely related to AlmaLinux and is also RHEL-compatible.

Back to the blog