Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker could cause denial-of-service by supplying crafted XML that crashes the API gateway process (CVE-2026-6653), and local crafted disk-image probing could corrupt partition metadata integrity (CVE-2026-53615). Disabling any plugin or feature that parses untrusted XML would fully eliminate CVE-2026-6653. Note: CVE-2026-6653 only applies if such XML parsing is enabled. Although no exposed finding reaches severity 7.0, the 212 exposed-surface issues and 52 findings at severity 6.0 or above keep the image in the CAUTION band.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-53615 | MEDIUM6.8 | libsmartcols 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM6.8 | libuuid 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6653 | MEDIUM6.66 | libxml2 2.9.13-14.el9_8.2 fixed in 2.9.13-14.el9_8.4 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-76957 | MEDIUM6.63 | expat 2.5.0-6.el9_8.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86140 | MEDIUM6.63 | libxml2 2.9.13-14.el9_8.2 fixed in 2.9.13-14.el9_8.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11979 | MEDIUM6.63 | libxml2 2.9.13-14.el9_8.2 fixed in 2.9.13-14.el9_8.4 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86138 | MEDIUM6.63 | libxml2 2.9.13-14.el9_8.2 fixed in 2.9.13-14.el9_8.5 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86142 | MEDIUM6.63 | libxml2 2.9.13-14.el9_8.2 fixed in 2.9.13-14.el9_8.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86144 | MEDIUM6.63 | libxml2 2.9.13-14.el9_8.2 fixed in 2.9.13-14.el9_8.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89161 | MEDIUM6.63 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95519 | MEDIUM6.63 | rpm-build-libs 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95521 | MEDIUM6.63 | rpm-build-libs 4.16.1.3-40.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-95519 | MEDIUM6.63 | rpm-libs 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95521 | MEDIUM6.63 | rpm-libs 4.16.1.3-40.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-95519 | MEDIUM6.63 | rpm-plugin-systemd-inhibit 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95521 | MEDIUM6.63 | rpm-plugin-systemd-inhibit 4.16.1.3-40.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-95519 | MEDIUM6.63 | rpm-sign-libs 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95521 | MEDIUM6.63 | rpm-sign-libs 4.16.1.3-40.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-11822 | MEDIUM6.63 | sqlite-libs 3.34.1-10.el9_8 fixed in 3.34.1-11.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11824 | MEDIUM6.63 | sqlite-libs 3.34.1-10.el9_8 fixed in 3.34.1-11.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63382 | MEDIUM6.54 | libevent 2.1.12-8.el9_4 fixed in 2.1.13-1.el9_8 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-63385 | MEDIUM6.54 | libevent 2.1.12-8.el9_4 fixed in 2.1.13-1.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | libgcc 11.5.0-14.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | libgomp 11.5.0-14.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | libstdc++ 11.5.0-14.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-103111 | MEDIUM6.46 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-66046 | MEDIUM6.38 | expat 2.5.0-6.el9_8.1 fixed in 2.5.0-6.el9_8.5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-76641 | MEDIUM6.38 | expat 2.5.0-6.el9_8.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-93990 | MEDIUM6.38 | expat 2.5.0-6.el9_8.1 fixed in 2.5.0-6.el9_8.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-32636 | MEDIUM6.38 | glib2 2.68.4-19.el9_8.9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-63383 | MEDIUM6.38 | libevent 2.1.12-8.el9_4 fixed in 2.1.13-1.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63384 | MEDIUM6.38 | libevent 2.1.12-8.el9_4 fixed in 2.1.13-1.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-14456 | MEDIUM6.38 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63072 | MEDIUM6.38 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM6.38 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM6.38 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-54874 | MEDIUM6.38 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM6.38 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM6.38 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-84782 | MEDIUM6.29 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-2.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-89157 | MEDIUM6.29 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86143 | MEDIUM6.21 | libxml2 2.9.13-14.el9_8.2 fixed in 2.9.13-14.el9_8.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-16118 | MEDIUM6.03 | glib2 2.68.4-19.el9_8.9 fixed in 2.68.4-19.el9_8.10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-103242 | MEDIUM6.03 | rpm-build-libs 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95520 | MEDIUM6.03 | rpm-build-libs 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-103242 | MEDIUM6.03 | rpm-libs 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95520 | MEDIUM6.03 | rpm-libs 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-103242 | MEDIUM6.03 | rpm-plugin-systemd-inhibit 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95520 | MEDIUM6.03 | rpm-plugin-systemd-inhibit 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-103242 | MEDIUM6.03 | rpm-sign-libs 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95520 | MEDIUM6.03 | rpm-sign-libs 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-27113 | MEDIUM6 | libxml2 2.9.13-14.el9_8.2 No fix yet | 1.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86805 | MEDIUM5.95 | glibc 2.34-275.el9_8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM5.95 | glibc 2.34-275.el9_8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM5.95 | glibc-common 2.34-275.el9_8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM5.95 | glibc-common 2.34-275.el9_8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM5.95 | libblkid 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM5.95 | libfdisk 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libgcc 11.5.0-14.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libgomp 11.5.0-14.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM5.95 | libmount 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM5.95 | libsmartcols 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libstdc++ 11.5.0-14.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM5.95 | libuuid 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78367 | MEDIUM5.95 | rpm-build-libs 4.16.1.3-40.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78367 | MEDIUM5.95 | rpm-libs 4.16.1.3-40.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78367 | MEDIUM5.95 | rpm-plugin-systemd-inhibit 4.16.1.3-40.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78367 | MEDIUM5.95 | rpm-sign-libs 4.16.1.3-40.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41996 | MEDIUM5.9 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63073 | MEDIUM5.9 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56132 | MEDIUM5.87 | expat 2.5.0-6.el9_8.1 fixed in 2.5.0-6.el9_8.3 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM5.87 | expat 2.5.0-6.el9_8.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56404 | MEDIUM5.87 | expat 2.5.0-6.el9_8.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56405 | MEDIUM5.87 | expat 2.5.0-6.el9_8.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM5.87 | expat 2.5.0-6.el9_8.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56407 | MEDIUM5.87 | expat 2.5.0-6.el9_8.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | openldap 2.6.8-4.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | systemd-libs 252-67.el9_8.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5915 | MEDIUM5.61 | libarchive 3.5.3-11.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5918 | MEDIUM5.61 | libarchive 3.5.3-11.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63381 | MEDIUM5.61 | libevent 2.1.12-8.el9_4 fixed in 2.1.13-1.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77214 | MEDIUM5.58 | expat 2.5.0-6.el9_8.1 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107778 | MEDIUM5.52 | krb5-libs 1.21.1-10.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4426 | MEDIUM5.52 | libarchive 3.5.3-11.el9_8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63379 | MEDIUM5.52 | libevent 2.1.12-8.el9_4 fixed in 2.1.13-1.el9_8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-9149 | MEDIUM5.52 | libsolv 0.7.24-6.el9_8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-9150 | MEDIUM5.52 | libsolv 0.7.24-6.el9_8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-45322 | MEDIUM5.52 | libxml2 2.9.13-14.el9_8.2 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-89158 | MEDIUM5.52 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89160 | MEDIUM5.52 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | MEDIUM5.35 | libattr 2.5.1-3.el9 fixed in 2.6.0-1.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1757 | MEDIUM5.27 | libxml2 2.9.13-14.el9_8.2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102633 | MEDIUM5.02 | expat 2.5.0-6.el9_8.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | MEDIUM5.02 | expat 2.5.0-6.el9_8.1 fixed in 2.5.0-6.el9_8.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56412 | MEDIUM5.02 | expat 2.5.0-6.el9_8.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | glibc 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.02 | glibc 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.02 | glibc 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | glibc-common 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.02 | glibc-common 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.02 | glibc-common 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0990 | MEDIUM5.02 | libxml2 2.9.13-14.el9_8.2 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-54872 | MEDIUM5.02 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-72897 | MEDIUM5.02 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75805 | MEDIUM5.02 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77696 | MEDIUM5.02 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42765 | MEDIUM5.02 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-89156 | MEDIUM5.02 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | MEDIUM5 | openssl 1:3.5.5-6.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | MEDIUM5 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5916 | MEDIUM4.76 | libarchive 3.5.3-11.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-84837 | MEDIUM4.68 | python3-rpm 4.16.1.3-40.el9 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-84837 | MEDIUM4.68 | rpm 4.16.1.3-40.el9 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1619 | MEDIUM4.68 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1720 | MEDIUM4.68 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2042 | MEDIUM4.68 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2124 | MEDIUM4.68 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2125 | MEDIUM4.68 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2126 | MEDIUM4.68 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2129 | MEDIUM4.68 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2175 | MEDIUM4.68 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2182 | MEDIUM4.68 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2183 | MEDIUM4.68 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2206 | MEDIUM4.68 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2207 | MEDIUM4.68 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2210 | MEDIUM4.68 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2257 | MEDIUM4.68 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2284 | MEDIUM4.68 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2285 | MEDIUM4.68 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2286 | MEDIUM4.68 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2304 | MEDIUM4.68 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2343 | MEDIUM4.68 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2344 | MEDIUM4.68 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2345 | MEDIUM4.68 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1371 | MEDIUM4.67 | elfutils-libelf 0.194-1.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1377 | MEDIUM4.67 | elfutils-libelf 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1371 | MEDIUM4.67 | elfutils-libs 0.194-1.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1377 | MEDIUM4.67 | elfutils-libs 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32776 | MEDIUM4.67 | expat 2.5.0-6.el9_8.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | MEDIUM4.67 | expat 2.5.0-6.el9_8.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | MEDIUM4.67 | expat 2.5.0-6.el9_8.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | expat 2.5.0-6.el9_8.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | glibc 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | glibc-common 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-60753 | MEDIUM4.67 | libarchive 3.5.3-11.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5745 | MEDIUM4.67 | libarchive 3.5.3-11.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1632 | MEDIUM4.67 | libarchive 3.5.3-11.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | MEDIUM4.67 | libgcc 11.5.0-14.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc 11.5.0-14.el9 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | MEDIUM4.67 | libgomp 11.5.0-14.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgomp 11.5.0-14.el9 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-24056 | MEDIUM4.67 | libpkgconf 1.7.3-10.el9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-82327 | MEDIUM4.67 | libsolv 0.7.24-6.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | MEDIUM4.67 | libstdc++ 11.5.0-14.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libstdc++ 11.5.0-14.el9 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-44605 | MEDIUM4.67 | rpm-build-libs 4.16.1.3-40.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44605 | MEDIUM4.67 | rpm-libs 4.16.1.3-40.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44605 | MEDIUM4.67 | rpm-plugin-systemd-inhibit 4.16.1.3-40.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44605 | MEDIUM4.67 | rpm-sign-libs 4.16.1.3-40.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50812 | MEDIUM4.67 | sqlite-libs 3.34.1-10.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-0232 | MEDIUM4.67 | sqlite-libs 3.34.1-10.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM4.67 | systemd-libs 252-67.el9_8.4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib 1.2.11-40.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40468 | MEDIUM4.64 | gawk 5.1.0-6.el9 fixed in 5.1.0-6.el9_8.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-1489 | MEDIUM4.59 | glib2 2.68.4-19.el9_8.9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-18798 | MEDIUM4.5 | openssl 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63076 | MEDIUM4.5 | openssl 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-14457 | MEDIUM4.5 | openssl 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-18798 | MEDIUM4.5 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63076 | MEDIUM4.5 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14457 | MEDIUM4.5 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1620 | MEDIUM4.5 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-3705 | MEDIUM4.5 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5344 | MEDIUM4.5 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-86469 | MEDIUM4.5 | glib2 2.68.4-19.el9_8.9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM4.5 | glibc 2.34-275.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM4.5 | glibc-common 2.34-275.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-30571 | MEDIUM4.5 | libarchive 3.5.3-11.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libblkid 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libfdisk 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libmount 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libsmartcols 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libuuid 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42772 | MEDIUM4.5 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54873 | MEDIUM4.5 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75804 | MEDIUM4.5 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM4.5 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-84784 | MEDIUM4.5 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | xz-libs 5.2.5-8.el9_0 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-7264 | MEDIUM4.48 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | 20.2% High Exploitation Risk | Post-Exploit |
| CVE-2024-7264 | MEDIUM4.48 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | 20.2% High Exploitation Risk | Post-Exploit |
| CVE-2021-4166 | MEDIUM4.26 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2287 | MEDIUM4.26 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42250 | MEDIUM4.25 | bzip2-libs 1.0.8-11.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | krb5-libs 1.21.1-10.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5917 | MEDIUM4.25 | libarchive 3.5.3-11.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86145 | MEDIUM4.18 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | glibc 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | glibc-common 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.17 | krb5-libs 1.21.1-10.el9_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-8458 | MEDIUM4.13 | curl-minimal 7.76.1-40.el9_8.5 fixed in 7.76.1-40.el9_8.7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | MEDIUM4.13 | libcurl-minimal 7.76.1-40.el9_8.5 fixed in 7.76.1-40.el9_8.7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-28387 | MEDIUM4.13 | openssl 1:3.5.5-6.el9_8 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-28387 | MEDIUM4.13 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-19445 | MEDIUM4.13 | python3 3.9.25-7.el9_8.3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19445 | MEDIUM4.13 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-97687 | MEDIUM4.13 | python3-urllib3 1.26.5-8.el9_8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | MEDIUM4.08 | util-linux 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | MEDIUM4.08 | util-linux-core 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1376 | MEDIUM4 | elfutils-libelf 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | MEDIUM4 | elfutils-libs 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libblkid 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libfdisk 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54875 | MEDIUM4 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | LOW3.98 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-79824 | LOW3.98 | python3 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-79824 | LOW3.98 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-95519 | LOW3.98 | python3-rpm 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-95521 | LOW3.98 | python3-rpm 4.16.1.3-40.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-95519 | LOW3.98 | rpm 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-95521 | LOW3.98 | rpm 4.16.1.3-40.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-43961 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-39881 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2021-3928 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-0351 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-2522 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-2817 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2819 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-2845 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2849 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2862 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-2889 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2946 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2982 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-3016 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3037 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3099 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3134 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-3234 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3235 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3256 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3296 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-3297 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3324 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3352 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-4141 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-4292 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-0049 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-0051 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-0054 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-0288 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-0433 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-0512 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-1127 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-2610 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-4734 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4735 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4738 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4751 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4781 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-5535 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-22667 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1215 | LOW3.98 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-0213 | LOW3.96 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-92388 | LOW3.9 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | — | Post-Exploit |
| CVE-2024-9681 | LOW3.9 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-86414 | LOW3.9 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | — | Post-Exploit |
| CVE-2026-92390 | LOW3.9 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | — | Post-Exploit |
| CVE-2026-92388 | LOW3.9 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | — | Post-Exploit |
| CVE-2024-9681 | LOW3.9 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-86414 | LOW3.9 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | — | Post-Exploit |
| CVE-2026-92390 | LOW3.9 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | — | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | curl-minimal 7.76.1-40.el9_8.5 fixed in 7.76.1-40.el9_8.7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9546 | LOW3.82 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-40467 | LOW3.82 | gawk 5.1.0-6.el9 fixed in 5.1.0-6.el9_8.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-40553 | LOW3.82 | gawk 5.1.0-6.el9 fixed in 5.1.0-6.el9_8.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW3.82 | gzip 1.12-1.el9 fixed in 1.12-2.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl-minimal 7.76.1-40.el9_8.5 fixed in 7.76.1-40.el9_8.7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9546 | LOW3.82 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-14456 | LOW3.82 | openssl 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-63072 | LOW3.82 | openssl 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-28388 | LOW3.82 | openssl 1:3.5.5-6.el9_8 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-28389 | LOW3.82 | openssl 1:3.5.5-6.el9_8 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-54874 | LOW3.82 | openssl 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63074 | LOW3.82 | openssl 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63075 | LOW3.82 | openssl 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-3644 | LOW3.82 | python3 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW3.82 | python3 3.9.25-7.el9_8.3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW3.82 | python3 3.9.25-7.el9_8.3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3644 | LOW3.82 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW3.82 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW3.82 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-57585 | LOW3.82 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-97689 | LOW3.82 | python3-urllib3 1.26.5-8.el9_8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59871 | LOW3.82 | tar 2:1.34-11.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-26269 | LOW3.82 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-56131 | LOW3.82 | expat 2.5.0-6.el9_8.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-84782 | LOW3.77 | openssl 1:3.5.5-6.el9_8 fixed in 1:3.5.8-2.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19553 | LOW3.77 | python3 3.9.25-7.el9_8.3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19553 | LOW3.77 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-29040 | LOW3.74 | tpm2-tss 3.2.3-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-9080 | LOW3.72 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW3.72 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-4156 | LOW3.62 | gawk 5.1.0-6.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-103242 | LOW3.62 | python3-rpm 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-95520 | LOW3.62 | python3-rpm 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-103242 | LOW3.62 | rpm 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-95520 | LOW3.62 | rpm 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2005-2541 | LOW3.6 | tar 2:1.34-11.el9 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-13732 | LOW3.57 | gdb-gdbserver 16.3-3.el9 fixed in 16.3-3.1.el9_8 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-78367 | LOW3.57 | python3-rpm 4.16.1.3-40.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78367 | LOW3.57 | rpm 4.16.1.3-40.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW3.57 | util-linux 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW3.57 | util-linux-core 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-1484 | LOW3.57 | glib2 2.68.4-19.el9_8.9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | LOW3.57 | glibc 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | glibc 2.34-275.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | LOW3.57 | glibc-common 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | glibc-common 2.34-275.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-11053 | LOW3.54 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | gdb-gdbserver 16.3-3.el9 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2024-11053 | LOW3.54 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2024-41996 | LOW3.54 | openssl 1:3.5.5-6.el9_8 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63073 | LOW3.54 | openssl 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-13034 | LOW3.47 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90803 | LOW3.47 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-13034 | LOW3.47 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-3572 | LOW3.42 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2024-25260 | LOW3.4 | elfutils-libelf 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-25260 | LOW3.4 | elfutils-libs 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-90828 | LOW3.37 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90829 | LOW3.37 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90831 | LOW3.37 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-28419 | LOW3.37 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-1170 | LOW3.37 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-1175 | LOW3.37 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | curl-minimal 7.76.1-40.el9_8.5 fixed in 7.76.1-40.el9_8.8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-19931 | LOW3.31 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl-minimal 7.76.1-40.el9_8.5 fixed in 7.76.1-40.el9_8.8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | libcurl-minimal 7.76.1-40.el9_8.5 fixed in 7.76.1-40.el9_8.8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-19931 | LOW3.31 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl-minimal 7.76.1-40.el9_8.5 fixed in 7.76.1-40.el9_8.8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW3.31 | python3 3.9.25-7.el9_8.3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7774 | LOW3.31 | python3 3.9.25-7.el9_8.3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW3.31 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7774 | LOW3.31 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-13346 | LOW3.31 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-33056 | LOW3.31 | tar 2:1.34-11.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-15028 | LOW3.31 | libarchive 3.5.3-11.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-1674 | LOW3.3 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2208 | LOW3.3 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-3278 | LOW3.3 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-12345 | LOW3.21 | python3 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-12345 | LOW3.21 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5958 | LOW3.21 | sed 4.8-10.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-86409 | LOW3.18 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | — | Post-Exploit |
| CVE-2026-86409 | LOW3.18 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | — | Post-Exploit |
| CVE-2026-41080 | LOW3.15 | expat 2.5.0-6.el9_8.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-3360 | LOW3.15 | glib2 2.68.4-19.el9_8.9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-7039 | LOW3.15 | glib2 2.68.4-19.el9_8.9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0988 | LOW3.15 | glib2 2.68.4-19.el9_8.9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.15 | glibc 2.34-275.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.15 | glibc-common 2.34-275.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0989 | LOW3.15 | libxml2 2.9.13-14.el9_8.2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.15 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35191 | LOW3.15 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.15 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56391 | LOW3.11 | coreutils-single 8.32-41.el9_8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW3.11 | coreutils-single 8.32-41.el9_8 fixed in 8.32-41.el9_8.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90804 | LOW3.11 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.11 | python3 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.11 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-50181 | LOW3.11 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-50182 | LOW3.11 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-57451 | LOW3.11 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-9232 | LOW3.1 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5713 | LOW3.06 | python3 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5713 | LOW3.06 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-17591 | LOW3.06 | libarchive 3.5.3-11.el9_8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54872 | LOW3.01 | openssl 1:3.5.5-6.el9_8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-72897 | LOW3.01 | openssl 1:3.5.5-6.el9_8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-75805 | LOW3.01 | openssl 1:3.5.5-6.el9_8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-77696 | LOW3.01 | openssl 1:3.5.5-6.el9_8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42765 | LOW3.01 | openssl 1:3.5.5-6.el9_8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-32284 | LOW3.01 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2021-3968 | LOW2.88 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-15003 | LOW2.86 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-84837 | LOW2.81 | rpm-build-libs 4.16.1.3-40.el9 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-84837 | LOW2.81 | rpm-libs 4.16.1.3-40.el9 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-84837 | LOW2.81 | rpm-plugin-systemd-inhibit 4.16.1.3-40.el9 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-84837 | LOW2.81 | rpm-sign-libs 4.16.1.3-40.el9 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3927 | LOW2.81 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3973 | LOW2.81 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3974 | LOW2.81 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2021-4136 | LOW2.81 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2021-4173 | LOW2.81 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2021-4187 | LOW2.81 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1616 | LOW2.81 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-90830 | LOW2.8 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-47007 | LOW2.8 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47010 | LOW2.8 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47011 | LOW2.8 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-24883 | LOW2.8 | gnupg2 2.3.3-5.el9_7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-13837 | LOW2.8 | python3 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-0864 | LOW2.8 | python3 3.9.25-7.el9_8.3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-42308 | LOW2.8 | python3 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-13837 | LOW2.8 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-0864 | LOW2.8 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-42308 | LOW2.8 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-25645 | LOW2.8 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-44605 | LOW2.8 | python3-rpm 4.16.1.3-40.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-44605 | LOW2.8 | rpm 4.16.1.3-40.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53655 | LOW2.8 | tar 2:1.34-11.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 2:1.34-11.el9 fixed in 2:1.34-13.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-28418 | LOW2.8 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45130 | LOW2.8 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-73070 | LOW2.8 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-1725 | LOW2.8 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2874 | LOW2.8 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2923 | LOW2.8 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2980 | LOW2.8 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-3153 | LOW2.8 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-4293 | LOW2.8 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-1264 | LOW2.8 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-2609 | LOW2.8 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-46246 | LOW2.8 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-5441 | LOW2.8 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-45306 | LOW2.8 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-22134 | LOW2.8 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-24014 | LOW2.8 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41990 | LOW2.8 | libgcrypt 1.10.0-13.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | sqlite-libs 3.34.1-10.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-41409 | LOW2.7 | pcre2 10.40-6.el9 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42772 | LOW2.7 | openssl 1:3.5.5-6.el9_8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54873 | LOW2.7 | openssl 1:3.5.5-6.el9_8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-75804 | LOW2.7 | openssl 1:3.5.5-6.el9_8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-75806 | LOW2.7 | openssl 1:3.5.5-6.el9_8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-84784 | LOW2.7 | openssl 1:3.5.5-6.el9_8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW2.7 | python3 3.9.25-7.el9_8.3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-19672 | LOW2.7 | python3 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW2.7 | python3 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4360 | LOW2.7 | python3 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW2.7 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-19672 | LOW2.7 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW2.7 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4360 | LOW2.7 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-47081 | LOW2.7 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-45409 | LOW2.7 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-59875 | LOW2.7 | tar 2:1.34-11.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux-core 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-44656 | LOW2.7 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2024-41957 | LOW2.7 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42307 | LOW2.64 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63387 | LOW2.63 | libevent 2.1.12-8.el9_4 fixed in 2.1.13-1.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11731 | LOW2.63 | libxslt 1.1.34-14.el9_8.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-74860 | LOW2.6 | libxml2 2.9.13-14.el9_8.2 fixed in 2.9.13-14.el9_8.5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-4516 | LOW2.6 | python3 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-4516 | LOW2.6 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63388 | LOW2.57 | libevent 2.1.12-8.el9_4 fixed in 2.1.13-1.el9_8 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-90802 | LOW2.55 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-0992 | LOW2.46 | libxml2 2.9.13-14.el9_8.2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | LOW2.45 | libblkid 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.45 | libfdisk 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.45 | libmount 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | LOW2.45 | python3 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.45 | python3 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | LOW2.45 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.45 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gnupg2 2.3.3-5.el9_7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gnupg2 2.3.3-5.el9_7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.12-1.el9 fixed in 1.12-2.el9_8 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-54875 | LOW2.4 | openssl 1:3.5.5-6.el9_8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-13176 | LOW2.4 | openssl 1:3.5.5-6.el9_8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-64118 | LOW2.4 | tar 2:1.34-11.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux-core 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57452 | LOW2.4 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-48706 | LOW2.4 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-43374 | LOW2.4 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-47814 | LOW2.4 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1485 | LOW2.38 | glib2 2.68.4-19.el9_8.9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | LOW2.29 | python3 3.9.25-7.el9_8.3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW2.29 | python3 3.9.25-7.el9_8.3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-11468 | LOW2.29 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW2.29 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-43802 | LOW2.29 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-18477 | LOW2.24 | tar 2:1.34-11.el9 fixed in 2:1.34-13.el9_8 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW2.24 | tar 2:1.34-11.el9 fixed in 2:1.34-13.el9_8 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-29768 | LOW2.24 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-87864 | LOW2.22 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | — | Post-Exploit |
| CVE-2026-92389 | LOW2.22 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | — | Post-Exploit |
| CVE-2026-92391 | LOW2.22 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | — | Post-Exploit |
| CVE-2026-87864 | LOW2.22 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | — | Post-Exploit |
| CVE-2026-92389 | LOW2.22 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | — | Post-Exploit |
| CVE-2026-92391 | LOW2.22 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | — | Post-Exploit |
| CVE-2023-48231 | LOW2.19 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48232 | LOW2.19 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48233 | LOW2.19 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2023-48234 | LOW2.19 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2023-48235 | LOW2.19 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2023-48236 | LOW2.19 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48237 | LOW2.19 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2023-45803 | LOW2.14 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-41965 | LOW2.14 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-26603 | LOW2.14 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-24515 | LOW2.12 | expat 2.5.0-6.el9_8.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18739 | LOW2.12 | popt 1.18-8.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18743 | LOW2.12 | popt 1.18-8.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94266 | LOW1.98 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | — | Post-Exploit |
| CVE-2026-94266 | LOW1.98 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | — | Post-Exploit |
| CVE-2026-18924 | LOW1.89 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.89 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW1.89 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.89 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-35189 | LOW1.89 | openssl 1:3.5.5-6.el9_8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-35191 | LOW1.89 | openssl 1:3.5.5-6.el9_8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-75803 | LOW1.89 | openssl 1:3.5.5-6.el9_8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18839 | LOW1.87 | popt 1.18-8.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-9232 | LOW1.86 | openssl 1:3.5.5-6.el9_8 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-105712 | LOW1.84 | gnupg2 2.3.3-5.el9_7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gnupg2 2.3.3-5.el9_7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW1.68 | python3 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.68 | python3 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3 3.9.25-7.el9_8.3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW1.68 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.68 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-39804 | LOW1.68 | tar 2:1.34-11.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-82209 | LOW1.58 | curl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-82209 | LOW1.58 | libcurl-minimal 7.76.1-40.el9_8.5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-1795 | LOW1.58 | python3 3.9.25-7.el9_8.3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1795 | LOW1.58 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gnupg2 2.3.3-5.el9_7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | gdb-gdbserver 16.3-3.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18503 | LOW1.43 | python3 3.9.25-7.el9_8.3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18503 | LOW1.43 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-28422 | LOW1.12 | vim-minimal 2:8.2.2637-26.el9_8.13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-86145 | NONE0 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89161 | NONE0 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-103111 | NONE0 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-41409 | NONE0 | pcre2-syntax 10.40-6.el9 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-89157 | NONE0 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-86805 | NONE0 | glibc-langpack-en 2.34-275.el9_8 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-95818 | NONE0 | glibc-langpack-en 2.34-275.el9_8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86805 | NONE0 | glibc-minimal-langpack 2.34-275.el9_8 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-95818 | NONE0 | glibc-minimal-langpack 2.34-275.el9_8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22185 | NONE0 | openldap-devel 2.6.8-4.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4105 | NONE0 | systemd 252-67.el9_8.4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4105 | NONE0 | systemd-pam 252-67.el9_8.4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4105 | NONE0 | systemd-rpm-macros 252-67.el9_8.4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.2-12.20210508.el9 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-libs 6.2-12.20210508.el9 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-89158 | NONE0 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89160 | NONE0 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-12610 | NONE0 | pam 1.5.1-28.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-54371 | NONE0 | attr 2.5.1-3.el9 fixed in 2.6.0-1.el9_8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6791 | NONE0 | glibc-langpack-en 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-77117 | NONE0 | glibc-langpack-en 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80489 | NONE0 | glibc-langpack-en 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6791 | NONE0 | glibc-minimal-langpack 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-77117 | NONE0 | glibc-minimal-langpack 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80489 | NONE0 | glibc-minimal-langpack 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89156 | NONE0 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-16730 | NONE0 | dbus-broker 28-7.el9 fixed in 28-9.el9_8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1371 | NONE0 | elfutils-default-yama-scope 0.194-1.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1377 | NONE0 | elfutils-default-yama-scope 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6368 | NONE0 | glibc-langpack-en 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6368 | NONE0 | glibc-minimal-langpack 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-24056 | NONE0 | pkgconf 1.7.3-10.el9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-24056 | NONE0 | pkgconf-m4 1.7.3-10.el9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-24056 | NONE0 | pkgconf-pkg-config 1.7.3-10.el9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-15059 | NONE0 | systemd 252-67.el9_8.4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-15059 | NONE0 | systemd-pam 252-67.el9_8.4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-15059 | NONE0 | systemd-rpm-macros 252-67.el9_8.4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-8674 | NONE0 | glibc-langpack-en 2.34-275.el9_8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8674 | NONE0 | glibc-minimal-langpack 2.34-275.el9_8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-18374 | NONE0 | glibc-langpack-en 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-18374 | NONE0 | glibc-minimal-langpack 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | pam 1.5.1-28.el9 fixed in 1.5.1-28.el9_8.1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-1376 | NONE0 | elfutils-default-yama-scope 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-19542 | NONE0 | glibc-langpack-en 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89092 | NONE0 | glibc-langpack-en 2.34-275.el9_8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-19542 | NONE0 | glibc-minimal-langpack 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89092 | NONE0 | glibc-minimal-langpack 2.34-275.el9_8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-25260 | NONE0 | elfutils-default-yama-scope 0.194-1.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97399 | NONE0 | glibc-langpack-en 2.34-275.el9_8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97399 | NONE0 | glibc-minimal-langpack 2.34-275.el9_8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107161 | NONE0 | cyrus-sasl 2.1.27-22.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107161 | NONE0 | cyrus-sasl-devel 2.1.27-22.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107161 | NONE0 | cyrus-sasl-lib 2.1.27-22.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-88647 | NONE0 | gnutls 3.8.10-8.el9_8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-67693 | NONE0 | gnutls 3.8.10-8.el9_8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-88648 | NONE0 | gnutls 3.8.10-8.el9_8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
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.