Last scanned:
This base/runtime image carries significant vulnerabilities that any image built on it would inherit; remediate them in the final image before production. A remote attacker could trigger denial-of-service or memory corruption in GnuTLS (CVE-2026-33846), and a specially crafted ISO9660 image could lead to arbitrary code execution via libarchive (CVE-2026-5121) on 32-bit systems. The most severe issues are in components that may not be enabled by default (e.g., DTLS, QUIC), so their real-world impact depends on the application. These vulnerabilities are important to patch, but they do not make the base image unusable for production if addressed in the final image. Note: this is a general-purpose base/runtime image — many findings live in components that an application built on top may never load, so actual exploitability depends on the final image. For an accurate risk picture, re-scan the final application image with context.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-33846 | HIGH7.5 | gnutls 3.8.3-4.el9_4 fixed in 3.8.10-4.el9_8 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42009 | HIGH7.5 | gnutls 3.8.3-4.el9_4 fixed in 3.8.10-4.el9_8 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5121 | HIGH7.5 | libarchive 3.5.3-4.el9 fixed in 3.5.3-9.el9_7 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34183 | HIGH7.5 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.5.5-4.el9_8 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-12797 | HIGH7.4 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.2.2-6.el9_5.1 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-52533 | HIGH7 | glib2 2.68.4-14.el9_4.1 fixed in 2.68.4-16.el9_6.2 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42013 | MEDIUM6.97 | gnutls 3.8.3-4.el9_4 fixed in 3.8.10-4.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM6.97 | gnutls 3.8.3-4.el9_4 fixed in 3.8.10-4.el9_8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-32990 | MEDIUM6.97 | gnutls 3.8.3-4.el9_4 fixed in 3.8.3-6.el9_6.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | glibc 2.34-100.el9_4.3 fixed in 2.34-231.el9_7.10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | glibc-common 2.34-100.el9_4.3 fixed in 2.34-231.el9_7.10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | glibc-minimal-langpack 2.34-100.el9_4.3 fixed in 2.34-231.el9_7.10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-5914 | MEDIUM6.63 | libarchive 3.5.3-4.el9 fixed in 3.5.3-6.el9_6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-25724 | MEDIUM6.63 | libarchive 3.5.3-4.el9 fixed in 3.5.3-5.el9_6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48864 | MEDIUM6.63 | libsolv 0.7.24-2.el9 fixed in 0.7.24-6.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49043 | MEDIUM6.63 | libxml2 2.9.13-6.el9_4 fixed in 2.9.13-6.el9_5.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7425 | MEDIUM6.63 | libxml2 2.9.13-6.el9_4 fixed in 2.9.13-11.el9_6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | systemd-libs 252-32.el9_4.7 fixed in 252-67.el9_8.2.alma.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13601 | MEDIUM6.54 | glib2 2.68.4-14.el9_4.1 fixed in 2.68.4-18.el9_7.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-24928 | MEDIUM6.54 | libxml2 2.9.13-6.el9_4 fixed in 2.9.13-6.el9_5.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | krb5-libs 1.21.1-2.el9_4 fixed in 1.21.1-10.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | krb5-libs 1.21.1-2.el9_4 fixed in 1.21.1-10.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4111 | MEDIUM6.38 | libarchive 3.5.3-4.el9 fixed in 3.5.3-7.el9_7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-4424 | MEDIUM6.38 | libarchive 3.5.3-4.el9 fixed in 3.5.3-9.el9_7 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-27135 | MEDIUM6.38 | libnghttp2 1.43.0-5.el9_4.3 fixed in 1.43.0-6.el9_7.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-32414 | MEDIUM6.38 | libxml2 2.9.13-6.el9_4 fixed in 2.9.13-12.el9_6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-32415 | MEDIUM6.38 | libxml2 2.9.13-6.el9_4 fixed in 2.9.13-12.el9_6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.5.1-7.el9_7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-3833 | MEDIUM6.29 | gnutls 3.8.3-4.el9_4 fixed in 3.8.10-4.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM6.29 | gnutls 3.8.3-4.el9_4 fixed in 3.8.10-4.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.5.5-4.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.5.1-7.el9_7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11187 | MEDIUM6.1 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.5.1-7.el9_7 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42012 | MEDIUM6.03 | gnutls 3.8.3-4.el9_4 fixed in 3.8.10-4.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54369 | MEDIUM6.03 | libacl 2.3.1-4.el9 fixed in 2.4.0-1.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | glibc 2.34-100.el9_4.3 fixed in 2.34-168.el9_6.19 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | glibc-common 2.34-100.el9_4.3 fixed in 2.34-168.el9_6.19 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | glibc-minimal-langpack 2.34-100.el9_4.3 fixed in 2.34-168.el9_6.19 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4878 | MEDIUM5.95 | libcap 2.48-9.el9_2 fixed in 2.48-10.el9_8.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | krb5-libs 1.21.1-2.el9_4 fixed in 1.21.1-3.el9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt 1.10.0-10.el9_2 fixed in 1.10.0-11.el9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1 4.16.0-8.el9_1 fixed in 4.16.0-10.el9_8 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-5535 | MEDIUM5.9 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.2.2-6.el9_5 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.9 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.5.5-4.el9_8 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.9 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.5.5-2.el9_8 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.61 | gnutls 3.8.3-4.el9_4 fixed in 3.8.10-4.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.5.1-4.el9_7 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4741 | MEDIUM5.6 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.2.2-6.el9_5 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14512 | MEDIUM5.52 | glib2 2.68.4-14.el9_4.1 fixed in 2.68.4-19.el9_8.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc 2.34-100.el9_4.3 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | glibc 2.34-100.el9_4.3 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc-common 2.34-100.el9_4.3 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | glibc-common 2.34-100.el9_4.3 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc-minimal-langpack 2.34-100.el9_4.3 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | glibc-minimal-langpack 2.34-100.el9_4.3 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6395 | MEDIUM5.52 | gnutls 3.8.3-4.el9_4 fixed in 3.8.3-6.el9_6.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | krb5-libs 1.21.1-2.el9_4 fixed in 1.21.1-6.el9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-34459 | MEDIUM5.5 | libxml2 2.9.13-6.el9_4 fixed in 2.9.13-14.el9_8.1 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54370 | MEDIUM5.35 | libacl 2.3.1-4.el9 fixed in 2.4.0-1.el9_8 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM5.35 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.5.5-4.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-12243 | MEDIUM5.3 | gnutls 3.8.3-4.el9_4 fixed in 3.8.3-6.el9 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-32989 | MEDIUM5.3 | gnutls 3.8.3-4.el9_4 fixed in 3.8.3-6.el9_6.2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-12133 | MEDIUM5.3 | libtasn1 4.16.0-8.el9_1 fixed in 4.16.0-9.el9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4603 | MEDIUM5.3 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.2.2-6.el9_5 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid 2.37.4-18.el9 fixed in 2.37.4-21.el9_7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount 2.37.4-18.el9 fixed in 2.37.4-21.el9_7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libsmartcols 2.37.4-18.el9 fixed in 2.37.4-21.el9_7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid 2.37.4-18.el9 fixed in 2.37.4-21.el9_7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | glibc 2.34-100.el9_4.3 fixed in 2.34-231.el9_7.10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc 2.34-100.el9_4.3 fixed in 2.34-274.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | glibc-common 2.34-100.el9_4.3 fixed in 2.34-231.el9_7.10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc-common 2.34-100.el9_4.3 fixed in 2.34-274.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | glibc-minimal-langpack 2.34-100.el9_4.3 fixed in 2.34-231.el9_7.10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc-minimal-langpack 2.34-100.el9_4.3 fixed in 2.34-274.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | krb5-libs 1.21.1-2.el9_4 fixed in 1.21.1-3.el9 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | krb5-libs 1.21.1-2.el9_4 fixed in 1.21.1-8.el9_6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15468 | MEDIUM5.02 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.5.1-7.el9_7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-66199 | MEDIUM5.02 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.5.1-7.el9_7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.5.1-7.el9_7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.5.1-7.el9_7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.02 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.5.5-4.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.5.5-4.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.5.5-4.el9_8 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2511 | MEDIUM4.81 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.2.2-6.el9_5 | 54.0% Actively Exploited | Directly Exposed |
| CVE-2025-5702 | MEDIUM4.76 | glibc 2.34-100.el9_4.3 fixed in 2.34-168.el9_6.20 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5702 | MEDIUM4.76 | glibc-common 2.34-100.el9_4.3 fixed in 2.34-168.el9_6.20 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5702 | MEDIUM4.76 | glibc-minimal-langpack 2.34-100.el9_4.3 fixed in 2.34-168.el9_6.20 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | glibc 2.34-100.el9_4.3 fixed in 2.34-125.el9_5.8.alma.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | glibc-common 2.34-100.el9_4.3 fixed in 2.34-125.el9_5.8.alma.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | glibc-minimal-langpack 2.34-100.el9_4.3 fixed in 2.34-125.el9_5.8.alma.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26462 | MEDIUM4.67 | krb5-libs 1.21.1-2.el9_4 fixed in 1.21.1-3.el9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-9714 | MEDIUM4.67 | libxml2 2.9.13-6.el9_4 fixed in 2.9.13-14.el9_7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15469 | MEDIUM4.67 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.5.1-7.el9_7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM4.67 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.5.1-7.el9_7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | glibc 2.34-100.el9_4.3 fixed in 2.34-231.el9_7.10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc 2.34-100.el9_4.3 fixed in 2.34-270.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | glibc-common 2.34-100.el9_4.3 fixed in 2.34-231.el9_7.10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-common 2.34-100.el9_4.3 fixed in 2.34-270.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | glibc-minimal-langpack 2.34-100.el9_4.3 fixed in 2.34-231.el9_7.10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-minimal-langpack 2.34-100.el9_4.3 fixed in 2.34-270.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM4.5 | gnutls 3.8.3-4.el9_4 fixed in 3.8.10-4.el9_8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-14831 | MEDIUM4.5 | gnutls 3.8.3-4.el9_4 fixed in 3.8.3-10.el9_7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.5.5-4.el9_8 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc 2.34-100.el9_4.3 fixed in 2.34-272.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc 2.34-100.el9_4.3 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-common 2.34-100.el9_4.3 fixed in 2.34-272.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc-common 2.34-100.el9_4.3 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-minimal-langpack 2.34-100.el9_4.3 fixed in 2.34-272.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc-minimal-langpack 2.34-100.el9_4.3 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-4373 | MEDIUM4.08 | glib2 2.68.4-14.el9_4.1 fixed in 2.68.4-16.el9_6.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15467 | MEDIUM4.06 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.5.1-7.el9_7 | 47.6% High Exploitation Risk | Post-Exploit |
| CVE-2025-68160 | MEDIUM4 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.5.1-7.el9_7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4598 | MEDIUM4 | systemd-libs 252-32.el9_4.7 fixed in 252-55.el9_7.7.alma.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-3596 | LOW3.73 | krb5-libs 1.21.1-2.el9_4 fixed in 1.21.1-4.el9_5 | 14.9% High Exploitation Risk | Post-Exploit |
| CVE-2025-6965 | LOW3.61 | sqlite-libs 3.34.1-7.el9_3 fixed in 3.34.1-9.el9_7 | 74.4% Actively Exploited | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gnupg2 2.3.3-4.el9 fixed in 2.3.3-5.el9_7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-12900 | LOW3.53 | bzip2-libs 1.0.8-8.el9 fixed in 1.0.8-10.el9_5 | 8.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42010 | LOW3.53 | gnutls 3.8.3-4.el9_4 fixed in 3.8.10-4.el9_8 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-56171 | LOW3.53 | libxml2 2.9.13-6.el9_4 fixed in 2.9.13-6.el9_5.2 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4438 | LOW3.4 | glibc 2.34-100.el9_4.3 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | glibc-common 2.34-100.el9_4.3 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | glibc-minimal-langpack 2.34-100.el9_4.3 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-9820 | LOW3.4 | gnutls 3.8.3-4.el9_4 fixed in 3.8.3-10.el9_7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW3.4 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.5.1-7.el9_7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-49796 | LOW3.28 | libxml2 2.9.13-6.el9_4 fixed in 2.9.13-10.el9_6 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3832 | LOW3.15 | gnutls 3.8.3-4.el9_4 fixed in 3.8.10-4.el9_8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-5419 | LOW3.15 | gnutls 3.8.3-4.el9_4 fixed in 3.8.10-4.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.5.5-4.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14087 | LOW3 | glib2 2.68.4-14.el9_4.1 fixed in 2.68.4-19.el9_8.1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-32988 | LOW2.95 | gnutls 3.8.3-4.el9_4 fixed in 3.8.3-6.el9_6.2 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.5.5-4.el9_8 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2020-11023 | LOW2.86 | libgcc 11.4.1-3.el9.alma.1 fixed in 11.5.0-5.el9_5.alma.1 | 83.8% Actively Exploited | Post-Exploit |
| CVE-2020-11023 | LOW2.86 | libstdc++ 11.4.1-3.el9.alma.1 fixed in 11.5.0-5.el9_5.alma.1 | 83.8% Actively Exploited | Post-Exploit |
| CVE-2026-58016 | LOW2.78 | glib2 2.68.4-14.el9_4.1 fixed in 2.68.4-19.el9_8.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-33845 | LOW2.78 | gnutls 3.8.3-4.el9_4 fixed in 3.8.10-4.el9_8 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-49794 | LOW2.78 | libxml2 2.9.13-6.el9_4 fixed in 2.9.13-10.el9_6 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | LOW2.78 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-6021 | LOW2.7 | libxml2 2.9.13-6.el9_4 fixed in 2.9.13-10.el9_6 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28390 | LOW2.7 | openssl-libs 1:3.0.7-28.el9_4 fixed in 1:3.5.5-3.el9_8 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-2100 | LOW2.7 | p11-kit 0.25.3-2.el9 fixed in 0.26.2-1.el9 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-2100 | LOW2.7 | p11-kit-trust 0.25.3-2.el9 fixed in 0.26.2-1.el9 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils-single 8.32-35.el9 fixed in 8.32-41.el9_8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6170 | LOW2.12 | libxml2 2.9.13-6.el9_4 fixed in 2.9.13-14.el9_8.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9086 | LOW1.91 | curl-minimal 7.76.1-29.el9_4.1 fixed in 7.76.1-35.el9_7.3 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-9086 | LOW1.91 | libcurl-minimal 7.76.1-29.el9_4.1 fixed in 7.76.1-35.el9_7.3 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | shadow-utils 2:4.9-8.el9 fixed in 2:4.9-15.el9 | 0.4% Theoretical Threat | Post-Exploit |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.