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.30-9.el8 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27534 | MEDIUM5.28 | curl 7.61.1-33.el8 No fix yet | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2398 | MEDIUM5.17 | curl 7.61.1-33.el8 fixed in 7.61.1-34.el8_10.2 | 36.1% High Exploitation Risk | Post-Exploit |
| CVE-2023-2650 | MEDIUM5.07 | openssl 1:1.1.1k-12.el8_9 No fix yet | 75.1% Actively Exploited | Post-Exploit |
| CVE-2026-31789 | MEDIUM5 | openssl 1:1.1.1k-12.el8_9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45447 | MEDIUM4.86 | openssl 1:1.1.1k-12.el8_9 fixed in 1:1.1.1k-16.el8_6 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-38428 | MEDIUM4.64 | wget 1.19.5-11.el8 fixed in 1.19.5-12.el8_10 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-28390 | MEDIUM4.5 | openssl 1:1.1.1k-12.el8_9 fixed in 1:1.1.1k-17.el8_6 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0464 | MEDIUM4.5 | openssl 1:1.1.1k-12.el8_9 No fix yet | 3.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28388 | MEDIUM4.5 | openssl 1:1.1.1k-12.el8_9 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28389 | MEDIUM4.5 | openssl 1:1.1.1k-12.el8_9 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9923 | MEDIUM4.5 | tar 2:1.30-9.el8 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2024-7264 | MEDIUM4.48 | curl 7.61.1-33.el8 No fix yet | 17.3% High Exploitation Risk | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | curl 7.61.1-33.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | curl 7.61.1-33.el8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-28387 | MEDIUM4.13 | openssl 1:1.1.1k-12.el8_9 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2023-46218 | LOW3.9 | curl 7.61.1-33.el8 fixed in 7.61.1-33.el8_9.5 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-10524 | LOW3.9 | wget 1.19.5-11.el8 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | curl 7.61.1-33.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | curl 7.61.1-33.el8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | curl 7.61.1-33.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | curl 7.61.1-33.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69421 | LOW3.82 | openssl 1:1.1.1k-12.el8_9 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-69419 | LOW3.77 | openssl 1:1.1.1k-12.el8_9 fixed in 1:1.1.1k-15.el8_6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-31879 | LOW3.66 | wget 1.19.5-11.el8 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-58471 | LOW3.62 | wget 1.19.5-11.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-58472 | LOW3.62 | wget 1.19.5-11.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gnupg2 2.2.20-3.el8_6 fixed in 2.2.20-4.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-44604 | LOW3.57 | rpm 4.14.3-28.el8_9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-11053 | LOW3.54 | curl 7.61.1-33.el8 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2024-41996 | LOW3.54 | openssl 1:1.1.1k-12.el8_9 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-5535 | LOW3.54 | openssl 1:1.1.1k-12.el8_9 fixed in 1:1.1.1k-14.el8_6 | 5.6% Low-Moderate Risk | Post-Exploit |
| CVE-2025-13034 | LOW3.47 | curl 7.61.1-33.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | curl 7.61.1-33.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-9230 | LOW3.36 | openssl 1:1.1.1k-12.el8_9 fixed in 1:1.1.1k-14.el8_10 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4741 | LOW3.36 | openssl 1:1.1.1k-12.el8_9 fixed in 1:1.1.1k-16.el8_6 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | curl 7.61.1-33.el8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | curl 7.61.1-33.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | curl 7.61.1-33.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | curl 7.61.1-33.el8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl 7.61.1-33.el8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | curl 7.61.1-33.el8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42771 | LOW3.31 | openssl 1:1.1.1k-12.el8_9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-33056 | LOW3.31 | tar 2:1.30-9.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58469 | LOW3.31 | wget 1.19.5-11.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-0727 | LOW3.3 | openssl 1:1.1.1k-12.el8_9 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-44605 | LOW3.3 | rpm 4.14.3-28.el8_9 No fix yet | — | Post-Exploit |
| CVE-2026-42768 | LOW3.21 | openssl 1:1.1.1k-12.el8_9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-9086 | LOW3.18 | curl 7.61.1-33.el8 fixed in 7.61.1-34.el8_10.9 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0466 | LOW3.18 | openssl 1:1.1.1k-12.el8_9 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0465 | LOW3.18 | openssl 1:1.1.1k-12.el8_9 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.32.1-43.el8 fixed in 2.32.1-48.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-15468 | LOW3.01 | openssl 1:1.1.1k-12.el8_9 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-69420 | LOW3.01 | openssl 1:1.1.1k-12.el8_9 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-22796 | LOW3.01 | openssl 1:1.1.1k-12.el8_9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW3.01 | openssl 1:1.1.1k-12.el8_9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.01 | openssl 1:1.1.1k-12.el8_9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-15146 | LOW3.01 | wget 1.19.5-11.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-34180 | LOW3 | openssl 1:1.1.1k-12.el8_9 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | curl 7.61.1-33.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-2511 | LOW2.89 | openssl 1:1.1.1k-12.el8_9 No fix yet | 54.0% Actively Exploited | Post-Exploit |
| CVE-2025-45582 | LOW2.86 | tar 2:1.30-9.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-24883 | LOW2.8 | gnupg2 2.2.20-3.el8_6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15469 | LOW2.8 | openssl 1:1.1.1k-12.el8_9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-22795 | LOW2.8 | openssl 1:1.1.1k-12.el8_9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW2.8 | openssl 1:1.1.1k-12.el8_9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-53655 | LOW2.8 | tar 2:1.30-9.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 2:1.30-9.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | curl 7.61.1-33.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | curl 7.61.1-33.el8 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | curl 7.61.1-33.el8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42766 | LOW2.7 | openssl 1:1.1.1k-12.el8_9 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux 2.32.1-43.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-58470 | LOW2.7 | wget 1.19.5-11.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | curl 7.61.1-33.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl 7.61.1-33.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gnupg2 2.2.20-3.el8_6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gnupg2 2.2.20-3.el8_6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.9-13.el8_5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-13176 | LOW2.4 | openssl 1:1.1.1k-12.el8_9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-68160 | LOW2.4 | openssl 1:1.1.1k-12.el8_9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-64118 | LOW2.4 | tar 2:1.30-9.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.32.1-43.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-28322 | LOW2.22 | curl 7.61.1-33.el8 fixed in 7.61.1-33.el8_9.5 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-38546 | LOW2.22 | curl 7.61.1-33.el8 fixed in 7.61.1-33.el8_9.5 | 6.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-69418 | LOW2.04 | openssl 1:1.1.1k-12.el8_9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-20193 | LOW1.98 | tar 2:1.30-9.el8 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | shadow-utils 2:4.6-19.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gnupg2 2.2.20-3.el8_6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-39804 | LOW1.68 | tar 2:1.30-9.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gnupg2 2.2.20-3.el8_6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-42960 | NONE0 | python3-unbound 1.16.2-5.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42960 | NONE0 | unbound-libs 1.16.2-5.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-12900 | NONE0 | bzip2-libs 1.0.6-26.el8 fixed in 1.0.6-28.el8_10 | 8.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-37920 | NONE0 | ca-certificates 2023.2.60_v7.0.306-80.0.el8_8 fixed in 2024.2.69_v8.0.303-80.0.el8_10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-45491 | NONE0 | expat 2.2.5-11.el8 fixed in 2.2.5-15.el8_10 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-45492 | NONE0 | expat 2.2.5-11.el8 fixed in 2.2.5-15.el8_10 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2025-14087 | NONE0 | glib2 2.56.4-161.el8 fixed in 2.56.4-169.el8_10 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42010 | NONE0 | gnutls 3.6.16-8.el8_9.1 fixed in 3.6.16-8.el8_10.6 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-56171 | NONE0 | libxml2 2.9.7-18.el8_9 fixed in 2.9.7-19.el8_10 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-6653 | NONE0 | libxml2 2.9.7-18.el8_9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31789 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56171 | NONE0 | python3-libxml2 2.9.7-18.el8_9 fixed in 2.9.7-19.el8_10 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-6653 | NONE0 | python3-libxml2 2.9.7-18.el8_9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-20703 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-58016 | NONE0 | glib2 2.56.4-161.el8 fixed in 2.56.4-170.el8_10 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-33845 | NONE0 | gnutls 3.6.16-8.el8_9.1 fixed in 3.6.16-8.el8_10.6 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-37371 | NONE0 | krb5-libs 1.18.2-26.el8_9 fixed in 1.18.2-29.el8_10 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2025-49794 | NONE0 | libxml2 2.9.7-18.el8_9 fixed in 2.9.7-21.el8_10.1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-49796 | NONE0 | libxml2 2.9.7-18.el8_9 fixed in 2.9.7-21.el8_10.1 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2025-49794 | NONE0 | python3-libxml2 2.9.7-18.el8_9 fixed in 2.9.7-21.el8_10.1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-49796 | NONE0 | python3-libxml2 2.9.7-18.el8_9 fixed in 2.9.7-21.el8_10.1 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2024-3596 | NONE0 | krb5-libs 1.18.2-26.el8_9 fixed in 1.18.2-30.el8_10 | 14.9% High Exploitation Risk | Not Applicable |
| CVE-2024-2961 | NONE0 | glibc 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.1 | 88.3% Actively Exploited | Not Applicable |
| CVE-2024-2961 | NONE0 | glibc-common 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.1 | 88.3% Actively Exploited | Not Applicable |
| CVE-2024-2961 | NONE0 | glibc-gconv-extra 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.1 | 88.3% Actively Exploited | Not Applicable |
| CVE-2024-2961 | NONE0 | glibc-langpack-en 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.1 | 88.3% Actively Exploited | Not Applicable |
| CVE-2024-2961 | NONE0 | glibc-minimal-langpack 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.1 | 88.3% Actively Exploited | Not Applicable |
| CVE-2023-27534 | NONE0 | libcurl 7.61.1-33.el8 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-5372 | NONE0 | libssh 0.9.6-13.el8_9 fixed in 0.9.6-16.el8_10 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-5372 | NONE0 | libssh-config 0.9.6-13.el8_9 fixed in 0.9.6-16.el8_10 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-39537 | NONE0 | ncurses-base 6.1-10.20180224.el8 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-39537 | NONE0 | ncurses-libs 6.1-10.20180224.el8 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-6345 | NONE0 | platform-python-setuptools 39.2.0-7.el8 fixed in 39.2.0-8.el8_10 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2025-47273 | NONE0 | platform-python-setuptools 39.2.0-7.el8 fixed in 39.2.0-9.el8_10 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-6345 | NONE0 | python3-setuptools-wheel 39.2.0-7.el8 fixed in 39.2.0-8.el8_10 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2025-47273 | NONE0 | python3-setuptools-wheel 39.2.0-7.el8 fixed in 39.2.0-9.el8_10 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-47162 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | glib2 2.56.4-161.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-44690 | NONE0 | python3-unbound 1.16.2-5.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-44690 | NONE0 | unbound-libs 1.16.2-5.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | glib2 2.56.4-161.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | glib2 2.56.4-161.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | glib2 2.56.4-161.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-32988 | NONE0 | gnutls 3.6.16-8.el8_9.1 fixed in 3.6.16-8.el8_10.4 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-32990 | NONE0 | gnutls 3.6.16-8.el8_9.1 fixed in 3.6.16-8.el8_10.4 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-42013 | NONE0 | gnutls 3.6.16-8.el8_9.1 fixed in 3.6.16-8.el8_10.6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5260 | NONE0 | gnutls 3.6.16-8.el8_9.1 fixed in 3.6.16-8.el8_10.6 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-0966 | NONE0 | libssh 0.9.6-13.el8_9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-0966 | NONE0 | libssh-config 0.9.6-13.el8_9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-34982 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 fixed in 2:8.0.1763-22.el8_10.3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52859 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8286 | NONE0 | libcurl 7.61.1-33.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-15079 | NONE0 | libcurl 7.61.1-33.el8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-5318 | NONE0 | libssh 0.9.6-13.el8_9 fixed in 0.9.6-15.el8_10 | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2025-5318 | NONE0 | libssh-config 0.9.6-13.el8_9 fixed in 0.9.6-15.el8_10 | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-17543 | NONE0 | lz4-libs 1.8.3-3.el8_4 fixed in 1.8.3-5.el8_10 | 9.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-45447 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 fixed in 1:1.1.1k-16.el8_6 | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-28387 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-6100 | NONE0 | platform-python 3.6.8-56.el8_9.3 fixed in 3.6.8-76.el8_10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6100 | NONE0 | python3-libs 3.6.8-56.el8_9.3 fixed in 3.6.8-76.el8_10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2020-35512 | NONE0 | dbus 1:1.12.8-26.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-35512 | NONE0 | dbus-common 1:1.12.8-26.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-35512 | NONE0 | dbus-daemon 1:1.12.8-26.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-35512 | NONE0 | dbus-libs 1:1.12.8-26.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-35512 | NONE0 | dbus-tools 1:1.12.8-26.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5914 | NONE0 | libarchive 3.3.3-5.el8 fixed in 3.3.3-6.el8_10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-25724 | NONE0 | libarchive 3.3.3-5.el8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-48864 | NONE0 | libsolv 0.7.20-6.el8 fixed in 0.7.20-7.el8_10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-7425 | NONE0 | libxml2 2.9.7-18.el8_9 fixed in 2.9.7-21.el8_10.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49043 | NONE0 | libxml2 2.9.7-18.el8_9 fixed in 2.9.7-18.el8_10.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11979 | NONE0 | libxml2 2.9.7-18.el8_9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6020 | NONE0 | pam 1.3.1-27.el8 fixed in 1.3.1-38.el8_10 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-8941 | NONE0 | pam 1.3.1-27.el8 fixed in 1.3.1-38.el8_10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6597 | NONE0 | platform-python 3.6.8-56.el8_9.3 fixed in 3.6.8-62.el8_10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-9287 | NONE0 | platform-python 3.6.8-56.el8_9.3 fixed in 3.6.8-69.el8_10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2018-20225 | NONE0 | platform-python-pip 9.0.3-23.el8 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2023-6597 | NONE0 | python3-libs 3.6.8-56.el8_9.3 fixed in 3.6.8-62.el8_10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-9287 | NONE0 | python3-libs 3.6.8-56.el8_9.3 fixed in 3.6.8-69.el8_10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-7425 | NONE0 | python3-libxml2 2.9.7-18.el8_9 fixed in 2.9.7-21.el8_10.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49043 | NONE0 | python3-libxml2 2.9.7-18.el8_9 fixed in 2.9.7-18.el8_10.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11979 | NONE0 | python3-libxml2 2.9.7-18.el8_9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2018-20225 | NONE0 | python3-pip-wheel 9.0.3-23.el8 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2026-29111 | NONE0 | systemd 239-78.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-29111 | NONE0 | systemd-libs 239-78.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-29111 | NONE0 | systemd-pam 239-78.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55895 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57456 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-39881 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-55693 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-57455 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-59856 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-59858 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2021-3927 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2021-3974 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-0351 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-1619 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-1720 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-2124 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-2125 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-2126 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-2129 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-2175 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-2182 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-2183 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-2206 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-2207 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-2210 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-2284 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-2285 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-2286 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-2343 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-2344 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-2345 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-2522 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-2819 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-2845 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-2849 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-2946 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-3037 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-3234 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-3235 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-3256 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-3296 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-3352 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-4292 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-0049 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-0054 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-0288 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-0433 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-0512 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-1127 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-2610 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-4733 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-4734 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-4735 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-4738 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-4750 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-4751 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-4752 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-4781 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-5535 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-22667 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1215 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-13601 | NONE0 | glib2 2.56.4-161.el8 fixed in 2.56.4-168.el8_10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-24928 | NONE0 | libxml2 2.9.7-18.el8_9 fixed in 2.9.7-19.el8_10 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-24928 | NONE0 | python3-libxml2 2.9.7-18.el8_9 fixed in 2.9.7-19.el8_10 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6965 | NONE0 | sqlite-libs 3.26.0-19.el8_9 fixed in 3.26.0-20.el8_10 | 74.4% Actively Exploited | Not Applicable |
| CVE-2024-33599 | NONE0 | glibc 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.2 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-33599 | NONE0 | glibc-common 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.2 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-33599 | NONE0 | glibc-gconv-extra 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.2 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-33599 | NONE0 | glibc-langpack-en 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.2 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-33599 | NONE0 | glibc-minimal-langpack 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.2 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-12718 | NONE0 | platform-python 3.6.8-56.el8_9.3 fixed in 3.6.8-70.el8_10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-4517 | NONE0 | platform-python 3.6.8-56.el8_9.3 fixed in 3.6.8-70.el8_10 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-12718 | NONE0 | python3-libs 3.6.8-56.el8_9.3 fixed in 3.6.8-70.el8_10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-4517 | NONE0 | python3-libs 3.6.8-56.el8_9.3 fixed in 3.6.8-70.el8_10 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-6176 | NONE0 | brotli 1.0.6-3.el8 fixed in 1.0.6-4.el8_10 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-71319 | NONE0 | dnf-plugin-subscription-manager 1.28.40-1.el8_9 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-12143 | NONE0 | dnf-plugin-subscription-manager 1.28.40-1.el8_9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45186 | NONE0 | expat 2.2.5-11.el8 fixed in 2.5.0-2.el8_10 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-23990 | NONE0 | expat 2.2.5-11.el8 fixed in 2.5.0-1.el8_10 | 4.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-52425 | NONE0 | expat 2.2.5-11.el8 fixed in 2.2.5-11.el8_9.1 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2024-28757 | NONE0 | expat 2.2.5-11.el8 fixed in 2.5.0-1.el8_10 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2024-45490 | NONE0 | expat 2.2.5-11.el8 fixed in 2.2.5-15.el8_10 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2024-8176 | NONE0 | expat 2.2.5-11.el8 fixed in 2.2.5-17.el8_10 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2025-66864 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58011 | NONE0 | glib2 2.56.4-161.el8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | glib2 2.56.4-161.el8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-29499 | NONE0 | glib2 2.56.4-161.el8 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-32636 | NONE0 | glib2 2.56.4-161.el8 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2021-43618 | NONE0 | gmp 1:6.1.2-10.el8 fixed in 1:6.1.2-11.el8 | 3.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-33846 | NONE0 | gnutls 3.6.16-8.el8_9.1 fixed in 3.6.16-8.el8_10.6 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-42009 | NONE0 | gnutls 3.6.16-8.el8_9.1 fixed in 3.6.16-8.el8_10.6 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-37370 | NONE0 | krb5-libs 1.18.2-26.el8_9 fixed in 1.18.2-29.el8_10 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-40355 | NONE0 | krb5-libs 1.18.2-26.el8_9 fixed in 1.18.2-34.el8_10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-40356 | NONE0 | krb5-libs 1.18.2-26.el8_9 fixed in 1.18.2-34.el8_10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4424 | NONE0 | libarchive 3.3.3-5.el8 fixed in 3.3.3-7.el8_10 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-5121 | NONE0 | libarchive 3.3.3-5.el8 fixed in 3.3.3-7.el8_10 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-8927 | NONE0 | libcurl 7.61.1-33.el8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-2398 | NONE0 | libcurl 7.61.1-33.el8 fixed in 7.61.1-34.el8_10.2 | 36.1% High Exploitation Risk | Not Applicable |
| CVE-2026-5773 | NONE0 | libcurl 7.61.1-33.el8 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8932 | NONE0 | libcurl 7.61.1-33.el8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6276 | NONE0 | libcurl 7.61.1-33.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2018-20657 | NONE0 | libgcc 8.5.0-20.el8 No fix yet | 4.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-41989 | NONE0 | libgcrypt 1.8.5-7.el8_6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-27135 | NONE0 | libnghttp2 1.33.0-5.el8_9 fixed in 1.33.0-6.el8_10.2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-3731 | NONE0 | libssh 0.9.6-13.el8_9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-59847 | NONE0 | libssh 0.9.6-13.el8_9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-59850 | NONE0 | libssh 0.9.6-13.el8_9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-3731 | NONE0 | libssh-config 0.9.6-13.el8_9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-59847 | NONE0 | libssh-config 0.9.6-13.el8_9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-59850 | NONE0 | libssh-config 0.9.6-13.el8_9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2018-20657 | NONE0 | libstdc++ 8.5.0-20.el8 No fix yet | 4.0% Low-Moderate Risk | Not Applicable |
| CVE-2024-25062 | NONE0 | libxml2 2.9.7-18.el8_9 fixed in 2.9.7-18.el8_10.1 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2025-32414 | NONE0 | libxml2 2.9.7-18.el8_9 fixed in 2.9.7-20.el8_10 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-32415 | NONE0 | libxml2 2.9.7-18.el8_9 fixed in 2.9.7-21.el8_10.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-6021 | NONE0 | libxml2 2.9.7-18.el8_9 fixed in 2.9.7-21.el8_10.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-6732 | NONE0 | libxml2 2.9.7-18.el8_9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-27113 | NONE0 | libxml2 2.9.7-18.el8_9 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-4899 | NONE0 | libzstd 1.4.4-1.el8 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-2953 | NONE0 | openldap 2.4.46-18.el8 fixed in 2.4.46-19.el8_10 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2023-2953 | NONE0 | openldap-devel 2.4.46-18.el8 fixed in 2.4.46-19.el8_10 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2026-28390 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 fixed in 1:1.1.1k-17.el8_6 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-0464 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 No fix yet | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2025-69421 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-28388 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-28389 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-41409 | NONE0 | pcre2 10.32-3.el8_6 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-4138 | NONE0 | platform-python 3.6.8-56.el8_9.3 fixed in 3.6.8-70.el8_10 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-15308 | NONE0 | platform-python 3.6.8-56.el8_9.3 fixed in 3.6.8-77.el8_10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-6232 | NONE0 | platform-python 3.6.8-56.el8_9.3 fixed in 3.6.8-67.el8_10 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-4435 | NONE0 | platform-python 3.6.8-56.el8_9.3 fixed in 3.6.8-70.el8_10 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-8194 | NONE0 | platform-python 3.6.8-56.el8_9.3 fixed in 3.6.8-71.el8_10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-3644 | NONE0 | platform-python 3.6.8-56.el8_9.3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4224 | NONE0 | platform-python 3.6.8-56.el8_9.3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-7210 | NONE0 | platform-python 3.6.8-56.el8_9.3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2019-9674 | NONE0 | platform-python 3.6.8-56.el8_9.3 No fix yet | 5.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-7592 | NONE0 | platform-python 3.6.8-56.el8_9.3 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-71319 | NONE0 | python3-cloud-what 1.28.40-1.el8_9 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-12143 | NONE0 | python3-cloud-what 1.28.40-1.el8_9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-3651 | NONE0 | python3-idna 2.5-5.el8 fixed in 2.5-7.el8_10 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2025-4138 | NONE0 | python3-libs 3.6.8-56.el8_9.3 fixed in 3.6.8-70.el8_10 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-15308 | NONE0 | python3-libs 3.6.8-56.el8_9.3 fixed in 3.6.8-77.el8_10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-6232 | NONE0 | python3-libs 3.6.8-56.el8_9.3 fixed in 3.6.8-67.el8_10 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-4435 | NONE0 | python3-libs 3.6.8-56.el8_9.3 fixed in 3.6.8-70.el8_10 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-8194 | NONE0 | python3-libs 3.6.8-56.el8_9.3 fixed in 3.6.8-71.el8_10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-3644 | NONE0 | python3-libs 3.6.8-56.el8_9.3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4224 | NONE0 | python3-libs 3.6.8-56.el8_9.3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-7210 | NONE0 | python3-libs 3.6.8-56.el8_9.3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2019-9674 | NONE0 | python3-libs 3.6.8-56.el8_9.3 No fix yet | 5.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-7592 | NONE0 | python3-libs 3.6.8-56.el8_9.3 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-25062 | NONE0 | python3-libxml2 2.9.7-18.el8_9 fixed in 2.9.7-18.el8_10.1 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2025-32414 | NONE0 | python3-libxml2 2.9.7-18.el8_9 fixed in 2.9.7-20.el8_10 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-32415 | NONE0 | python3-libxml2 2.9.7-18.el8_9 fixed in 2.9.7-21.el8_10.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-6021 | NONE0 | python3-libxml2 2.9.7-18.el8_9 fixed in 2.9.7-21.el8_10.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-6732 | NONE0 | python3-libxml2 2.9.7-18.el8_9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-27113 | NONE0 | python3-libxml2 2.9.7-18.el8_9 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-71319 | NONE0 | python3-subscription-manager-rhsm 1.28.40-1.el8_9 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-12143 | NONE0 | python3-subscription-manager-rhsm 1.28.40-1.el8_9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-71319 | NONE0 | python3-syspurpose 1.28.40-1.el8_9 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-12143 | NONE0 | python3-syspurpose 1.28.40-1.el8_9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-50387 | NONE0 | python3-unbound 1.16.2-5.el8 fixed in 1.16.2-5.el8_9.2 | 100.0% Actively Exploited | Not Applicable |
| CVE-2023-50868 | NONE0 | python3-unbound 1.16.2-5.el8 fixed in 1.16.2-5.el8_9.2 | 81.7% Actively Exploited | Not Applicable |
| CVE-2025-5994 | NONE0 | python3-unbound 1.16.2-5.el8 fixed in 1.16.2-5.9.el8_10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-41292 | NONE0 | python3-unbound 1.16.2-5.el8 fixed in 1.16.2-5.12.el8_10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42944 | NONE0 | python3-unbound 1.16.2-5.el8 fixed in 1.16.2-5.11.el8_10 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42959 | NONE0 | python3-unbound 1.16.2-5.el8 fixed in 1.16.2-5.11.el8_10 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-40622 | NONE0 | python3-unbound 1.16.2-5.el8 fixed in 1.16.2-5.12.el8_10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-16866 | NONE0 | python3-unbound 1.16.2-5.el8 No fix yet | 3.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-66418 | NONE0 | python3-urllib3 1.24.2-5.el8_9.2 fixed in 1.24.2-9.el8_10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-66471 | NONE0 | python3-urllib3 1.24.2-5.el8_9.2 fixed in 1.24.2-9.el8_10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-21441 | NONE0 | python3-urllib3 1.24.2-5.el8_9.2 fixed in 1.24.2-9.el8_10 | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-19244 | NONE0 | sqlite-libs 3.26.0-19.el8_9 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2019-9936 | NONE0 | sqlite-libs 3.26.0-19.el8_9 No fix yet | 5.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-9937 | NONE0 | sqlite-libs 3.26.0-19.el8_9 No fix yet | 6.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-71319 | NONE0 | subscription-manager 1.28.40-1.el8_9 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-12143 | NONE0 | subscription-manager 1.28.40-1.el8_9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-71319 | NONE0 | subscription-manager-rhsm-certificates 20220623-1.el8 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-12143 | NONE0 | subscription-manager-rhsm-certificates 20220623-1.el8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-50387 | NONE0 | unbound-libs 1.16.2-5.el8 fixed in 1.16.2-5.el8_9.2 | 100.0% Actively Exploited | Not Applicable |
| CVE-2023-50868 | NONE0 | unbound-libs 1.16.2-5.el8 fixed in 1.16.2-5.el8_9.2 | 81.7% Actively Exploited | Not Applicable |
| CVE-2025-5994 | NONE0 | unbound-libs 1.16.2-5.el8 fixed in 1.16.2-5.9.el8_10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-41292 | NONE0 | unbound-libs 1.16.2-5.el8 fixed in 1.16.2-5.12.el8_10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42944 | NONE0 | unbound-libs 1.16.2-5.el8 fixed in 1.16.2-5.11.el8_10 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42959 | NONE0 | unbound-libs 1.16.2-5.el8 fixed in 1.16.2-5.11.el8_10 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-40622 | NONE0 | unbound-libs 1.16.2-5.el8 fixed in 1.16.2-5.12.el8_10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-16866 | NONE0 | unbound-libs 1.16.2-5.el8 No fix yet | 3.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-20786 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-3705 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-5344 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-26269 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-3833 | NONE0 | gnutls 3.6.16-8.el8_9.1 fixed in 3.6.16-8.el8_10.6 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42011 | NONE0 | gnutls 3.6.16-8.el8_9.1 fixed in 3.6.16-8.el8_10.6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-69419 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 fixed in 1:1.1.1k-15.el8_6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-10963 | NONE0 | pam 1.3.1-27.el8 fixed in 1.3.1-36.el8_10 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-4330 | NONE0 | platform-python 3.6.8-56.el8_9.3 fixed in 3.6.8-70.el8_10 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-4330 | NONE0 | python3-libs 3.6.8-56.el8_9.3 fixed in 3.6.8-70.el8_10 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-1488 | NONE0 | python3-unbound 1.16.2-5.el8 fixed in 1.16.2-5.8.el8_10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-1488 | NONE0 | unbound-libs 1.16.2-5.el8 fixed in 1.16.2-5.8.el8_10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25749 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 fixed in 2:8.0.1763-22.el8_10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-41411 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 fixed in 2:8.0.1763-24.el8_10 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-54369 | NONE0 | acl 2.2.53-1.el8 fixed in 2.4.0-1.el8_10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-4156 | NONE0 | gawk 4.2.1-4.el8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42012 | NONE0 | gnutls 3.6.16-8.el8_9.1 fixed in 3.6.16-8.el8_10.6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-54369 | NONE0 | libacl 2.2.53-1.el8 fixed in 2.4.0-1.el8_10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4786 | NONE0 | platform-python 3.6.8-56.el8_9.3 fixed in 3.6.8-76.el8_10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-15366 | NONE0 | platform-python 3.6.8-56.el8_9.3 fixed in 3.6.8-73.el8_10 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15367 | NONE0 | platform-python 3.6.8-56.el8_9.3 fixed in 3.6.8-73.el8_10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-1299 | NONE0 | platform-python 3.6.8-56.el8_9.3 fixed in 3.6.8-73.el8_10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4786 | NONE0 | python3-libs 3.6.8-56.el8_9.3 fixed in 3.6.8-76.el8_10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-15366 | NONE0 | python3-libs 3.6.8-56.el8_9.3 fixed in 3.6.8-73.el8_10 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15367 | NONE0 | python3-libs 3.6.8-56.el8_9.3 fixed in 3.6.8-73.el8_10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-1299 | NONE0 | python3-libs 3.6.8-56.el8_9.3 fixed in 3.6.8-73.el8_10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-4166 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-2287 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-52533 | NONE0 | glib2 2.56.4-161.el8 fixed in 2.56.4-166.el8_10 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-4802 | NONE0 | glibc 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.22 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-4802 | NONE0 | glibc-common 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.22 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-4802 | NONE0 | glibc-gconv-extra 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.22 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-4802 | NONE0 | glibc-langpack-en 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.22 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-4802 | NONE0 | glibc-minimal-langpack 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.22 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-4878 | NONE0 | libcap 2.48-6.el8_9 fixed in 2.48-6.el8_10.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-44604 | NONE0 | python3-rpm 4.14.3-28.el8_9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-44604 | NONE0 | rpm-build-libs 4.14.3-28.el8_9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-44604 | NONE0 | rpm-libs 4.14.3-28.el8_9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46483 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56132 | NONE0 | expat 2.2.5-11.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56403 | NONE0 | expat 2.2.5-11.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56404 | NONE0 | expat 2.2.5-11.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56405 | NONE0 | expat 2.2.5-11.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56406 | NONE0 | expat 2.2.5-11.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56407 | NONE0 | expat 2.2.5-11.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2013-0340 | NONE0 | expat 2.2.5-11.el8 fixed in 2.5.0-1.el8_10 | 20.1% High Exploitation Risk | Not Applicable |
| CVE-2025-13034 | NONE0 | libcurl 7.61.1-33.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-1965 | NONE0 | libcurl 7.61.1-33.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-22185 | NONE0 | openldap 2.4.46-18.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22185 | NONE0 | openldap-devel 2.4.46-18.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-6923 | NONE0 | platform-python 3.6.8-56.el8_9.3 fixed in 3.6.8-67.el8_10 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-0938 | NONE0 | platform-python 3.6.8-56.el8_9.3 fixed in 3.6.8-74.el8_10 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-6923 | NONE0 | python3-libs 3.6.8-56.el8_9.3 fixed in 3.6.8-67.el8_10 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-0938 | NONE0 | python3-libs 3.6.8-56.el8_9.3 fixed in 3.6.8-74.el8_10 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-4105 | NONE0 | systemd 239-78.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4105 | NONE0 | systemd-libs 239-78.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4105 | NONE0 | systemd-pam 239-78.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-42014 | NONE0 | gnutls 3.6.16-8.el8_9.1 fixed in 3.6.16-8.el8_10.6 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-5915 | NONE0 | libarchive 3.3.3-5.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5918 | NONE0 | libarchive 3.3.3-5.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-28419 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-1170 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-1175 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-14512 | NONE0 | glib2 2.56.4-161.el8 fixed in 2.56.4-169.el8_10 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-4437 | NONE0 | glibc 2.28-236.el8_9.12 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | glibc 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4437 | NONE0 | glibc-common 2.28-236.el8_9.12 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | glibc-common 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4437 | NONE0 | glibc-gconv-extra 2.28-236.el8_9.12 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | glibc-gconv-extra 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4437 | NONE0 | glibc-langpack-en 2.28-236.el8_9.12 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | glibc-langpack-en 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4437 | NONE0 | glibc-minimal-langpack 2.28-236.el8_9.12 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | glibc-minimal-langpack 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6395 | NONE0 | gnutls 3.6.16-8.el8_9.1 fixed in 3.6.16-8.el8_10.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-4209 | NONE0 | gnutls 3.6.16-8.el8_9.1 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2025-24528 | NONE0 | krb5-libs 1.18.2-26.el8_9 fixed in 1.18.2-31.el8_10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4426 | NONE0 | libarchive 3.3.3-5.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2018-1000879 | NONE0 | libarchive 3.3.3-5.el8 No fix yet | 3.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-1000880 | NONE0 | libarchive 3.3.3-5.el8 No fix yet | 4.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-46218 | NONE0 | libcurl 7.61.1-33.el8 fixed in 7.61.1-33.el8_9.5 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2026-11856 | NONE0 | libcurl 7.61.1-33.el8 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-3784 | NONE0 | libcurl 7.61.1-33.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-5545 | NONE0 | libcurl 7.61.1-33.el8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6429 | NONE0 | libcurl 7.61.1-33.el8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8924 | NONE0 | libcurl 7.61.1-33.el8 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-7264 | NONE0 | libcurl 7.61.1-33.el8 No fix yet | 17.3% High Exploitation Risk | Not Applicable |
| CVE-2025-14524 | NONE0 | libcurl 7.61.1-33.el8 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-9149 | NONE0 | libsolv 0.7.20-6.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-5351 | NONE0 | libssh 0.9.6-13.el8_9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-59843 | NONE0 | libssh 0.9.6-13.el8_9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-59844 | NONE0 | libssh 0.9.6-13.el8_9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-5351 | NONE0 | libssh-config 0.9.6-13.el8_9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-59843 | NONE0 | libssh-config 0.9.6-13.el8_9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-59844 | NONE0 | libssh-config 0.9.6-13.el8_9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45322 | NONE0 | libxml2 2.9.7-18.el8_9 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2020-19185 | NONE0 | ncurses-base 6.1-10.20180224.el8 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19186 | NONE0 | ncurses-base 6.1-10.20180224.el8 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2020-19187 | NONE0 | ncurses-base 6.1-10.20180224.el8 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19188 | NONE0 | ncurses-base 6.1-10.20180224.el8 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19189 | NONE0 | ncurses-base 6.1-10.20180224.el8 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2020-19190 | NONE0 | ncurses-base 6.1-10.20180224.el8 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.1-10.20180224.el8 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2020-19185 | NONE0 | ncurses-libs 6.1-10.20180224.el8 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19186 | NONE0 | ncurses-libs 6.1-10.20180224.el8 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2020-19187 | NONE0 | ncurses-libs 6.1-10.20180224.el8 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19188 | NONE0 | ncurses-libs 6.1-10.20180224.el8 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19189 | NONE0 | ncurses-libs 6.1-10.20180224.el8 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2020-19190 | NONE0 | ncurses-libs 6.1-10.20180224.el8 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-libs 6.1-10.20180224.el8 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-2650 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 No fix yet | 75.1% Actively Exploited | Not Applicable |
| CVE-2026-42771 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11972 | NONE0 | platform-python 3.6.8-56.el8_9.3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-11972 | NONE0 | python3-libs 3.6.8-56.el8_9.3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45322 | NONE0 | python3-libxml2 2.9.7-18.el8_9 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-37891 | NONE0 | python3-urllib3 1.24.2-5.el8_9.2 fixed in 1.24.2-8.el8_10 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-12610 | NONE0 | pam 1.3.1-27.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-54370 | NONE0 | acl 2.2.53-1.el8 fixed in 2.4.0-1.el8_10 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-54370 | NONE0 | libacl 2.2.53-1.el8 fixed in 2.4.0-1.el8_10 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-54371 | NONE0 | libattr 2.4.48-3.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-0964 | NONE0 | libssh 0.9.6-13.el8_9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0964 | NONE0 | libssh-config 0.9.6-13.el8_9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42768 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-5958 | NONE0 | sed 4.5-5.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-1757 | NONE0 | libxml2 2.9.7-18.el8_9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-13757 | NONE0 | p11-kit 0.23.22-1.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-13757 | NONE0 | p11-kit-trust 0.23.22-1.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-0450 | NONE0 | platform-python 3.6.8-56.el8_9.3 fixed in 3.6.8-62.el8_10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-0450 | NONE0 | python3-libs 3.6.8-56.el8_9.3 fixed in 3.6.8-62.el8_10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-1757 | NONE0 | python3-libxml2 2.9.7-18.el8_9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56391 | NONE0 | coreutils-single 8.30-15.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0235 | NONE0 | dnf-plugin-subscription-manager 1.28.40-1.el8_9 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-4647 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libblkid 2.32.1-43.el8 fixed in 2.32.1-48.el8_10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libfdisk 2.32.1-43.el8 fixed in 2.32.1-48.el8_10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-11023 | NONE0 | libgcc 8.5.0-20.el8 fixed in 8.5.0-23.el8_10 | 83.8% Actively Exploited | Not Applicable |
| CVE-2025-14104 | NONE0 | libmount 2.32.1-43.el8 fixed in 2.32.1-48.el8_10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libsmartcols 2.32.1-43.el8 fixed in 2.32.1-48.el8_10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-11023 | NONE0 | libstdc++ 8.5.0-20.el8 fixed in 8.5.0-23.el8_10 | 83.8% Actively Exploited | Not Applicable |
| CVE-2025-14104 | NONE0 | libuuid 2.32.1-43.el8 fixed in 2.32.1-48.el8_10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6019 | NONE0 | platform-python 3.6.8-56.el8_9.3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-50181 | NONE0 | platform-python-pip 9.0.3-23.el8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-50182 | NONE0 | platform-python-pip 9.0.3-23.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-0235 | NONE0 | python3-cloud-what 1.28.40-1.el8_9 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-6019 | NONE0 | python3-libs 3.6.8-56.el8_9.3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-50181 | NONE0 | python3-pip-wheel 9.0.3-23.el8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-50182 | NONE0 | python3-pip-wheel 9.0.3-23.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-0235 | NONE0 | python3-subscription-manager-rhsm 1.28.40-1.el8_9 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-0235 | NONE0 | python3-syspurpose 1.28.40-1.el8_9 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2025-11411 | NONE0 | python3-unbound 1.16.2-5.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-0235 | NONE0 | subscription-manager 1.28.40-1.el8_9 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-0235 | NONE0 | subscription-manager-rhsm-certificates 20220623-1.el8 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2025-11411 | NONE0 | unbound-libs 1.16.2-5.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-5713 | NONE0 | platform-python 3.6.8-56.el8_9.3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-5713 | NONE0 | python3-libs 3.6.8-56.el8_9.3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-50602 | NONE0 | expat 2.2.5-11.el8 fixed in 2.2.5-16.el8_10 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-50219 | NONE0 | expat 2.2.5-11.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56412 | NONE0 | expat 2.2.5-11.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1153 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-5435 | NONE0 | glibc 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.40 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-15281 | NONE0 | glibc 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.31 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | glibc-common 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.40 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-15281 | NONE0 | glibc-common 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.31 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | glibc-gconv-extra 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.40 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-15281 | NONE0 | glibc-gconv-extra 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.31 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | glibc-langpack-en 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.40 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-15281 | NONE0 | glibc-langpack-en 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.31 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | glibc-minimal-langpack 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.40 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-15281 | NONE0 | glibc-minimal-langpack 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.31 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-3576 | NONE0 | krb5-libs 1.18.2-26.el8_9 fixed in 1.18.2-32.el8_10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26458 | NONE0 | krb5-libs 1.18.2-26.el8_9 fixed in 1.18.2-27.el8_10 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | krb5-libs 1.18.2-26.el8_9 fixed in 1.18.2-27.el8_10 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-11053 | NONE0 | libcurl 7.61.1-33.el8 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-12904 | NONE0 | libgcrypt 1.8.5-7.el8_6 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-2236 | NONE0 | libgcrypt 1.8.5-7.el8_6 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-59845 | NONE0 | libssh 0.9.6-13.el8_9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-59845 | NONE0 | libssh-config 0.9.6-13.el8_9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-13151 | NONE0 | libtasn1 4.13-4.el8_7 fixed in 4.13-6.el8_10 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-0990 | NONE0 | libxml2 2.9.7-18.el8_9 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-41996 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-5535 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 fixed in 1:1.1.1k-14.el8_6 | 5.6% Low-Moderate Risk | Not Applicable |
| CVE-2025-15468 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-69420 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-22796 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-42770 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-9076 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-13346 | NONE0 | platform-python-pip 9.0.3-23.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-0990 | NONE0 | python3-libxml2 2.9.7-18.el8_9 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-13346 | NONE0 | python3-pip-wheel 9.0.3-23.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-44608 | NONE0 | python3-unbound 1.16.2-5.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-55990 | NONE0 | python3-unbound 1.16.2-5.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-7008 | NONE0 | systemd 239-78.el8 fixed in 239-82.el8 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-7008 | NONE0 | systemd-libs 239-78.el8 fixed in 239-82.el8 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-7008 | NONE0 | systemd-pam 239-78.el8 fixed in 239-82.el8 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-44608 | NONE0 | unbound-libs 1.16.2-5.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-55990 | NONE0 | unbound-libs 1.16.2-5.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3783 | NONE0 | libcurl 7.61.1-33.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-15003 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-5916 | NONE0 | libarchive 3.3.3-5.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-9230 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 fixed in 1:1.1.1k-14.el8_10 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2024-4741 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 fixed in 1:1.1.1k-16.el8_6 | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2024-35195 | NONE0 | python3-requests 2.20.0-3.el8_8 fixed in 2.20.0-5.el8_10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-32776 | NONE0 | expat 2.2.5-11.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-32777 | NONE0 | expat 2.2.5-11.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-32778 | NONE0 | expat 2.2.5-11.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66382 | NONE0 | expat 2.2.5-11.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6844 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-47007 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-47010 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-47011 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-32611 | NONE0 | glib2 2.56.4-161.el8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-32665 | NONE0 | glib2 2.56.4-161.el8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-0395 | NONE0 | glibc 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.16 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-0395 | NONE0 | glibc-common 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.16 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-0395 | NONE0 | glibc-gconv-extra 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.16 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-0395 | NONE0 | glibc-langpack-en 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.16 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-0395 | NONE0 | glibc-minimal-langpack 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.16 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-60753 | NONE0 | libarchive 3.3.3-5.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-5745 | NONE0 | libarchive 3.3.3-5.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1632 | NONE0 | libarchive 3.3.3-5.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-14250 | NONE0 | libgcc 8.5.0-20.el8 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-27943 | NONE0 | libgcc 8.5.0-20.el8 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-24056 | NONE0 | libpkgconf 1.4.2-1.el8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0967 | NONE0 | libssh 0.9.6-13.el8_9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-0967 | NONE0 | libssh-config 0.9.6-13.el8_9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-14250 | NONE0 | libstdc++ 8.5.0-20.el8 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-27943 | NONE0 | libstdc++ 8.5.0-20.el8 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2018-1000654 | NONE0 | libtasn1 4.13-4.el8_7 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-9714 | NONE0 | libxml2 2.9.7-18.el8_9 fixed in 2.9.7-21.el8_10.4 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-34459 | NONE0 | libxml2 2.9.7-18.el8_9 fixed in 2.9.7-21.el8_10.5 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2018-19211 | NONE0 | ncurses-base 6.1-10.20180224.el8 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2018-19211 | NONE0 | ncurses-libs 6.1-10.20180224.el8 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-0727 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-15469 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-22795 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-7383 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | pam 1.3.1-27.el8 fixed in 1.3.1-33.el8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-24056 | NONE0 | pkgconf 1.4.2-1.el8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-24056 | NONE0 | pkgconf-m4 1.4.2-1.el8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-24056 | NONE0 | pkgconf-pkg-config 1.4.2-1.el8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-13837 | NONE0 | platform-python 3.6.8-56.el8_9.3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42308 | NONE0 | platform-python 3.6.8-56.el8_9.3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6075 | NONE0 | platform-python 3.6.8-56.el8_9.3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-25645 | NONE0 | platform-python-pip 9.0.3-23.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-13837 | NONE0 | python3-libs 3.6.8-56.el8_9.3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42308 | NONE0 | python3-libs 3.6.8-56.el8_9.3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6075 | NONE0 | python3-libs 3.6.8-56.el8_9.3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-9714 | NONE0 | python3-libxml2 2.9.7-18.el8_9 fixed in 2.9.7-21.el8_10.4 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-34459 | NONE0 | python3-libxml2 2.9.7-18.el8_9 fixed in 2.9.7-21.el8_10.5 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-25645 | NONE0 | python3-pip-wheel 9.0.3-23.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-44605 | NONE0 | python3-rpm 4.14.3-28.el8_9 No fix yet | — | Not Applicable |
| CVE-2026-44605 | NONE0 | rpm-build-libs 4.14.3-28.el8_9 No fix yet | — | Not Applicable |
| CVE-2026-44605 | NONE0 | rpm-libs 4.14.3-28.el8_9 No fix yet | — | Not Applicable |
| CVE-2024-0232 | NONE0 | sqlite-libs 3.26.0-19.el8_9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-3997 | NONE0 | systemd 239-78.el8 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2021-3997 | NONE0 | systemd-libs 239-78.el8 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2021-3997 | NONE0 | systemd-pam 239-78.el8 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-28418 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45130 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55892 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-59857 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2021-3236 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2208 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-2923 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-2980 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2022-3153 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-4293 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-1264 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-2609 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-46246 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-5441 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-45306 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22134 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-24014 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-27171 | NONE0 | zlib 1.2.11-25.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-1489 | NONE0 | glib2 2.56.4-161.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58055 | NONE0 | libnghttp2 1.33.0-5.el8_9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-59375 | NONE0 | expat 2.2.5-11.el8 fixed in 2.5.0-1.el8_10 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-15588 | NONE0 | glib2 2.56.4-161.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-33600 | NONE0 | glibc 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.2 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-0915 | NONE0 | glibc 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.31 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4046 | NONE0 | glibc 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.37 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-33600 | NONE0 | glibc-common 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.2 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-0915 | NONE0 | glibc-common 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.31 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4046 | NONE0 | glibc-common 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.37 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-33600 | NONE0 | glibc-gconv-extra 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.2 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-0915 | NONE0 | glibc-gconv-extra 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.31 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4046 | NONE0 | glibc-gconv-extra 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.37 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-33600 | NONE0 | glibc-langpack-en 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.2 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-0915 | NONE0 | glibc-langpack-en 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.31 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4046 | NONE0 | glibc-langpack-en 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.37 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-33600 | NONE0 | glibc-minimal-langpack 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.2 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-0915 | NONE0 | glibc-minimal-langpack 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.31 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4046 | NONE0 | glibc-minimal-langpack 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.37 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-12243 | NONE0 | gnutls 3.6.16-8.el8_9.1 fixed in 3.6.16-8.el8_10.3 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-28834 | NONE0 | gnutls 3.6.16-8.el8_9.1 fixed in 3.6.16-8.el8_9.3 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-14831 | NONE0 | gnutls 3.6.16-8.el8_9.1 fixed in 3.6.16-8.el8_10.5 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42015 | NONE0 | gnutls 3.6.16-8.el8_9.1 fixed in 3.6.16-8.el8_10.6 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libblkid 2.32.1-43.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-9086 | NONE0 | libcurl 7.61.1-33.el8 fixed in 7.61.1-34.el8_10.9 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-4873 | NONE0 | libcurl 7.61.1-33.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6253 | NONE0 | libcurl 7.61.1-33.el8 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-7168 | NONE0 | libcurl 7.61.1-33.el8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libfdisk 2.32.1-43.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libmount 2.32.1-43.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-28182 | NONE0 | libnghttp2 1.33.0-5.el8_9 fixed in 1.33.0-6.el8_10.1 | 84.8% Actively Exploited | Not Applicable |
| CVE-2026-13595 | NONE0 | libsmartcols 2.32.1-43.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-59848 | NONE0 | libssh 0.9.6-13.el8_9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6918 | NONE0 | libssh 0.9.6-13.el8_9 fixed in 0.9.6-14.el8 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-59848 | NONE0 | libssh-config 0.9.6-13.el8_9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6918 | NONE0 | libssh-config 0.9.6-13.el8_9 fixed in 0.9.6-14.el8 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2024-12133 | NONE0 | libtasn1 4.13-4.el8_7 fixed in 4.13-5.el8_10 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-13595 | NONE0 | libuuid 2.32.1-43.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-0466 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-0465 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-42766 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2025-12084 | NONE0 | platform-python 3.6.8-56.el8_9.3 fixed in 3.6.8-72.el8_10 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-12781 | NONE0 | platform-python 3.6.8-56.el8_9.3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-3276 | NONE0 | platform-python 3.6.8-56.el8_9.3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-4360 | NONE0 | platform-python 3.6.8-56.el8_9.3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45409 | NONE0 | python3-idna 2.5-5.el8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-12084 | NONE0 | python3-libs 3.6.8-56.el8_9.3 fixed in 3.6.8-72.el8_10 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-12781 | NONE0 | python3-libs 3.6.8-56.el8_9.3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-3276 | NONE0 | python3-libs 3.6.8-56.el8_9.3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-4360 | NONE0 | python3-libs 3.6.8-56.el8_9.3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47081 | NONE0 | python3-requests 2.20.0-3.el8_8 fixed in 2.20.0-6.el8_10 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42534 | NONE0 | python3-unbound 1.16.2-5.el8 fixed in 1.16.2-5.12.el8_10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-44390 | NONE0 | python3-unbound 1.16.2-5.el8 fixed in 1.16.2-5.12.el8_10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-8508 | NONE0 | python3-unbound 1.16.2-5.el8 fixed in 1.16.2-5.8.el8_10 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-32792 | NONE0 | python3-unbound 1.16.2-5.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42923 | NONE0 | python3-unbound 1.16.2-5.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-50251 | NONE0 | python3-unbound 1.16.2-5.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-44431 | NONE0 | python3-urllib3 1.24.2-5.el8_9.2 fixed in 1.24.2-10.el8_10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42534 | NONE0 | unbound-libs 1.16.2-5.el8 fixed in 1.16.2-5.12.el8_10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-44390 | NONE0 | unbound-libs 1.16.2-5.el8 fixed in 1.16.2-5.12.el8_10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-8508 | NONE0 | unbound-libs 1.16.2-5.el8 fixed in 1.16.2-5.8.el8_10 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-32792 | NONE0 | unbound-libs 1.16.2-5.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42923 | NONE0 | unbound-libs 1.16.2-5.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-50251 | NONE0 | unbound-libs 1.16.2-5.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-44656 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-34743 | NONE0 | xz-libs 5.2.4-4.el8_6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-4516 | NONE0 | platform-python 3.6.8-56.el8_9.3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-4516 | NONE0 | python3-libs 3.6.8-56.el8_9.3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42250 | NONE0 | bzip2-libs 1.0.6-26.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-57360 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | glibc 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | glibc 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | glibc-common 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | glibc-common 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | glibc-gconv-extra 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | glibc-gconv-extra 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | glibc-langpack-en 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | glibc-langpack-en 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | glibc-minimal-langpack 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | glibc-minimal-langpack 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-11850 | NONE0 | krb5-libs 1.18.2-26.el8_9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-5917 | NONE0 | libarchive 3.3.3-5.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-34180 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2024-0397 | NONE0 | platform-python 3.6.8-56.el8_9.3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-0397 | NONE0 | python3-libs 3.6.8-56.el8_9.3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-4373 | NONE0 | glib2 2.56.4-161.el8 fixed in 2.56.4-166.el8_10 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-14017 | NONE0 | libcurl 7.61.1-33.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-6004 | NONE0 | libssh 0.9.6-13.el8_9 fixed in 0.9.6-14.el8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6004 | NONE0 | libssh-config 0.9.6-13.el8_9 fixed in 0.9.6-14.el8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | pam 1.3.1-27.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-15282 | NONE0 | platform-python 3.6.8-56.el8_9.3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0672 | NONE0 | platform-python 3.6.8-56.el8_9.3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15282 | NONE0 | python3-libs 3.6.8-56.el8_9.3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0672 | NONE0 | python3-libs 3.6.8-56.el8_9.3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56416 | NONE0 | python3-unbound 1.16.2-5.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-43168 | NONE0 | python3-unbound 1.16.2-5.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56416 | NONE0 | unbound-libs 1.16.2-5.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-43168 | NONE0 | unbound-libs 1.16.2-5.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libblkid 2.32.1-43.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-15224 | NONE0 | libcurl 7.61.1-33.el8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libfdisk 2.32.1-43.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libmount 2.32.1-43.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libsmartcols 2.32.1-43.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-8114 | NONE0 | libssh 0.9.6-13.el8_9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8114 | NONE0 | libssh-config 0.9.6-13.el8_9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libuuid 2.32.1-43.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2021-24032 | NONE0 | libzstd 1.4.4-1.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-13176 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-68160 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | pam 1.3.1-27.el8 fixed in 1.3.1-36.el8_10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-4598 | NONE0 | systemd 239-78.el8 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-4598 | NONE0 | systemd-libs 239-78.el8 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-4598 | NONE0 | systemd-pam 239-78.el8 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-48706 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-43374 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47814 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11468 | NONE0 | platform-python 3.6.8-56.el8_9.3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0865 | NONE0 | platform-python 3.6.8-56.el8_9.3 fixed in 3.6.8-73.el8_10 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-1502 | NONE0 | platform-python 3.6.8-56.el8_9.3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-11468 | NONE0 | python3-libs 3.6.8-56.el8_9.3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0865 | NONE0 | python3-libs 3.6.8-56.el8_9.3 fixed in 3.6.8-73.el8_10 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-1502 | NONE0 | python3-libs 3.6.8-56.el8_9.3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-43802 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-5278 | NONE0 | coreutils-single 8.30-15.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56392 | NONE0 | coreutils-single 8.30-15.el8 fixed in 8.30-20.el8_10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-8905 | NONE0 | file-libs 5.33-25.el8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-8906 | NONE0 | file-libs 5.33-25.el8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-29768 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-28420 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42307 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-9358 | NONE0 | dnf-plugin-subscription-manager 1.28.40-1.el8_9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-6069 | NONE0 | platform-python 3.6.8-56.el8_9.3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-8291 | NONE0 | platform-python 3.6.8-56.el8_9.3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9358 | NONE0 | python3-cloud-what 1.28.40-1.el8_9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-6069 | NONE0 | python3-libs 3.6.8-56.el8_9.3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-8291 | NONE0 | python3-libs 3.6.8-56.el8_9.3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9358 | NONE0 | python3-subscription-manager-rhsm 1.28.40-1.el8_9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-9358 | NONE0 | python3-syspurpose 1.28.40-1.el8_9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-9358 | NONE0 | subscription-manager 1.28.40-1.el8_9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-9358 | NONE0 | subscription-manager-rhsm-certificates 20220623-1.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2018-20839 | NONE0 | systemd 239-78.el8 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-20839 | NONE0 | systemd-libs 239-78.el8 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-20839 | NONE0 | systemd-pam 239-78.el8 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-48231 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-48232 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-48233 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-48234 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-48235 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-48236 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-48237 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-1484 | NONE0 | glib2 2.56.4-161.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-8058 | NONE0 | glibc 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.25 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8058 | NONE0 | glibc-common 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.25 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8058 | NONE0 | glibc-gconv-extra 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.25 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8058 | NONE0 | glibc-langpack-en 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.25 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8058 | NONE0 | glibc-minimal-langpack 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.25 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-45803 | NONE0 | platform-python-pip 9.0.3-23.el8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45803 | NONE0 | python3-pip-wheel 9.0.3-23.el8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-41965 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-26603 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-53905 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 fixed in 2:8.0.1763-21.el8_10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-53906 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 fixed in 2:8.0.1763-21.el8_10 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-25260 | NONE0 | elfutils-default-yama-scope 0.189-3.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-25260 | NONE0 | elfutils-libelf 0.189-3.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-25260 | NONE0 | elfutils-libs 0.189-3.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-33601 | NONE0 | glibc 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.2 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-33602 | NONE0 | glibc 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4438 | NONE0 | glibc 2.28-236.el8_9.12 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-33601 | NONE0 | glibc-common 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.2 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-33602 | NONE0 | glibc-common 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4438 | NONE0 | glibc-common 2.28-236.el8_9.12 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-33601 | NONE0 | glibc-gconv-extra 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.2 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-33602 | NONE0 | glibc-gconv-extra 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4438 | NONE0 | glibc-gconv-extra 2.28-236.el8_9.12 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-33601 | NONE0 | glibc-langpack-en 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.2 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-33602 | NONE0 | glibc-langpack-en 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4438 | NONE0 | glibc-langpack-en 2.28-236.el8_9.12 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-33601 | NONE0 | glibc-minimal-langpack 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.2 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-33602 | NONE0 | glibc-minimal-langpack 2.28-236.el8_9.12 fixed in 2.28-251.el8_10.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4438 | NONE0 | glibc-minimal-langpack 2.28-236.el8_9.12 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-9820 | NONE0 | gnutls 3.6.16-8.el8_9.1 fixed in 3.6.16-8.el8_10.5 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57970 | NONE0 | libarchive 3.3.3-5.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69418 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-15028 | NONE0 | libarchive 3.3.3-5.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-59846 | NONE0 | libssh 0.9.6-13.el8_9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-59846 | NONE0 | libssh-config 0.9.6-13.el8_9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-34397 | NONE0 | glib2 2.56.4-161.el8 fixed in 2.56.4-166.el8_10 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-41080 | NONE0 | expat 2.2.5-11.el8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-3360 | NONE0 | glib2 2.56.4-161.el8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-7039 | NONE0 | glib2 2.56.4-161.el8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0988 | NONE0 | glib2 2.56.4-161.el8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-3832 | NONE0 | gnutls 3.6.16-8.el8_9.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-5419 | NONE0 | gnutls 3.6.16-8.el8_9.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-28322 | NONE0 | libcurl 7.61.1-33.el8 fixed in 7.61.1-33.el8_9.5 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-38546 | NONE0 | libcurl 7.61.1-33.el8 fixed in 7.61.1-33.el8_9.5 | 6.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-0989 | NONE0 | libxml2 2.9.7-18.el8_9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-2511 | NONE0 | openssl-libs 1:1.1.1k-12.el8_9 No fix yet | 54.0% Actively Exploited | Not Applicable |
| CVE-2024-11168 | NONE0 | platform-python 3.6.8-56.el8_9.3 fixed in 3.6.8-69.el8_10 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-4032 | NONE0 | platform-python 3.6.8-56.el8_9.3 fixed in 3.6.8-67.el8_10 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-11168 | NONE0 | python3-libs 3.6.8-56.el8_9.3 fixed in 3.6.8-69.el8_10 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-4032 | NONE0 | python3-libs 3.6.8-56.el8_9.3 fixed in 3.6.8-67.el8_10 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-0989 | NONE0 | python3-libxml2 2.9.7-18.el8_9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-33655 | NONE0 | python3-unbound 1.16.2-5.el8 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2026-42955 | NONE0 | python3-unbound 1.16.2-5.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46582 | NONE0 | python3-unbound 1.16.2-5.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50046 | NONE0 | python3-unbound 1.16.2-5.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-33655 | NONE0 | unbound-libs 1.16.2-5.el8 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2026-42955 | NONE0 | unbound-libs 1.16.2-5.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46582 | NONE0 | unbound-libs 1.16.2-5.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50046 | NONE0 | unbound-libs 1.16.2-5.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-4878 | NONE0 | libssh 0.9.6-13.el8_9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-4878 | NONE0 | libssh-config 0.9.6-13.el8_9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66861 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66862 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-41990 | NONE0 | libgcrypt 1.8.5-7.el8_6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-0965 | NONE0 | libssh 0.9.6-13.el8_9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-0965 | NONE0 | libssh-config 0.9.6-13.el8_9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4519 | NONE0 | platform-python 3.6.8-56.el8_9.3 fixed in 3.6.8-75.el8_10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-13462 | NONE0 | platform-python 3.6.8-56.el8_9.3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-2297 | NONE0 | platform-python 3.6.8-56.el8_9.3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3479 | NONE0 | platform-python 3.6.8-56.el8_9.3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4519 | NONE0 | python3-libs 3.6.8-56.el8_9.3 fixed in 3.6.8-75.el8_10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-13462 | NONE0 | python3-libs 3.6.8-56.el8_9.3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-2297 | NONE0 | python3-libs 3.6.8-56.el8_9.3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3479 | NONE0 | python3-libs 3.6.8-56.el8_9.3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-70873 | NONE0 | sqlite-libs 3.26.0-19.el8_9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-8277 | NONE0 | libssh 0.9.6-13.el8_9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0968 | NONE0 | libssh 0.9.6-13.el8_9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-8277 | NONE0 | libssh-config 0.9.6-13.el8_9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0968 | NONE0 | libssh-config 0.9.6-13.el8_9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-1795 | NONE0 | platform-python 3.6.8-56.el8_9.3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1795 | NONE0 | python3-libs 3.6.8-56.el8_9.3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-16517 | NONE0 | libarchive 3.3.3-5.el8 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-0992 | NONE0 | libxml2 2.9.7-18.el8_9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0992 | NONE0 | python3-libxml2 2.9.7-18.el8_9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69644 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-1485 | NONE0 | glib2 2.56.4-161.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-43167 | NONE0 | python3-unbound 1.16.2-5.el8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-43167 | NONE0 | unbound-libs 1.16.2-5.el8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-24515 | NONE0 | expat 2.2.5-11.el8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6170 | NONE0 | libxml2 2.9.7-18.el8_9 fixed in 2.9.7-21.el8_10.6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6170 | NONE0 | python3-libxml2 2.9.7-18.el8_9 fixed in 2.9.7-21.el8_10.6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28422 | NONE0 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56131 | NONE0 | expat 2.2.5-11.el8 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.