Last scanned:
AI verdict failed due to an error.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2005-2541 | MEDIUM6 | tar 2:1.34-9.el9_7 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-31789 | MEDIUM5 | openssl 1:3.5.1-7.el9_7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45447 | MEDIUM4.86 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45445 | MEDIUM4.64 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-28390 | MEDIUM4.5 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-3.el9_8 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34183 | MEDIUM4.5 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28388 | MEDIUM4.5 | openssl 1:3.5.1-7.el9_7 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28389 | MEDIUM4.5 | openssl 1:3.5.1-7.el9_7 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28387 | MEDIUM4.13 | openssl 1:3.5.1-7.el9_7 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-59871 | LOW3.82 | tar 2:1.34-9.el9_7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW3.77 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-44604 | LOW3.57 | rpm 4.16.1.3-39.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-31790 | LOW3.54 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-2.el9_8 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42764 | LOW3.54 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-41996 | LOW3.54 | openssl 1:3.5.1-7.el9_7 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-2673 | LOW3.31 | openssl 1:3.5.1-7.el9_7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-33056 | LOW3.31 | tar 2:1.34-9.el9_7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-44605 | LOW3.3 | rpm 4.16.1.3-39.el9 No fix yet | — | Post-Exploit |
| CVE-2026-34181 | LOW3.21 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42768 | LOW3.21 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42769 | LOW3.01 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW3.01 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.01 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-34180 | LOW3 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-24883 | LOW2.8 | gnupg2 2.3.3-5.el9_7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW2.8 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-53655 | LOW2.8 | tar 2:1.34-9.el9_7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 2:1.34-9.el9_7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42766 | LOW2.7 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-42767 | LOW2.7 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-59875 | LOW2.7 | tar 2:1.34-9.el9_7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux 2.37.4-21.el9_7 No fix yet | 0.1% 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 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-13176 | LOW2.4 | openssl 1:3.5.1-7.el9_7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-64118 | LOW2.4 | tar 2:1.34-9.el9_7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.37.4-21.el9_7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45446 | LOW1.89 | openssl 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-9232 | LOW1.86 | openssl 1:3.5.1-7.el9_7 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gnupg2 2.3.3-5.el9_7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-39804 | LOW1.68 | tar 2:1.34-9.el9_7 No fix yet | 0.3% 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-14087 | NONE0 | glib2 2.68.4-18.el9_7.1 fixed in 2.68.4-19.el9_8.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42010 | NONE0 | gnutls 3.8.3-9.el9 fixed in 3.8.10-4.el9_8 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-6653 | NONE0 | libxml2 2.9.13-14.el9_7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31789 | NONE0 | openssl-libs 1:3.5.1-7.el9_7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-58016 | NONE0 | glib2 2.68.4-18.el9_7.1 fixed in 2.68.4-19.el9_8.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-33845 | NONE0 | gnutls 3.8.3-9.el9 fixed in 3.8.10-4.el9_8 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-45445 | NONE0 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-47162 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | glib2 2.68.4-18.el9_7.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | glib2 2.68.4-18.el9_7.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | glib2 2.68.4-18.el9_7.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | glib2 2.68.4-18.el9_7.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42013 | NONE0 | gnutls 3.8.3-9.el9 fixed in 3.8.10-4.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5260 | NONE0 | gnutls 3.8.3-9.el9 fixed in 3.8.10-4.el9_8 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-34982 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 fixed in 2:8.2.2637-26.el9_8.4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52859 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8286 | NONE0 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8925 | NONE0 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-15079 | NONE0 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0861 | NONE0 | glibc 2.34-231.el9_7.2 fixed in 2.34-231.el9_7.10 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8286 | NONE0 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8925 | NONE0 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-15079 | NONE0 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45447 | NONE0 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-28387 | NONE0 | openssl-libs 1:3.5.1-7.el9_7 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-6100 | NONE0 | python3 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6100 | NONE0 | python3-libs 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-3968 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-11082 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-48864 | NONE0 | libsolv 0.7.24-3.el9 fixed in 0.7.24-6.el9_8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11979 | NONE0 | libxml2 2.9.13-14.el9_7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-29111 | NONE0 | systemd 252-55.el9_7.7 fixed in 252-67.el9_8.2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-29111 | NONE0 | systemd-libs 252-55.el9_7.7 fixed in 252-67.el9_8.2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-29111 | NONE0 | systemd-pam 252-55.el9_7.7 fixed in 252-67.el9_8.2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-29111 | NONE0 | systemd-rpm-macros 252-55.el9_7.7 fixed in 252-67.el9_8.2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55895 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57456 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-28417 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 fixed in 2:8.2.2637-23.el9_7.2 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-28421 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 fixed in 2:8.2.2637-23.el9_7.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-39881 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-55693 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-57455 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-59856 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-59858 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2021-3927 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2021-3928 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-3973 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-3974 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-4136 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2021-4173 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2021-4187 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-0351 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-1616 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2022-1619 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-1720 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-2042 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-2124 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-2125 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-2126 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-2129 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-2175 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-2182 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-2183 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-2206 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-2207 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-2210 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-2257 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-2284 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-2285 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-2286 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-2304 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-2343 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-2344 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-2345 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-2522 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-2817 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-2819 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-2845 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-2849 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-2862 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2022-2889 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-2946 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-2982 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-3016 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-3037 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-3099 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-3134 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-3234 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-3235 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-3256 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-3296 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-3297 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-3324 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-3352 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-4141 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-4292 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-0049 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-0051 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-0054 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-0288 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-0433 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-0512 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-1127 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-2610 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-4734 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-4735 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-4738 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-4751 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-4781 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-5535 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-22667 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1215 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-11352 | NONE0 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-11586 | NONE0 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5773 | NONE0 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6276 | NONE0 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45186 | NONE0 | expat 2.5.0-5.el9_7.1 fixed in 2.5.0-6.el9_8.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-66864 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58011 | NONE0 | glib2 2.68.4-18.el9_7.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | glib2 2.68.4-18.el9_7.1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-32636 | NONE0 | glib2 2.68.4-18.el9_7.1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-33846 | NONE0 | gnutls 3.8.3-9.el9 fixed in 3.8.10-4.el9_8 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-42009 | NONE0 | gnutls 3.8.3-9.el9 fixed in 3.8.10-4.el9_8 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-40355 | NONE0 | krb5-libs 1.21.1-8.el9_6 fixed in 1.21.1-10.el9_8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-40356 | NONE0 | krb5-libs 1.21.1-8.el9_6 fixed in 1.21.1-10.el9_8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4111 | NONE0 | libarchive 3.5.3-6.el9_6 fixed in 3.5.3-7.el9_7 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-4424 | NONE0 | libarchive 3.5.3-6.el9_6 fixed in 3.5.3-9.el9_7 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-14164 | NONE0 | libarchive 3.5.3-6.el9_6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5121 | NONE0 | libarchive 3.5.3-6.el9_6 fixed in 3.5.3-9.el9_7 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-11352 | NONE0 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-11586 | NONE0 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5773 | NONE0 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6276 | NONE0 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-41989 | NONE0 | libgcrypt 1.10.0-11.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-27135 | NONE0 | libnghttp2 1.43.0-6.el9 fixed in 1.43.0-6.el9_7.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-6732 | NONE0 | libxml2 2.9.13-14.el9_7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-27113 | NONE0 | libxml2 2.9.13-14.el9_7 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-28390 | NONE0 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-3.el9_8 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-34183 | NONE0 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-28388 | NONE0 | openssl-libs 1:3.5.1-7.el9_7 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-28389 | NONE0 | openssl-libs 1:3.5.1-7.el9_7 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-2100 | NONE0 | p11-kit 0.25.3-3.el9_5 fixed in 0.26.2-1.el9 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-2100 | NONE0 | p11-kit-trust 0.25.3-3.el9_5 fixed in 0.26.2-1.el9 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-41409 | NONE0 | pcre2 10.40-6.el9 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-41409 | NONE0 | pcre2-syntax 10.40-6.el9 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-15308 | NONE0 | python3 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-3644 | NONE0 | python3 3.9.25-3.el9_7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4224 | NONE0 | python3 3.9.25-3.el9_7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-7210 | NONE0 | python3 3.9.25-3.el9_7 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-15308 | NONE0 | python3-libs 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-3644 | NONE0 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4224 | NONE0 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-7210 | NONE0 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-44432 | NONE0 | python3-urllib3 1.26.5-6.el9_7.1 fixed in 1.26.5-8.el9_8 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2022-1620 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-3705 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-5344 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-26269 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-9547 | NONE0 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-3833 | NONE0 | gnutls 3.8.3-9.el9 fixed in 3.8.10-4.el9_8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42011 | NONE0 | gnutls 3.8.3-9.el9 fixed in 3.8.10-4.el9_8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-9547 | NONE0 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34182 | NONE0 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-33412 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 fixed in 2:8.2.2637-23.el9_7.2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-25749 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 fixed in 2:8.2.2637-23.el9_7.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-41411 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 fixed in 2:8.2.2637-26.el9_8.6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-54369 | NONE0 | acl 2.3.1-4.el9 fixed in 2.4.0-1.el9_8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-4156 | NONE0 | gawk 5.1.0-6.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-16118 | NONE0 | glib2 2.68.4-18.el9_7.1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-42012 | NONE0 | gnutls 3.8.3-9.el9 fixed in 3.8.10-4.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-54369 | NONE0 | libacl 2.3.1-4.el9 fixed in 2.4.0-1.el9_8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4786 | NONE0 | python3 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-15366 | NONE0 | python3 3.9.25-3.el9_7 fixed in 3.9.25-3.el9_7.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15367 | NONE0 | python3 3.9.25-3.el9_7 fixed in 3.9.25-3.el9_7.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-1299 | NONE0 | python3 3.9.25-3.el9_7 fixed in 3.9.25-3.el9_7.1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4786 | NONE0 | python3-libs 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-15366 | NONE0 | python3-libs 3.9.25-3.el9_7 fixed in 3.9.25-3.el9_7.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15367 | NONE0 | python3-libs 3.9.25-3.el9_7 fixed in 3.9.25-3.el9_7.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-1299 | NONE0 | python3-libs 3.9.25-3.el9_7 fixed in 3.9.25-3.el9_7.1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-4166 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-2287 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-4878 | NONE0 | libcap 2.48-10.el9 fixed in 2.48-10.el9_8.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-44604 | NONE0 | python3-rpm 4.16.1.3-39.el9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-44604 | NONE0 | rpm-build-libs 4.16.1.3-39.el9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-44604 | NONE0 | rpm-libs 4.16.1.3-39.el9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-44604 | NONE0 | rpm-plugin-systemd-inhibit 4.16.1.3-39.el9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-44604 | NONE0 | rpm-sign-libs 4.16.1.3-39.el9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46483 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56132 | NONE0 | expat 2.5.0-5.el9_7.1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56403 | NONE0 | expat 2.5.0-5.el9_7.1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56405 | NONE0 | expat 2.5.0-5.el9_7.1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56406 | NONE0 | expat 2.5.0-5.el9_7.1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-13034 | NONE0 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-1965 | NONE0 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-13034 | NONE0 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-1965 | NONE0 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-22185 | NONE0 | openldap 2.6.8-4.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22185 | NONE0 | openldap-devel 2.6.8-4.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4105 | NONE0 | systemd 252-55.el9_7.7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4105 | NONE0 | systemd-libs 252-55.el9_7.7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4105 | NONE0 | systemd-pam 252-55.el9_7.7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4105 | NONE0 | systemd-rpm-macros 252-55.el9_7.7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-42014 | NONE0 | gnutls 3.8.3-9.el9 fixed in 3.8.10-4.el9_8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-5915 | NONE0 | libarchive 3.5.3-6.el9_6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5918 | NONE0 | libarchive 3.5.3-6.el9_6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-28419 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0213 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-1170 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-1175 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-11856 | NONE0 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-3784 | NONE0 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-5545 | NONE0 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6429 | NONE0 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8924 | NONE0 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-7264 | NONE0 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 17.3% High Exploitation Risk | Not Applicable |
| CVE-2024-9681 | NONE0 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-14524 | NONE0 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-14512 | NONE0 | glib2 2.68.4-18.el9_7.1 fixed in 2.68.4-19.el9_8.1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-4437 | NONE0 | glibc 2.34-231.el9_7.2 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | glibc 2.34-231.el9_7.2 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4437 | NONE0 | glibc-common 2.34-231.el9_7.2 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | glibc-common 2.34-231.el9_7.2 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4437 | NONE0 | glibc-langpack-en 2.34-231.el9_7.2 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | glibc-langpack-en 2.34-231.el9_7.2 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4437 | NONE0 | glibc-minimal-langpack 2.34-231.el9_7.2 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | glibc-minimal-langpack 2.34-231.el9_7.2 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4426 | NONE0 | libarchive 3.5.3-6.el9_6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11856 | NONE0 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-3784 | NONE0 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-5545 | NONE0 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6429 | NONE0 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8924 | NONE0 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-7264 | NONE0 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 17.3% High Exploitation Risk | Not Applicable |
| CVE-2024-9681 | NONE0 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-14524 | NONE0 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-9149 | NONE0 | libsolv 0.7.24-3.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-9150 | NONE0 | libsolv 0.7.24-3.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45322 | NONE0 | libxml2 2.9.13-14.el9_7 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.2-12.20210508.el9 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-libs 6.2-12.20210508.el9 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-2673 | NONE0 | openssl-fips-provider 3.0.7-8.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-2673 | NONE0 | openssl-fips-provider-so 3.0.7-8.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-2673 | NONE0 | openssl-libs 1:3.5.1-7.el9_7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-11972 | NONE0 | python3 3.9.25-3.el9_7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-11972 | NONE0 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12610 | NONE0 | pam 1.5.1-26.el9_6 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-54370 | NONE0 | acl 2.3.1-4.el9 fixed in 2.4.0-1.el9_8 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-54371 | NONE0 | attr 2.5.1-3.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-54370 | NONE0 | libacl 2.3.1-4.el9 fixed in 2.4.0-1.el9_8 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-54371 | NONE0 | libattr 2.5.1-3.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-34181 | NONE0 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42768 | NONE0 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-5958 | NONE0 | sed 4.8-9.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-1757 | NONE0 | libxml2 2.9.13-14.el9_7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-13757 | NONE0 | p11-kit 0.25.3-3.el9_5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-13757 | NONE0 | p11-kit-trust 0.25.3-3.el9_5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56391 | NONE0 | coreutils-single 8.32-39.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6019 | NONE0 | python3 3.9.25-3.el9_7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6019 | NONE0 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-50181 | NONE0 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-50182 | NONE0 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-57451 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-5713 | NONE0 | python3 3.9.25-3.el9_7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-5713 | NONE0 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-11053 | NONE0 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-50219 | NONE0 | expat 2.5.0-5.el9_7.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56412 | NONE0 | expat 2.5.0-5.el9_7.1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1153 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-5435 | NONE0 | glibc 2.34-231.el9_7.2 fixed in 2.34-274.el9_8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-15281 | NONE0 | glibc 2.34-231.el9_7.2 fixed in 2.34-231.el9_7.10 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | glibc-common 2.34-231.el9_7.2 fixed in 2.34-274.el9_8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | glibc-langpack-en 2.34-231.el9_7.2 fixed in 2.34-274.el9_8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | glibc-minimal-langpack 2.34-231.el9_7.2 fixed in 2.34-274.el9_8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-11053 | NONE0 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2025-13151 | NONE0 | libtasn1 4.16.0-9.el9 fixed in 4.16.0-10.el9_8 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-0990 | NONE0 | libxml2 2.9.13-14.el9_7 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-31790 | NONE0 | openssl-fips-provider 3.0.7-8.el9 fixed in 3.0.7-11.el9_8 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-31790 | NONE0 | openssl-fips-provider-so 3.0.7-8.el9 fixed in 3.0.7-11.el9_8 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-31790 | NONE0 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-2.el9_8 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-42764 | NONE0 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-41996 | NONE0 | openssl-libs 1:3.5.1-7.el9_7 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-42769 | NONE0 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42770 | NONE0 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-9076 | NONE0 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32284 | NONE0 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-3783 | NONE0 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-3783 | NONE0 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-3572 | NONE0 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2026-15003 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-5916 | NONE0 | libarchive 3.5.3-6.el9_6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-16730 | NONE0 | dbus-broker 28-7.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1371 | NONE0 | elfutils-default-yama-scope 0.193-1.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1377 | NONE0 | elfutils-default-yama-scope 0.193-1.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-1371 | NONE0 | elfutils-libelf 0.193-1.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1377 | NONE0 | elfutils-libelf 0.193-1.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-1371 | NONE0 | elfutils-libs 0.193-1.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1377 | NONE0 | elfutils-libs 0.193-1.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-32776 | NONE0 | expat 2.5.0-5.el9_7.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-32777 | NONE0 | expat 2.5.0-5.el9_7.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-32778 | NONE0 | expat 2.5.0-5.el9_7.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66382 | NONE0 | expat 2.5.0-5.el9_7.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11081 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6844 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-47007 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-47010 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-47011 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-60753 | NONE0 | libarchive 3.5.3-6.el9_6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-5745 | NONE0 | libarchive 3.5.3-6.el9_6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1632 | NONE0 | libarchive 3.5.3-6.el9_6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-46195 | NONE0 | libgcc 11.5.0-11.el9 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-27943 | NONE0 | libgcc 11.5.0-11.el9 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2021-46195 | NONE0 | libgomp 11.5.0-11.el9 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-27943 | NONE0 | libgomp 11.5.0-11.el9 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-24056 | NONE0 | libpkgconf 1.7.3-10.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-46195 | NONE0 | libstdc++ 11.5.0-11.el9 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-27943 | NONE0 | libstdc++ 11.5.0-11.el9 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-34459 | NONE0 | libxml2 2.9.13-14.el9_7 fixed in 2.9.13-14.el9_8.1 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-7383 | NONE0 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-24056 | NONE0 | pkgconf 1.7.3-10.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-24056 | NONE0 | pkgconf-m4 1.7.3-10.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-24056 | NONE0 | pkgconf-pkg-config 1.7.3-10.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-13837 | NONE0 | python3 3.9.25-3.el9_7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42308 | NONE0 | python3 3.9.25-3.el9_7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-13837 | NONE0 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42308 | NONE0 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-25645 | NONE0 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-44605 | NONE0 | python3-rpm 4.16.1.3-39.el9 No fix yet | — | Not Applicable |
| CVE-2026-44605 | NONE0 | rpm-build-libs 4.16.1.3-39.el9 No fix yet | — | Not Applicable |
| CVE-2026-44605 | NONE0 | rpm-libs 4.16.1.3-39.el9 No fix yet | — | Not Applicable |
| CVE-2026-44605 | NONE0 | rpm-plugin-systemd-inhibit 4.16.1.3-39.el9 No fix yet | — | Not Applicable |
| CVE-2026-44605 | NONE0 | rpm-sign-libs 4.16.1.3-39.el9 No fix yet | — | Not Applicable |
| CVE-2024-0232 | NONE0 | sqlite-libs 3.34.1-9.el9_7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-28418 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45130 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55892 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-59857 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-1674 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-1725 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-2208 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-2874 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-2923 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-2980 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2022-3153 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-3278 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-4293 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-1264 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-2609 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-46246 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-5441 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-45306 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22134 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-24014 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-27171 | NONE0 | zlib 1.2.11-40.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-1489 | NONE0 | glib2 2.68.4-18.el9_7.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58055 | NONE0 | libnghttp2 1.43.0-6.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4873 | NONE0 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6253 | NONE0 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-7168 | NONE0 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-15588 | NONE0 | glib2 2.68.4-18.el9_7.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-0915 | NONE0 | glibc 2.34-231.el9_7.2 fixed in 2.34-231.el9_7.10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4046 | NONE0 | glibc 2.34-231.el9_7.2 fixed in 2.34-270.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4046 | NONE0 | glibc-common 2.34-231.el9_7.2 fixed in 2.34-270.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4046 | NONE0 | glibc-langpack-en 2.34-231.el9_7.2 fixed in 2.34-270.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4046 | NONE0 | glibc-minimal-langpack 2.34-231.el9_7.2 fixed in 2.34-270.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-14831 | NONE0 | gnutls 3.8.3-9.el9 fixed in 3.8.3-10.el9_7 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42015 | NONE0 | gnutls 3.8.3-9.el9 fixed in 3.8.10-4.el9_8 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-30571 | NONE0 | libarchive 3.5.3-6.el9_6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libblkid 2.37.4-21.el9_7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4873 | NONE0 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6253 | NONE0 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-7168 | NONE0 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libfdisk 2.37.4-21.el9_7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libmount 2.37.4-21.el9_7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libsmartcols 2.37.4-21.el9_7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libuuid 2.37.4-21.el9_7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-42766 | NONE0 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-42767 | NONE0 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-12781 | NONE0 | python3 3.9.25-3.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-3276 | NONE0 | python3 3.9.25-3.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45409 | NONE0 | python3-idna 2.10-7.el9_4.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-12781 | NONE0 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-3276 | NONE0 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45409 | NONE0 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-44431 | NONE0 | python3-urllib3 1.26.5-6.el9_7.1 fixed in 1.26.5-8.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | util-linux-core 2.37.4-21.el9_7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-44656 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-41957 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-34743 | NONE0 | xz-libs 5.2.5-8.el9_0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-4516 | NONE0 | python3 3.9.25-3.el9_7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-4516 | NONE0 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42250 | NONE0 | bzip2-libs 1.0.8-10.el9_5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-57360 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | glibc 2.34-231.el9_7.2 fixed in 2.34-272.el9_8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | glibc 2.34-231.el9_7.2 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | glibc-common 2.34-231.el9_7.2 fixed in 2.34-272.el9_8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | glibc-common 2.34-231.el9_7.2 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | glibc-langpack-en 2.34-231.el9_7.2 fixed in 2.34-272.el9_8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | glibc-langpack-en 2.34-231.el9_7.2 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | glibc-minimal-langpack 2.34-231.el9_7.2 fixed in 2.34-272.el9_8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | glibc-minimal-langpack 2.34-231.el9_7.2 fixed in 2.34-274.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-11850 | NONE0 | krb5-libs 1.21.1-8.el9_6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-5917 | NONE0 | libarchive 3.5.3-6.el9_6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-34180 | NONE0 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-14017 | NONE0 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-8926 | NONE0 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-14017 | NONE0 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-8926 | NONE0 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | pam 1.5.1-26.el9_6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-15282 | NONE0 | python3 3.9.25-3.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0672 | NONE0 | python3 3.9.25-3.el9_7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15282 | NONE0 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0672 | NONE0 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15224 | NONE0 | curl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-1376 | NONE0 | elfutils-default-yama-scope 0.193-1.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-1376 | NONE0 | elfutils-libelf 0.193-1.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-1376 | NONE0 | elfutils-libs 0.193-1.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libblkid 2.37.4-21.el9_7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-15224 | NONE0 | libcurl-minimal 7.76.1-35.el9_7.3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libfdisk 2.37.4-21.el9_7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libmount 2.37.4-21.el9_7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libsmartcols 2.37.4-21.el9_7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libuuid 2.37.4-21.el9_7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-13176 | NONE0 | openssl-libs 1:3.5.1-7.el9_7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | util-linux-core 2.37.4-21.el9_7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-57452 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-48706 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-43374 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47814 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11468 | NONE0 | python3 3.9.25-3.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0865 | NONE0 | python3 3.9.25-3.el9_7 fixed in 3.9.25-5.el9_8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-1502 | NONE0 | python3 3.9.25-3.el9_7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-11468 | NONE0 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0865 | NONE0 | python3-libs 3.9.25-3.el9_7 fixed in 3.9.25-5.el9_8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-1502 | NONE0 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-43802 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-5278 | NONE0 | coreutils-single 8.32-39.el9 fixed in 8.32-41.el9_8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56392 | NONE0 | coreutils-single 8.32-39.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-29040 | NONE0 | tpm2-tss 3.2.3-1.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-29768 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-28420 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42307 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-48231 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-48232 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-48233 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-48234 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-48235 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-48236 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-48237 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-1484 | NONE0 | glib2 2.68.4-18.el9_7.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45803 | NONE0 | python3-pip-wheel 21.3.1-1.el9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-41965 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-26603 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-25260 | NONE0 | elfutils-default-yama-scope 0.193-1.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-25260 | NONE0 | elfutils-libelf 0.193-1.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-25260 | NONE0 | elfutils-libs 0.193-1.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-4438 | NONE0 | glibc 2.34-231.el9_7.2 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-4438 | NONE0 | glibc-common 2.34-231.el9_7.2 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-4438 | NONE0 | glibc-langpack-en 2.34-231.el9_7.2 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-4438 | NONE0 | glibc-minimal-langpack 2.34-231.el9_7.2 fixed in 2.34-270.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-9820 | NONE0 | gnutls 3.8.3-9.el9 fixed in 3.8.3-10.el9_7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-15028 | NONE0 | libarchive 3.5.3-6.el9_6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-41080 | NONE0 | expat 2.5.0-5.el9_7.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-3360 | NONE0 | glib2 2.68.4-18.el9_7.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-7039 | NONE0 | glib2 2.68.4-18.el9_7.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0988 | NONE0 | glib2 2.68.4-18.el9_7.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-3832 | NONE0 | gnutls 3.8.3-9.el9 fixed in 3.8.10-4.el9_8 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-5419 | NONE0 | gnutls 3.8.3-9.el9 fixed in 3.8.10-4.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0989 | NONE0 | libxml2 2.9.13-14.el9_7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45446 | NONE0 | openssl-libs 1:3.5.1-7.el9_7 fixed in 1:3.5.5-4.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-66861 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66862 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-41990 | NONE0 | libgcrypt 1.10.0-11.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4519 | NONE0 | python3 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-13462 | NONE0 | python3 3.9.25-3.el9_7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-2297 | NONE0 | python3 3.9.25-3.el9_7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3479 | NONE0 | python3 3.9.25-3.el9_7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4519 | NONE0 | python3-libs 3.9.25-3.el9_7 fixed in 3.9.25-7.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-13462 | NONE0 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-2297 | NONE0 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3479 | NONE0 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-70873 | NONE0 | sqlite-libs 3.34.1-9.el9_7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-9232 | NONE0 | openssl-libs 1:3.5.1-7.el9_7 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-1795 | NONE0 | python3 3.9.25-3.el9_7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1795 | NONE0 | python3-libs 3.9.25-3.el9_7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-16517 | NONE0 | libarchive 3.5.3-6.el9_6 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-0992 | NONE0 | libxml2 2.9.13-14.el9_7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69644 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | gdb-gdbserver 16.3-2.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-1485 | NONE0 | glib2 2.68.4-18.el9_7.1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-24515 | NONE0 | expat 2.5.0-5.el9_7.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6170 | NONE0 | libxml2 2.9.13-14.el9_7 fixed in 2.9.13-14.el9_8.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28422 | NONE0 | vim-minimal 2:8.2.2637-23.el9_7 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.
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.