CVE coverage

AlmaLinux 9 CVE tracker

Noxen pulls AlmaLinux 9 CVE data from the same upstream sources Red Hat publishes against (RHEL 9 binary-compatible). NVD provides the upstream advisory; OSV's Red Hat ecosystem feed provides the rpm-level fix versions. The AlmaLinux project also publishes its own errata, which we cross-reference.

Live

Headline numbers

  • Total CVE records (all distros)Loading…
  • Last buildLoading…
  • OSV records (RH ecosystem + others)Loading…
  • NVD records (cross-platform)Loading…

How matching works

What Noxen does for an AlmaLinux 9 host

  1. Reads /etc/os-release to confirm AlmaLinux 9 (RHEL 9 binary-compatible).
  2. Reads rpm -qa for installed packages, including epoch and release.
  3. Filters the local feed cache to OSV records tagged with ecosystem AlmaLinux:9 / Red Hat:9, plus NVD records whose CPE matches the installed packages.
  4. Compares installed vs fix versions using rpm version semantics (epoch:version-release).
  5. Emits findings only where the installed version is strictly older than the fix.

Live listings

Top recent critical CVEs (Red Hat ecosystem (RHEL / Rocky / AlmaLinux))

Most-recently-published critical CVEs in the Red Hat ecosystem (RHEL / Rocky / AlmaLinux). Auto-deduped to one row per CVE ID. Snapshot baked at ; live re-fetch on page load.

CVESev.CVSSSummaryPackageFix inPublished
RLSA-2026:22450critical9.1Important: osbuild-composer security updateosbuild-composer0:165.1-2.el10_2.rocky.0.1
RLSA-2026:22937critical9.1Important: image-builder security updateimage-builder0:52.1-1.el10_2.rocky.0.1
RLSA-2026:23228critical9.1Important: image-builder security updateimage-builder0:52.1-1.el9_8
RLSA-2026:21755critical9.0Important: flatpak security updateflatpak0:1.12.9-4.el9_8.1
RLSA-2026:20606critical9.1Important: ruby4.0 security updateruby4.00:4.0.3-34.el10_2
RLSA-2026:21757critical9.0Important: flatpak security updateflatpak0:1.16.0-9.el10_2.1
RLSA-2024:8834critical9.1Important: python-gevent security updatepython-gevent0:1.2.2-5.el8
RLSA-2026:19135critical9.1Important: opentelemetry-collector security updateopentelemetry-collector0:0.144.0-2.el10_2

Top recent high-severity CVEs (Red Hat ecosystem (RHEL / Rocky / AlmaLinux))

CVESev.CVSSSummaryPackageFix inPublished
RLSA-2026:23231high8.1Important: unbound security updateunbound0:1.24.2-7.el10_2.1
RLSA-2026:23388high7.5Important: php security updatephp0:8.3.31-1.el10_2
RLSA-2026:22643high7.5Important: thunderbird security updatethunderbird0:140.11.0-1.el8_10
RLSA-2026:23360high7.5Important: bind9.16 security updatebind9.162:9.16.23-0.22.el8_10.6
RLSA-2026:20613high8.2Important: gnutls security updategnutls0:3.8.10-4.el10_2
RLSA-2026:22649high8.2Important: php8.4 security updatephp8.40:8.4.21-1.el10_2
RLSA-2026:22141high7.8Moderate: go-fdo-client and go-fdo-server security updatego-fdo-server0:1.0.1-2.el10_2
RLSA-2026:22145high7.5Important: .NET 10.0 security updatedotnet10.00:10.0.108-1.el10_2

New to severity terminology? CVE, CVSS, CWE, CPE explained.

Notable

Recent CVEs that AlmaLinux 9 homelabs care about.

FAQ

Frequently asked about AlmaLinux 9 CVEs

How is AlmaLinux 9 different from RHEL 9 for CVE tracking?

Functionally, very little. AlmaLinux 9 is binary-compatible with RHEL 9 and rebuilds Red Hat's source packages on the same release cadence, so a fix landing in RHEL 9 lands in AlmaLinux 9 within days. Noxen matches against the Red Hat ecosystem feed plus AlmaLinux errata to pick up both channels.

How do I check AlmaLinux 9 CVEs on a host?

For a quick check: dnf updateinfo list security. For per-CVE detail with fix versions, Noxen reads rpm package state over SSH and matches against the live ecosystem feed using rpm version semantics (epoch:version-release).

Is AlmaLinux 9 still supported in 2026?

Yes — the AlmaLinux 9 lifecycle tracks RHEL 9 (active maintenance phase through May 2032). Major and minor security errata continue throughout this window.

Will Noxen flag a CVE that AlmaLinux 9 has already backported a fix for?

No. Red Hat-family distros backport security fixes without changing the upstream version number — the fix shows up as a higher release field (the part after the dash in epoch:version-release). Noxen compares the installed epoch:version-release against the fixed package version using rpm version semantics, so a host that has applied the backported errata is correctly shown as patched rather than as a false positive.

Which AlmaLinux 9 CVEs should I patch first?

Severity alone is a poor sort key. Noxen ranks findings by exposure first — a high-severity CVE in a package behind an internet-facing service outranks a critical one in a library nothing reaches — then by CVSS and EPSS. The EPSS prioritisation guide walks through the reasoning.

Scan an AlmaLinux 9 fleet with Noxen

Add your AlmaLinux 9 hosts via your existing ~/.ssh/config; Noxen reads rpm package state and matches against the live signed feed. No agent, no SaaS round-trip. $79 one-time.

← back to the CVE dashboard   Debian 11 →   AlmaLinux 8 →