Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker could trigger remote denial of service, memory corruption, or potentially execute arbitrary code via crafted XML, X.509 certificates, or PKCS#7 messages (e.g., CVE-2026-6653, CVE-2026-45447). Although the image is from a popular community publisher and pinned by digest, the exposed surface contains a high number of medium-high severity vulnerabilities. Post-exploit-only findings are lower severity, but the overall risk remains elevated.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-6653 | HIGH8.33 | libxml2 2.9.7-16.el8_8.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | HIGH8.33 | openssl-libs 1:1.1.1k-9.el8_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-32988 | HIGH8.2 | gnutls 3.6.16-7.el8 fixed in 3.6.16-8.el8_10.4 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-5318 | HIGH8.1 | libssh 0.9.6-10.el8_8 fixed in 0.9.6-15.el8_10 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-5318 | HIGH8.1 | libssh-config 0.9.6-10.el8_8 fixed in 0.9.6-15.el8_10 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-17543 | HIGH8.1 | lz4-libs 1.8.3-3.el8_4 fixed in 1.8.3-5.el8_10 | 9.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45447 | HIGH8.1 | openssl-libs 1:1.1.1k-9.el8_7 fixed in 1:1.1.1k-16.el8_6 | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-11023 | HIGH7.93 | libgcc 8.5.0-20.el8 fixed in 8.5.0-23.el8_10 | 83.8% Actively Exploited | Directly Exposed |
| CVE-2020-11023 | HIGH7.93 | libstdc++ 8.5.0-20.el8 fixed in 8.5.0-23.el8_10 | 83.8% Actively Exploited | Directly Exposed |
| CVE-2013-0340 | HIGH7.82 | expat 2.2.5-11.el8 fixed in 2.5.0-1.el8_10 | 20.1% High Exploitation Risk | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | glib2 2.56.4-161.el8 fixed in 2.56.4-170.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33845 | HIGH7.73 | gnutls 3.6.16-7.el8 fixed in 3.6.16-8.el8_10.6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-49794 | HIGH7.73 | libxml2 2.9.7-16.el8_8.1 fixed in 2.9.7-21.el8_10.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-48795 | HIGH7.67 | libssh 0.9.6-10.el8_8 fixed in 0.9.6-13.el8_9 | 93.3% Actively Exploited | Directly Exposed |
| CVE-2023-48795 | HIGH7.67 | libssh-config 0.9.6-10.el8_8 fixed in 0.9.6-13.el8_9 | 93.3% Actively Exploited | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | glibc 2.28-236.el8.7 fixed in 2.28-251.el8_10.2 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | glibc-common 2.28-236.el8.7 fixed in 2.28-251.el8_10.2 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | glibc-gconv-extra 2.28-236.el8.7 fixed in 2.28-251.el8_10.2 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | glibc-langpack-en 2.28-236.el8.7 fixed in 2.28-251.el8_10.2 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | glibc-minimal-langpack 2.28-236.el8.7 fixed in 2.28-251.el8_10.2 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23990 | HIGH7.5 | expat 2.2.5-11.el8 fixed in 2.5.0-1.el8_10 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-52425 | HIGH7.5 | expat 2.2.5-11.el8 fixed in 2.2.5-11.el8_9.1 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28757 | HIGH7.5 | expat 2.2.5-11.el8 fixed in 2.5.0-1.el8_10 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-45490 | HIGH7.5 | expat 2.2.5-11.el8 fixed in 2.2.5-15.el8_10 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-8176 | HIGH7.5 | expat 2.2.5-11.el8 fixed in 2.2.5-17.el8_10 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-43618 | HIGH7.5 | gmp 1:6.1.2-10.el8 fixed in 1:6.1.2-11.el8 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33846 | HIGH7.5 | gnutls 3.6.16-7.el8 fixed in 3.6.16-8.el8_10.6 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42009 | HIGH7.5 | gnutls 3.6.16-7.el8 fixed in 3.6.16-8.el8_10.6 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0553 | HIGH7.5 | gnutls 3.6.16-7.el8 fixed in 3.6.16-8.el8_9.1 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5121 | HIGH7.5 | libarchive 3.3.3-5.el8 fixed in 3.3.3-7.el8_10 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20657 | HIGH7.5 | libgcc 8.5.0-20.el8 No fix yet | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20657 | HIGH7.5 | libstdc++ 8.5.0-20.el8 No fix yet | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-25062 | HIGH7.5 | libxml2 2.9.7-16.el8_8.1 fixed in 2.9.7-18.el8_10.1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-6021 | HIGH7.5 | libxml2 2.9.7-16.el8_8.1 fixed in 2.9.7-21.el8_10.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-27113 | HIGH7.5 | libxml2 2.9.7-16.el8_8.1 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-4899 | HIGH7.5 | libzstd 1.4.4-1.el8 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2953 | HIGH7.5 | openldap 2.4.46-18.el8 fixed in 2.4.46-19.el8_10 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28390 | HIGH7.5 | openssl-libs 1:1.1.1k-9.el8_7 fixed in 1:1.1.1k-17.el8_6 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0464 | HIGH7.5 | openssl-libs 1:1.1.1k-9.el8_7 No fix yet | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28388 | HIGH7.5 | openssl-libs 1:1.1.1k-9.el8_7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28389 | HIGH7.5 | openssl-libs 1:1.1.1k-9.el8_7 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41409 | HIGH7.5 | pcre2 10.32-3.el8_6 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19244 | HIGH7.5 | sqlite-libs 3.26.0-18.el8_8 No fix yet | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9936 | HIGH7.5 | sqlite-libs 3.26.0-18.el8_8 No fix yet | 5.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9937 | HIGH7.5 | sqlite-libs 3.26.0-18.el8_8 No fix yet | 6.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-16866 | HIGH7.5 | unbound-libs 1.16.2-5.el8 No fix yet | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2025-5372 | HIGH7.48 | libssh 0.9.6-10.el8_8 fixed in 0.9.6-16.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-5372 | HIGH7.48 | libssh-config 0.9.6-10.el8_8 fixed in 0.9.6-16.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | glib2 2.56.4-161.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-44690 | HIGH7.31 | unbound-libs 1.16.2-5.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-7104 | HIGH7.3 | sqlite-libs 3.26.0-18.el8_8 fixed in 3.26.0-19.el8_9 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-52533 | HIGH7 | glib2 2.56.4-161.el8 fixed in 2.56.4-166.el8_10 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | glib2 2.56.4-161.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | glib2 2.56.4-161.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | glib2 2.56.4-161.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-32990 | MEDIUM6.97 | gnutls 3.6.16-7.el8 fixed in 3.6.16-8.el8_10.4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42013 | MEDIUM6.97 | gnutls 3.6.16-7.el8 fixed in 3.6.16-8.el8_10.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM6.97 | gnutls 3.6.16-7.el8 fixed in 3.6.16-8.el8_10.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-0966 | MEDIUM6.97 | libssh 0.9.6-10.el8_8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-0966 | MEDIUM6.97 | libssh-config 0.9.6-10.el8_8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-28182 | MEDIUM6.89 | libnghttp2 1.33.0-5.el8_9 fixed in 1.33.0-6.el8_10.1 | 84.8% Actively Exploited | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | openssl-libs 1:1.1.1k-9.el8_7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-2650 | MEDIUM6.76 | openssl-libs 1:1.1.1k-9.el8_7 No fix yet | 75.1% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-37920 | MEDIUM6.66 | 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 | Directly ExposedContext importance: MEDIUM |
| CVE-2025-5914 | MEDIUM6.63 | libarchive 3.3.3-5.el8 fixed in 3.3.3-6.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-25724 | MEDIUM6.63 | libarchive 3.3.3-5.el8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-7425 | MEDIUM6.63 | libxml2 2.9.7-16.el8_8.1 fixed in 2.9.7-21.el8_10.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49043 | MEDIUM6.63 | libxml2 2.9.7-16.el8_8.1 fixed in 2.9.7-18.el8_10.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11979 | MEDIUM6.63 | libxml2 2.9.7-16.el8_8.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13601 | MEDIUM6.54 | glib2 2.56.4-161.el8 fixed in 2.56.4-168.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-24928 | MEDIUM6.54 | libxml2 2.9.7-16.el8_8.1 fixed in 2.9.7-19.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-4209 | MEDIUM6.5 | gnutls 3.6.16-7.el8 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-1000879 | MEDIUM6.5 | libarchive 3.3.3-5.el8 No fix yet | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-1000880 | MEDIUM6.5 | libarchive 3.3.3-5.el8 No fix yet | 4.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-6176 | MEDIUM6.38 | brotli 1.0.6-3.el8 fixed in 1.0.6-4.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45186 | MEDIUM6.38 | expat 2.2.5-11.el8 fixed in 2.5.0-2.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | glib2 2.56.4-161.el8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | glib2 2.56.4-161.el8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-29499 | MEDIUM6.38 | glib2 2.56.4-161.el8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-32636 | MEDIUM6.38 | glib2 2.56.4-161.el8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | krb5-libs 1.18.2-26.el8_9 fixed in 1.18.2-29.el8_10 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | krb5-libs 1.18.2-26.el8_9 fixed in 1.18.2-34.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | krb5-libs 1.18.2-26.el8_9 fixed in 1.18.2-34.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4424 | MEDIUM6.38 | libarchive 3.3.3-5.el8 fixed in 3.3.3-7.el8_10 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-41989 | MEDIUM6.38 | libgcrypt 1.8.5-7.el8_6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27135 | MEDIUM6.38 | libnghttp2 1.33.0-5.el8_9 fixed in 1.33.0-6.el8_10.2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-3731 | MEDIUM6.38 | libssh 0.9.6-10.el8_8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-59847 | MEDIUM6.38 | libssh 0.9.6-10.el8_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59850 | MEDIUM6.38 | libssh 0.9.6-10.el8_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3731 | MEDIUM6.38 | libssh-config 0.9.6-10.el8_8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-59847 | MEDIUM6.38 | libssh-config 0.9.6-10.el8_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59850 | MEDIUM6.38 | libssh-config 0.9.6-10.el8_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-32414 | MEDIUM6.38 | libxml2 2.9.7-16.el8_8.1 fixed in 2.9.7-20.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-32415 | MEDIUM6.38 | libxml2 2.9.7-16.el8_8.1 fixed in 2.9.7-21.el8_10.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6732 | MEDIUM6.38 | libxml2 2.9.7-16.el8_8.1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | openssl-libs 1:1.1.1k-9.el8_7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-5994 | MEDIUM6.38 | unbound-libs 1.16.2-5.el8 fixed in 1.16.2-5.9.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41292 | MEDIUM6.38 | unbound-libs 1.16.2-5.el8 fixed in 1.16.2-5.12.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42944 | MEDIUM6.38 | unbound-libs 1.16.2-5.el8 fixed in 1.16.2-5.11.el8_10 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42959 | MEDIUM6.38 | unbound-libs 1.16.2-5.el8 fixed in 1.16.2-5.11.el8_10 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-40622 | MEDIUM6.38 | unbound-libs 1.16.2-5.el8 fixed in 1.16.2-5.12.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3833 | MEDIUM6.29 | gnutls 3.6.16-7.el8 fixed in 3.6.16-8.el8_10.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM6.29 | gnutls 3.6.16-7.el8 fixed in 3.6.16-8.el8_10.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | openssl-libs 1:1.1.1k-9.el8_7 fixed in 1:1.1.1k-15.el8_6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-1488 | MEDIUM6.21 | unbound-libs 1.16.2-5.el8 fixed in 1.16.2-5.8.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM6.03 | gnutls 3.6.16-7.el8 fixed in 3.6.16-8.el8_10.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | glibc 2.28-236.el8.7 fixed in 2.28-251.el8_10.22 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | glibc-common 2.28-236.el8.7 fixed in 2.28-251.el8_10.22 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | glibc-gconv-extra 2.28-236.el8.7 fixed in 2.28-251.el8_10.22 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | glibc-langpack-en 2.28-236.el8.7 fixed in 2.28-251.el8_10.22 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | glibc-minimal-langpack 2.28-236.el8.7 fixed in 2.28-251.el8_10.22 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-50602 | MEDIUM5.9 | expat 2.2.5-11.el8 fixed in 2.2.5-16.el8_10 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5981 | MEDIUM5.9 | gnutls 3.6.16-7.el8 fixed in 3.6.16-8.el8_9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | krb5-libs 1.18.2-26.el8_9 fixed in 1.18.2-27.el8_10 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-12904 | MEDIUM5.9 | libgcrypt 1.8.5-7.el8_6 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt 1.8.5-7.el8_6 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1 4.13-4.el8_7 fixed in 4.13-6.el8_10 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2408 | MEDIUM5.9 | openssl-libs 1:1.1.1k-9.el8_7 fixed in 1:1.1.1k-12.el8_9 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-41996 | MEDIUM5.9 | openssl-libs 1:1.1.1k-9.el8_7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-5535 | MEDIUM5.9 | openssl-libs 1:1.1.1k-9.el8_7 fixed in 1:1.1.1k-14.el8_6 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-45491 | MEDIUM5.88 | expat 2.2.5-11.el8 fixed in 2.2.5-15.el8_10 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-45492 | MEDIUM5.88 | expat 2.2.5-11.el8 fixed in 2.2.5-15.el8_10 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-56171 | MEDIUM5.88 | libxml2 2.9.7-16.el8_8.1 fixed in 2.9.7-19.el8_10 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56132 | MEDIUM5.87 | expat 2.2.5-11.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM5.87 | expat 2.2.5-11.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56404 | MEDIUM5.87 | expat 2.2.5-11.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56405 | MEDIUM5.87 | expat 2.2.5-11.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM5.87 | expat 2.2.5-11.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56407 | MEDIUM5.87 | expat 2.2.5-11.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | openldap 2.4.46-18.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.61 | gnutls 3.6.16-7.el8 fixed in 3.6.16-8.el8_10.6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5915 | MEDIUM5.61 | libarchive 3.3.3-5.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5918 | MEDIUM5.61 | libarchive 3.3.3-5.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | openssl-libs 1:1.1.1k-9.el8_7 fixed in 1:1.1.1k-14.el8_10 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4741 | MEDIUM5.6 | openssl-libs 1:1.1.1k-9.el8_7 fixed in 1:1.1.1k-16.el8_6 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14512 | MEDIUM5.52 | glib2 2.56.4-161.el8 fixed in 2.56.4-169.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc 2.28-236.el8.7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | glibc 2.28-236.el8.7 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc-common 2.28-236.el8.7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | glibc-common 2.28-236.el8.7 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc-gconv-extra 2.28-236.el8.7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | glibc-gconv-extra 2.28-236.el8.7 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc-langpack-en 2.28-236.el8.7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | glibc-langpack-en 2.28-236.el8.7 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc-minimal-langpack 2.28-236.el8.7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | glibc-minimal-langpack 2.28-236.el8.7 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6395 | MEDIUM5.52 | gnutls 3.6.16-7.el8 fixed in 3.6.16-8.el8_10.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | krb5-libs 1.18.2-26.el8_9 fixed in 1.18.2-31.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4426 | MEDIUM5.52 | libarchive 3.3.3-5.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5351 | MEDIUM5.52 | libssh 0.9.6-10.el8_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-59843 | MEDIUM5.52 | libssh 0.9.6-10.el8_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-59844 | MEDIUM5.52 | libssh 0.9.6-10.el8_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-5351 | MEDIUM5.52 | libssh-config 0.9.6-10.el8_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-59843 | MEDIUM5.52 | libssh-config 0.9.6-10.el8_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-59844 | MEDIUM5.52 | libssh-config 0.9.6-10.el8_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-39615 | MEDIUM5.52 | libxml2 2.9.7-16.el8_8.1 fixed in 2.9.7-18.el8_9 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-45322 | MEDIUM5.52 | libxml2 2.9.7-16.el8_8.1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42771 | MEDIUM5.52 | openssl-libs 1:1.1.1k-9.el8_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-14250 | MEDIUM5.5 | libgcc 8.5.0-20.el8 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-14250 | MEDIUM5.5 | libstdc++ 8.5.0-20.el8 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-1000654 | MEDIUM5.5 | libtasn1 4.13-4.el8_7 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-34459 | MEDIUM5.5 | libxml2 2.9.7-16.el8_8.1 fixed in 2.9.7-21.el8_10.5 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | openssl-libs 1:1.1.1k-9.el8_7 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-49796 | MEDIUM5.46 | libxml2 2.9.7-16.el8_8.1 fixed in 2.9.7-21.el8_10.1 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-0964 | MEDIUM5.35 | libssh 0.9.6-10.el8_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0964 | MEDIUM5.35 | libssh-config 0.9.6-10.el8_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | openssl-libs 1:1.1.1k-9.el8_7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-59375 | MEDIUM5.3 | expat 2.2.5-11.el8 fixed in 2.5.0-1.el8_10 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | glibc 2.28-236.el8.7 fixed in 2.28-251.el8_10.2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | glibc-common 2.28-236.el8.7 fixed in 2.28-251.el8_10.2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | glibc-gconv-extra 2.28-236.el8.7 fixed in 2.28-251.el8_10.2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | glibc-langpack-en 2.28-236.el8.7 fixed in 2.28-251.el8_10.2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | glibc-minimal-langpack 2.28-236.el8.7 fixed in 2.28-251.el8_10.2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-12243 | MEDIUM5.3 | gnutls 3.6.16-7.el8 fixed in 3.6.16-8.el8_10.3 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6918 | MEDIUM5.3 | libssh 0.9.6-10.el8_8 fixed in 0.9.6-14.el8 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6918 | MEDIUM5.3 | libssh-config 0.9.6-10.el8_8 fixed in 0.9.6-14.el8 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-12133 | MEDIUM5.3 | libtasn1 4.13-4.el8_7 fixed in 4.13-5.el8_10 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0466 | MEDIUM5.3 | openssl-libs 1:1.1.1k-9.el8_7 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0465 | MEDIUM5.3 | openssl-libs 1:1.1.1k-9.el8_7 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3446 | MEDIUM5.3 | openssl-libs 1:1.1.1k-9.el8_7 fixed in 1:1.1.1k-12.el8_9 | 6.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3817 | MEDIUM5.3 | openssl-libs 1:1.1.1k-9.el8_7 fixed in 1:1.1.1k-12.el8_9 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5678 | MEDIUM5.3 | openssl-libs 1:1.1.1k-9.el8_7 fixed in 1:1.1.1k-12.el8_9 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-1757 | MEDIUM5.27 | libxml2 2.9.7-16.el8_8.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | p11-kit 0.23.22-1.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | p11-kit-trust 0.23.22-1.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11411 | MEDIUM5.18 | unbound-libs 1.16.2-5.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-2650 | MEDIUM5.07 | openssl 1:1.1.1k-9.el8_7 No fix yet | 75.1% Actively Exploited | Post-Exploit |
| CVE-2026-50219 | MEDIUM5.02 | expat 2.2.5-11.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56412 | MEDIUM5.02 | expat 2.2.5-11.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc 2.28-236.el8.7 fixed in 2.28-251.el8_10.40 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | glibc 2.28-236.el8.7 fixed in 2.28-251.el8_10.31 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc-common 2.28-236.el8.7 fixed in 2.28-251.el8_10.40 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | glibc-common 2.28-236.el8.7 fixed in 2.28-251.el8_10.31 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc-gconv-extra 2.28-236.el8.7 fixed in 2.28-251.el8_10.40 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | glibc-gconv-extra 2.28-236.el8.7 fixed in 2.28-251.el8_10.31 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc-langpack-en 2.28-236.el8.7 fixed in 2.28-251.el8_10.40 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | glibc-langpack-en 2.28-236.el8.7 fixed in 2.28-251.el8_10.31 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc-minimal-langpack 2.28-236.el8.7 fixed in 2.28-251.el8_10.40 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | glibc-minimal-langpack 2.28-236.el8.7 fixed in 2.28-251.el8_10.31 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | krb5-libs 1.18.2-26.el8_9 fixed in 1.18.2-32.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | krb5-libs 1.18.2-26.el8_9 fixed in 1.18.2-27.el8_10 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-59845 | MEDIUM5.02 | libssh 0.9.6-10.el8_8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-59845 | MEDIUM5.02 | libssh-config 0.9.6-10.el8_8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0990 | MEDIUM5.02 | libxml2 2.9.7-16.el8_8.1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-15468 | MEDIUM5.02 | openssl-libs 1:1.1.1k-9.el8_7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | openssl-libs 1:1.1.1k-9.el8_7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | openssl-libs 1:1.1.1k-9.el8_7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | openssl-libs 1:1.1.1k-9.el8_7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | openssl-libs 1:1.1.1k-9.el8_7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44608 | MEDIUM5.02 | unbound-libs 1.16.2-5.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-55990 | MEDIUM5.02 | unbound-libs 1.16.2-5.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | MEDIUM5 | openssl 1:1.1.1k-9.el8_7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-34180 | MEDIUM5 | openssl-libs 1:1.1.1k-9.el8_7 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45447 | MEDIUM4.86 | openssl 1:1.1.1k-9.el8_7 fixed in 1:1.1.1k-16.el8_6 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2511 | MEDIUM4.81 | openssl-libs 1:1.1.1k-9.el8_7 No fix yet | 54.0% Actively Exploited | Directly Exposed |
| CVE-2025-5916 | MEDIUM4.76 | libarchive 3.3.3-5.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-20225 | MEDIUM4.68 | platform-python-pip 9.0.3-23.el8 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20225 | MEDIUM4.68 | python3-pip-wheel 9.0.3-23.el8 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3927 | MEDIUM4.68 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3974 | MEDIUM4.68 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1619 | MEDIUM4.68 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1720 | MEDIUM4.68 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2124 | MEDIUM4.68 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2125 | MEDIUM4.68 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2126 | MEDIUM4.68 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2129 | MEDIUM4.68 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2175 | MEDIUM4.68 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2182 | MEDIUM4.68 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2183 | MEDIUM4.68 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2206 | MEDIUM4.68 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2207 | MEDIUM4.68 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2210 | MEDIUM4.68 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2284 | MEDIUM4.68 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2285 | MEDIUM4.68 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2286 | MEDIUM4.68 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2343 | MEDIUM4.68 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2344 | MEDIUM4.68 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2345 | MEDIUM4.68 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-32776 | MEDIUM4.67 | expat 2.2.5-11.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | MEDIUM4.67 | expat 2.2.5-11.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | MEDIUM4.67 | expat 2.2.5-11.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | expat 2.2.5-11.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-32611 | MEDIUM4.67 | glib2 2.56.4-161.el8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-32665 | MEDIUM4.67 | glib2 2.56.4-161.el8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | glibc 2.28-236.el8.7 fixed in 2.28-251.el8_10.16 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | glibc-common 2.28-236.el8.7 fixed in 2.28-251.el8_10.16 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | glibc-gconv-extra 2.28-236.el8.7 fixed in 2.28-251.el8_10.16 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | glibc-langpack-en 2.28-236.el8.7 fixed in 2.28-251.el8_10.16 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | glibc-minimal-langpack 2.28-236.el8.7 fixed in 2.28-251.el8_10.16 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-60753 | MEDIUM4.67 | libarchive 3.3.3-5.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5745 | MEDIUM4.67 | libarchive 3.3.3-5.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1632 | MEDIUM4.67 | libarchive 3.3.3-5.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc 8.5.0-20.el8 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-0967 | MEDIUM4.67 | libssh 0.9.6-10.el8_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0967 | MEDIUM4.67 | libssh-config 0.9.6-10.el8_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libstdc++ 8.5.0-20.el8 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-9714 | MEDIUM4.67 | libxml2 2.9.7-16.el8_8.1 fixed in 2.9.7-21.el8_10.4 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15469 | MEDIUM4.67 | openssl-libs 1:1.1.1k-9.el8_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM4.67 | openssl-libs 1:1.1.1k-9.el8_7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | openssl-libs 1:1.1.1k-9.el8_7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-0232 | MEDIUM4.67 | sqlite-libs 3.26.0-18.el8_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib 1.2.11-25.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| 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-1489 | MEDIUM4.59 | glib2 2.56.4-161.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58055 | MEDIUM4.59 | libnghttp2 1.33.0-5.el8_9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4517 | MEDIUM4.56 | platform-python 3.6.8-56.el8_9 fixed in 3.6.8-70.el8_10 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28390 | MEDIUM4.5 | openssl 1:1.1.1k-9.el8_7 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-9.el8_7 No fix yet | 3.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28388 | MEDIUM4.5 | openssl 1:1.1.1k-9.el8_7 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28389 | MEDIUM4.5 | openssl 1:1.1.1k-9.el8_7 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-4138 | MEDIUM4.5 | platform-python 3.6.8-56.el8_9 fixed in 3.6.8-70.el8_10 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-48560 | MEDIUM4.5 | platform-python 3.6.8-56.el8_9 fixed in 3.6.8-56.el8_9.2 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2024-6232 | MEDIUM4.5 | platform-python 3.6.8-56.el8_9 fixed in 3.6.8-67.el8_10 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9674 | MEDIUM4.5 | platform-python 3.6.8-56.el8_9 No fix yet | 5.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-7592 | MEDIUM4.5 | platform-python 3.6.8-56.el8_9 No fix yet | 2.3% 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-2018-20786 | MEDIUM4.5 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-3705 | MEDIUM4.5 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5344 | MEDIUM4.5 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-15588 | MEDIUM4.5 | glib2 2.56.4-161.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | glibc 2.28-236.el8.7 fixed in 2.28-251.el8_10.31 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc 2.28-236.el8.7 fixed in 2.28-251.el8_10.37 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | glibc-common 2.28-236.el8.7 fixed in 2.28-251.el8_10.31 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-common 2.28-236.el8.7 fixed in 2.28-251.el8_10.37 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | glibc-gconv-extra 2.28-236.el8.7 fixed in 2.28-251.el8_10.31 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-gconv-extra 2.28-236.el8.7 fixed in 2.28-251.el8_10.37 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | glibc-langpack-en 2.28-236.el8.7 fixed in 2.28-251.el8_10.31 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-langpack-en 2.28-236.el8.7 fixed in 2.28-251.el8_10.37 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | glibc-minimal-langpack 2.28-236.el8.7 fixed in 2.28-251.el8_10.31 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-minimal-langpack 2.28-236.el8.7 fixed in 2.28-251.el8_10.37 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-28834 | MEDIUM4.5 | gnutls 3.6.16-7.el8 fixed in 3.6.16-8.el8_9.3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-14831 | MEDIUM4.5 | gnutls 3.6.16-7.el8 fixed in 3.6.16-8.el8_10.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM4.5 | gnutls 3.6.16-7.el8 fixed in 3.6.16-8.el8_10.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-59848 | MEDIUM4.5 | libssh 0.9.6-10.el8_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59848 | MEDIUM4.5 | libssh-config 0.9.6-10.el8_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | openssl-libs 1:1.1.1k-9.el8_7 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42534 | MEDIUM4.5 | unbound-libs 1.16.2-5.el8 fixed in 1.16.2-5.12.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44390 | MEDIUM4.5 | unbound-libs 1.16.2-5.el8 fixed in 1.16.2-5.12.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-8508 | MEDIUM4.5 | unbound-libs 1.16.2-5.el8 fixed in 1.16.2-5.8.el8_10 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-32792 | MEDIUM4.5 | unbound-libs 1.16.2-5.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42923 | MEDIUM4.5 | unbound-libs 1.16.2-5.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-50251 | MEDIUM4.5 | unbound-libs 1.16.2-5.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | xz-libs 5.2.4-4.el8_6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-47162 | MEDIUM4.49 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-7264 | MEDIUM4.48 | curl 7.61.1-33.el8 No fix yet | 17.3% High Exploitation Risk | Post-Exploit |
| CVE-2024-7264 | MEDIUM4.48 | libcurl 7.61.1-33.el8 No fix yet | 17.3% High Exploitation Risk | Post-Exploit |
| CVE-2021-4166 | MEDIUM4.26 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2287 | MEDIUM4.26 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42250 | MEDIUM4.25 | bzip2-libs 1.0.6-26.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc 2.28-236.el8.7 fixed in 2.28-251.el8_10.38 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc 2.28-236.el8.7 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-common 2.28-236.el8.7 fixed in 2.28-251.el8_10.38 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc-common 2.28-236.el8.7 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-gconv-extra 2.28-236.el8.7 fixed in 2.28-251.el8_10.38 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc-gconv-extra 2.28-236.el8.7 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-langpack-en 2.28-236.el8.7 fixed in 2.28-251.el8_10.38 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc-langpack-en 2.28-236.el8.7 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-minimal-langpack 2.28-236.el8.7 fixed in 2.28-251.el8_10.38 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc-minimal-langpack 2.28-236.el8.7 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | krb5-libs 1.18.2-26.el8_9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5917 | MEDIUM4.25 | libarchive 3.3.3-5.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34982 | MEDIUM4.18 | vim-minimal 2:8.0.1763-19.el8_6.4 fixed in 2:8.0.1763-22.el8_10.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-52859 | MEDIUM4.18 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.3% Theoretical Threat | 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-8286 | MEDIUM4.13 | libcurl 7.61.1-33.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl 7.61.1-33.el8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-28387 | MEDIUM4.13 | openssl 1:1.1.1k-9.el8_7 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | MEDIUM4.13 | platform-python 3.6.8-56.el8_9 fixed in 3.6.8-76.el8_10 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-2961 | MEDIUM4.12 | glibc 2.28-236.el8.7 fixed in 2.28-251.el8_10.1 | 88.3% Actively Exploited | Post-Exploit |
| CVE-2024-2961 | MEDIUM4.12 | glibc-common 2.28-236.el8.7 fixed in 2.28-251.el8_10.1 | 88.3% Actively Exploited | Post-Exploit |
| CVE-2024-2961 | MEDIUM4.12 | glibc-gconv-extra 2.28-236.el8.7 fixed in 2.28-251.el8_10.1 | 88.3% Actively Exploited | Post-Exploit |
| CVE-2024-2961 | MEDIUM4.12 | glibc-langpack-en 2.28-236.el8.7 fixed in 2.28-251.el8_10.1 | 88.3% Actively Exploited | Post-Exploit |
| CVE-2024-2961 | MEDIUM4.12 | glibc-minimal-langpack 2.28-236.el8.7 fixed in 2.28-251.el8_10.1 | 88.3% Actively Exploited | Post-Exploit |
| CVE-2025-0938 | MEDIUM4.08 | platform-python 3.6.8-56.el8_9 fixed in 3.6.8-74.el8_10 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-4373 | MEDIUM4.08 | glib2 2.56.4-161.el8 fixed in 2.56.4-166.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-6004 | MEDIUM4.08 | libssh 0.9.6-10.el8_8 fixed in 0.9.6-14.el8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-6004 | MEDIUM4.08 | libssh-config 0.9.6-10.el8_8 fixed in 0.9.6-14.el8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56416 | MEDIUM4.08 | unbound-libs 1.16.2-5.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-43168 | MEDIUM4.08 | unbound-libs 1.16.2-5.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8114 | MEDIUM4 | libssh 0.9.6-10.el8_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8114 | MEDIUM4 | libssh-config 0.9.6-10.el8_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-24032 | MEDIUM4 | libzstd 1.4.4-1.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | openssl-libs 1:1.1.1k-9.el8_7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4 | openssl-libs 1:1.1.1k-9.el8_7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | glibc 2.28-236.el8.7 fixed in 2.28-251.el8_10.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | glibc-common 2.28-236.el8.7 fixed in 2.28-251.el8_10.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | glibc-gconv-extra 2.28-236.el8.7 fixed in 2.28-251.el8_10.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | glibc-langpack-en 2.28-236.el8.7 fixed in 2.28-251.el8_10.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | glibc-minimal-langpack 2.28-236.el8.7 fixed in 2.28-251.el8_10.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-6846 | LOW3.98 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-6597 | LOW3.98 | platform-python 3.6.8-56.el8_9 fixed in 3.6.8-62.el8_10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-9287 | LOW3.98 | platform-python 3.6.8-56.el8_9 fixed in 3.6.8-69.el8_10 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-55895 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-39881 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-59856 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-0351 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-2522 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-2819 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-2845 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2849 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2946 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3037 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3234 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3235 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3256 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3296 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3352 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-4292 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-0049 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-0054 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-0288 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-0433 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-0512 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-1127 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-2610 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-4733 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-4734 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4735 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4738 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4750 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-4751 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4752 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4781 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-5535 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-22667 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1215 | LOW3.98 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% 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-2023-46218 | LOW3.9 | libcurl 7.61.1-33.el8 fixed in 7.61.1-33.el8_9.5 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-48564 | LOW3.9 | platform-python 3.6.8-56.el8_9 fixed in 3.6.8-56.el8_9.2 | 1.4% 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-2024-12718 | LOW3.88 | platform-python 3.6.8-56.el8_9 fixed in 3.6.8-70.el8_10 | 0.6% Theoretical Threat | 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-66864 | LOW3.82 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl 7.61.1-33.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl 7.61.1-33.el8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl 7.61.1-33.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl 7.61.1-33.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69421 | LOW3.82 | openssl 1:1.1.1k-9.el8_7 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-15308 | LOW3.82 | platform-python 3.6.8-56.el8_9 fixed in 3.6.8-77.el8_10 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-4435 | LOW3.82 | platform-python 3.6.8-56.el8_9 fixed in 3.6.8-70.el8_10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8194 | LOW3.82 | platform-python 3.6.8-56.el8_9 fixed in 3.6.8-71.el8_10 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3644 | LOW3.82 | platform-python 3.6.8-56.el8_9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW3.82 | platform-python 3.6.8-56.el8_9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW3.82 | platform-python 3.6.8-56.el8_9 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-26269 | LOW3.82 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-56131 | LOW3.82 | expat 2.2.5-11.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | LOW3.77 | openssl 1:1.1.1k-9.el8_7 fixed in 1:1.1.1k-15.el8_6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2019-8905 | LOW3.74 | file-libs 5.33-25.el8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-8906 | LOW3.74 | file-libs 5.33-25.el8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-3596 | LOW3.73 | krb5-libs 1.18.2-26.el8_9 fixed in 1.18.2-30.el8_10 | 14.9% High Exploitation Risk | Post-Exploit |
| CVE-2025-4330 | LOW3.72 | platform-python 3.6.8-56.el8_9 fixed in 3.6.8-70.el8_10 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-25749 | LOW3.72 | vim-minimal 2:8.0.1763-19.el8_6.4 fixed in 2:8.0.1763-22.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41411 | LOW3.72 | vim-minimal 2:8.0.1763-19.el8_6.4 fixed in 2:8.0.1763-24.el8_10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-33655 | LOW3.7 | unbound-libs 1.16.2-5.el8 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-31879 | LOW3.66 | wget 1.19.5-11.el8 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2023-4156 | LOW3.62 | gawk 4.2.1-4.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4786 | LOW3.62 | platform-python 3.6.8-56.el8_9 fixed in 3.6.8-76.el8_10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW3.62 | platform-python 3.6.8-56.el8_9 fixed in 3.6.8-73.el8_10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW3.62 | platform-python 3.6.8-56.el8_9 fixed in 3.6.8-73.el8_10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1299 | LOW3.62 | platform-python 3.6.8-56.el8_9 fixed in 3.6.8-73.el8_10 | 0.6% Theoretical Threat | 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-6965 | LOW3.61 | sqlite-libs 3.26.0-18.el8_8 fixed in 3.26.0-20.el8_10 | 74.4% Actively Exploited | Post-Exploit |
| CVE-2005-2541 | LOW3.6 | tar 2:1.30-9.el8 No fix yet | 4.0% Low-Moderate Risk | 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-26.el8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-46483 | LOW3.57 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-1484 | LOW3.57 | glib2 2.56.4-161.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | glibc 2.28-236.el8.7 fixed in 2.28-251.el8_10.25 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | glibc-common 2.28-236.el8.7 fixed in 2.28-251.el8_10.25 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | glibc-gconv-extra 2.28-236.el8.7 fixed in 2.28-251.el8_10.25 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | glibc-langpack-en 2.28-236.el8.7 fixed in 2.28-251.el8_10.25 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | glibc-minimal-langpack 2.28-236.el8.7 fixed in 2.28-251.el8_10.25 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-11053 | LOW3.54 | curl 7.61.1-33.el8 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | gdb-gdbserver 8.2-20.el8 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-11053 | LOW3.54 | libcurl 7.61.1-33.el8 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2408 | LOW3.54 | openssl 1:1.1.1k-9.el8_7 fixed in 1:1.1.1k-12.el8_9 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-41996 | LOW3.54 | openssl 1:1.1.1k-9.el8_7 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-5535 | LOW3.54 | openssl 1:1.1.1k-9.el8_7 fixed in 1:1.1.1k-14.el8_6 | 5.6% Low-Moderate Risk | Post-Exploit |
| CVE-2019-12900 | LOW3.53 | bzip2-libs 1.0.6-26.el8 fixed in 1.0.6-28.el8_10 | 8.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42010 | LOW3.53 | gnutls 3.6.16-7.el8 fixed in 3.6.16-8.el8_10.6 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2020-20703 | LOW3.53 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-50387 | LOW3.51 | unbound-libs 1.16.2-5.el8 fixed in 1.16.2-5.el8_9.2 | 100.0% Actively Exploited | Post-Exploit |
| CVE-2023-50868 | LOW3.51 | unbound-libs 1.16.2-5.el8 fixed in 1.16.2-5.el8_9.2 | 81.7% Actively Exploited | 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-13034 | LOW3.47 | libcurl 7.61.1-33.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl 7.61.1-33.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-6923 | LOW3.47 | platform-python 3.6.8-56.el8_9 fixed in 3.6.8-67.el8_10 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2021-35938 | LOW3.42 | rpm 4.14.3-26.el8 fixed in 4.14.3-28.el8_9 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2021-35939 | LOW3.42 | rpm 4.14.3-26.el8 fixed in 4.14.3-28.el8_9 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-33602 | LOW3.4 | glibc 2.28-236.el8.7 fixed in 2.28-251.el8_10.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | glibc 2.28-236.el8.7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | glibc-common 2.28-236.el8.7 fixed in 2.28-251.el8_10.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | glibc-common 2.28-236.el8.7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | glibc-gconv-extra 2.28-236.el8.7 fixed in 2.28-251.el8_10.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | glibc-gconv-extra 2.28-236.el8.7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | glibc-langpack-en 2.28-236.el8.7 fixed in 2.28-251.el8_10.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | glibc-langpack-en 2.28-236.el8.7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | glibc-minimal-langpack 2.28-236.el8.7 fixed in 2.28-251.el8_10.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | glibc-minimal-langpack 2.28-236.el8.7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-9820 | LOW3.4 | gnutls 3.6.16-7.el8 fixed in 3.6.16-8.el8_10.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57970 | LOW3.4 | libarchive 3.3.3-5.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW3.4 | openssl-libs 1:1.1.1k-9.el8_7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28419 | LOW3.37 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-1170 | LOW3.37 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-1175 | LOW3.37 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-9230 | LOW3.36 | openssl 1:1.1.1k-9.el8_7 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-9.el8_7 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-11856 | LOW3.31 | libcurl 7.61.1-33.el8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl 7.61.1-33.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl 7.61.1-33.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl 7.61.1-33.el8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl 7.61.1-33.el8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl 7.61.1-33.el8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42771 | LOW3.31 | openssl 1:1.1.1k-9.el8_7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW3.31 | platform-python 3.6.8-56.el8_9 No fix yet | 0.4% 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-2026-15028 | LOW3.31 | libarchive 3.3.3-5.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59846 | LOW3.31 | libssh 0.9.6-10.el8_8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-59846 | LOW3.31 | libssh-config 0.9.6-10.el8_8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-0727 | LOW3.3 | openssl 1:1.1.1k-9.el8_7 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-44605 | LOW3.3 | rpm 4.14.3-26.el8 No fix yet | — | Post-Exploit |
| CVE-2022-2208 | LOW3.3 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-37371 | LOW3.28 | krb5-libs 1.18.2-26.el8_9 fixed in 1.18.2-29.el8_10 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2021-35937 | LOW3.26 | rpm 4.14.3-26.el8 fixed in 4.14.3-28.el8_9 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-34397 | LOW3.23 | glib2 2.56.4-161.el8 fixed in 2.56.4-166.el8_10 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | LOW3.21 | openssl 1:1.1.1k-9.el8_7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-5958 | LOW3.21 | sed 4.5-5.el8 No fix yet | 0.1% 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-2025-9086 | LOW3.18 | libcurl 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-9.el8_7 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0465 | LOW3.18 | openssl 1:1.1.1k-9.el8_7 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-3446 | LOW3.18 | openssl 1:1.1.1k-9.el8_7 fixed in 1:1.1.1k-12.el8_9 | 6.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-3817 | LOW3.18 | openssl 1:1.1.1k-9.el8_7 fixed in 1:1.1.1k-12.el8_9 | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5678 | LOW3.18 | openssl 1:1.1.1k-9.el8_7 fixed in 1:1.1.1k-12.el8_9 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27043 | LOW3.18 | platform-python 3.6.8-56.el8_9 fixed in 3.6.8-56.el8_9.3 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27534 | LOW3.17 | curl 7.61.1-33.el8 No fix yet | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27534 | LOW3.17 | libcurl 7.61.1-33.el8 No fix yet | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-6345 | LOW3.17 | platform-python-setuptools 39.2.0-7.el8 fixed in 39.2.0-8.el8_10 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2025-47273 | LOW3.17 | platform-python-setuptools 39.2.0-7.el8 fixed in 39.2.0-9.el8_10 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-6345 | LOW3.17 | python3-setuptools-wheel 39.2.0-7.el8 fixed in 39.2.0-8.el8_10 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2025-47273 | LOW3.17 | python3-setuptools-wheel 39.2.0-7.el8 fixed in 39.2.0-9.el8_10 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-0450 | LOW3.16 | platform-python 3.6.8-56.el8_9 fixed in 3.6.8-62.el8_10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41080 | LOW3.15 | expat 2.2.5-11.el8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-3360 | LOW3.15 | glib2 2.56.4-161.el8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-7039 | LOW3.15 | glib2 2.56.4-161.el8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0988 | LOW3.15 | glib2 2.56.4-161.el8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3832 | LOW3.15 | gnutls 3.6.16-7.el8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-5419 | LOW3.15 | gnutls 3.6.16-7.el8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0989 | LOW3.15 | libxml2 2.9.7-16.el8_8.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42955 | LOW3.15 | unbound-libs 1.16.2-5.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46582 | LOW3.15 | unbound-libs 1.16.2-5.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50046 | LOW3.15 | unbound-libs 1.16.2-5.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56391 | LOW3.11 | coreutils-single 8.30-15.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.11 | platform-python 3.6.8-56.el8_9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-50181 | LOW3.11 | platform-python-pip 9.0.3-23.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-50182 | LOW3.11 | platform-python-pip 9.0.3-23.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-50181 | LOW3.11 | python3-pip-wheel 9.0.3-23.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-50182 | LOW3.11 | python3-pip-wheel 9.0.3-23.el8 No fix yet | 0.3% Theoretical Threat | 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-2024-2398 | LOW3.1 | curl 7.61.1-33.el8 fixed in 7.61.1-34.el8_10.2 | 36.1% High Exploitation Risk | Post-Exploit |
| CVE-2024-2398 | LOW3.1 | libcurl 7.61.1-33.el8 fixed in 7.61.1-34.el8_10.2 | 36.1% High Exploitation Risk | Post-Exploit |
| CVE-2026-42960 | LOW3.06 | unbound-libs 1.16.2-5.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5713 | LOW3.06 | platform-python 3.6.8-56.el8_9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-4878 | LOW3.06 | libssh 0.9.6-10.el8_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4878 | LOW3.06 | libssh-config 0.9.6-10.el8_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15468 | LOW3.01 | openssl 1:1.1.1k-9.el8_7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-69420 | LOW3.01 | openssl 1:1.1.1k-9.el8_7 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-22796 | LOW3.01 | openssl 1:1.1.1k-9.el8_7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW3.01 | openssl 1:1.1.1k-9.el8_7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.01 | openssl 1:1.1.1k-9.el8_7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-13346 | LOW3.01 | platform-python-pip 9.0.3-23.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-13346 | LOW3.01 | python3-pip-wheel 9.0.3-23.el8 No fix yet | 0.3% 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-2025-14087 | LOW3 | glib2 2.56.4-161.el8 fixed in 2.56.4-169.el8_10 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-34180 | LOW3 | openssl 1:1.1.1k-9.el8_7 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-2026-3783 | LOW2.91 | libcurl 7.61.1-33.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-2511 | LOW2.89 | openssl 1:1.1.1k-9.el8_7 No fix yet | 54.0% Actively Exploited | Post-Exploit |
| CVE-2026-15003 | LOW2.86 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-45582 | LOW2.86 | tar 2:1.30-9.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-47007 | LOW2.8 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47010 | LOW2.8 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47011 | LOW2.8 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% 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-9.el8_7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-22795 | LOW2.8 | openssl 1:1.1.1k-9.el8_7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW2.8 | openssl 1:1.1.1k-9.el8_7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-13837 | LOW2.8 | platform-python 3.6.8-56.el8_9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42308 | LOW2.8 | platform-python 3.6.8-56.el8_9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-6075 | LOW2.8 | platform-python 3.6.8-56.el8_9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-25645 | LOW2.8 | platform-python-pip 9.0.3-23.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-25645 | LOW2.8 | python3-pip-wheel 9.0.3-23.el8 No fix yet | 0.2% 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-28418 | LOW2.8 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45130 | LOW2.8 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55892 | LOW2.8 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-59857 | LOW2.8 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-3236 | LOW2.8 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-2923 | LOW2.8 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2980 | LOW2.8 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2022-3153 | LOW2.8 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-4293 | LOW2.8 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-1264 | LOW2.8 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-2609 | LOW2.8 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-46246 | LOW2.8 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-5441 | LOW2.8 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-45306 | LOW2.8 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-22134 | LOW2.8 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-24014 | LOW2.8 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41990 | LOW2.8 | libgcrypt 1.8.5-7.el8_6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0965 | LOW2.8 | libssh 0.9.6-10.el8_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0965 | LOW2.8 | libssh-config 0.9.6-10.el8_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | sqlite-libs 3.26.0-18.el8_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| 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-4873 | LOW2.7 | libcurl 7.61.1-33.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl 7.61.1-33.el8 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl 7.61.1-33.el8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42766 | LOW2.7 | openssl 1:1.1.1k-9.el8_7 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2025-12084 | LOW2.7 | platform-python 3.6.8-56.el8_9 fixed in 3.6.8-72.el8_10 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW2.7 | platform-python 3.6.8-56.el8_9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW2.7 | platform-python 3.6.8-56.el8_9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4360 | LOW2.7 | platform-python 3.6.8-56.el8_9 No fix yet | 0.3% 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-44656 | LOW2.7 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.9% 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-8277 | LOW2.63 | libssh 0.9.6-10.el8_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0968 | LOW2.63 | libssh 0.9.6-10.el8_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-8277 | LOW2.63 | libssh-config 0.9.6-10.el8_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0968 | LOW2.63 | libssh-config 0.9.6-10.el8_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-4516 | LOW2.6 | platform-python 3.6.8-56.el8_9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-0397 | LOW2.55 | platform-python 3.6.8-56.el8_9 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-16517 | LOW2.46 | libarchive 3.3.3-5.el8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0992 | LOW2.46 | libxml2 2.9.7-16.el8_8.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14017 | LOW2.45 | curl 7.61.1-33.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl 7.61.1-33.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | LOW2.45 | platform-python 3.6.8-56.el8_9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.45 | platform-python 3.6.8-56.el8_9 No fix yet | 0.4% 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-2025-15224 | LOW2.4 | libcurl 7.61.1-33.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-13176 | LOW2.4 | openssl 1:1.1.1k-9.el8_7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-68160 | LOW2.4 | openssl 1:1.1.1k-9.el8_7 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-48706 | LOW2.4 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-43374 | LOW2.4 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-47814 | LOW2.4 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1485 | LOW2.38 | glib2 2.56.4-161.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-43167 | LOW2.38 | unbound-libs 1.16.2-5.el8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | LOW2.29 | platform-python 3.6.8-56.el8_9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0865 | LOW2.29 | platform-python 3.6.8-56.el8_9 fixed in 3.6.8-73.el8_10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW2.29 | platform-python 3.6.8-56.el8_9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-43802 | LOW2.29 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils-single 8.30-15.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW2.24 | coreutils-single 8.30-15.el8 fixed in 8.30-20.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-29768 | LOW2.24 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-28420 | LOW2.24 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42307 | LOW2.24 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.8% 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-2023-28322 | LOW2.22 | libcurl 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 | libcurl 7.61.1-33.el8 fixed in 7.61.1-33.el8_9.5 | 6.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4032 | LOW2.22 | platform-python 3.6.8-56.el8_9 fixed in 3.6.8-67.el8_10 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-6069 | LOW2.19 | platform-python 3.6.8-56.el8_9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8291 | LOW2.19 | platform-python 3.6.8-56.el8_9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-48231 | LOW2.19 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48232 | LOW2.19 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48233 | LOW2.19 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48234 | LOW2.19 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48235 | LOW2.19 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48236 | LOW2.19 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48237 | LOW2.19 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-45803 | LOW2.14 | platform-python-pip 9.0.3-23.el8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-45803 | LOW2.14 | python3-pip-wheel 9.0.3-23.el8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-41965 | LOW2.14 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-26603 | LOW2.14 | vim-minimal 2:8.0.1763-19.el8_6.4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-24515 | LOW2.12 | expat 2.2.5-11.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6170 | LOW2.12 | libxml2 2.9.7-16.el8_8.1 fixed in 2.9.7-21.el8_10.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-53905 | LOW2.09 | vim-minimal 2:8.0.1763-19.el8_6.4 fixed in 2:8.0.1763-21.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-53906 | LOW2.09 | vim-minimal 2:8.0.1763-19.el8_6.4 fixed in 2:8.0.1763-21.el8_10 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-69418 | LOW2.04 | openssl 1:1.1.1k-9.el8_7 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-2025-1152 | LOW1.89 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-11168 | LOW1.89 | platform-python 3.6.8-56.el8_9 fixed in 3.6.8-69.el8_10 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | shadow-utils 2:4.6-19.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% 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-2026-4519 | LOW1.68 | platform-python 3.6.8-56.el8_9 fixed in 3.6.8-75.el8_10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW1.68 | platform-python 3.6.8-56.el8_9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.68 | platform-python 3.6.8-56.el8_9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | platform-python 3.6.8-56.el8_9 No fix yet | 0.2% 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-2025-1150 | LOW1.58 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1795 | LOW1.58 | platform-python 3.6.8-56.el8_9 No fix yet | 0.6% 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-2025-69644 | LOW1.43 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-28422 | LOW1.12 | vim-minimal 2:8.0.1763-19.el8_6.4 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-2024-56171 | NONE0 | python3-libxml2 2.9.7-16.el8_8.1 fixed in 2.9.7-19.el8_10 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-6653 | NONE0 | python3-libxml2 2.9.7-16.el8_8.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-49794 | NONE0 | python3-libxml2 2.9.7-16.el8_8.1 fixed in 2.9.7-21.el8_10.1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-49796 | NONE0 | python3-libxml2 2.9.7-16.el8_8.1 fixed in 2.9.7-21.el8_10.1 | 1.5% Low-Moderate Risk | 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-2026-44690 | NONE0 | python3-unbound 1.16.2-5.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6100 | NONE0 | python3-libs 3.6.8-56.el8_9 fixed in 3.6.8-76.el8_10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-43804 | NONE0 | python3-urllib3 1.24.2-5.el8 fixed in 1.24.2-5.el8_9.2 | 1.2% Low-Moderate Risk | 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-48864 | NONE0 | libsolv 0.7.20-6.el8 fixed in 0.7.20-7.el8_10 | 0.2% 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 | python3-libs 3.6.8-56.el8_9 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 fixed in 3.6.8-69.el8_10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-7425 | NONE0 | python3-libxml2 2.9.7-16.el8_8.1 fixed in 2.9.7-21.el8_10.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49043 | NONE0 | python3-libxml2 2.9.7-16.el8_8.1 fixed in 2.9.7-18.el8_10.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11979 | NONE0 | python3-libxml2 2.9.7-16.el8_8.1 No fix yet | 0.1% Theoretical Threat | 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-2025-24928 | NONE0 | python3-libxml2 2.9.7-16.el8_8.1 fixed in 2.9.7-19.el8_10 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-12718 | NONE0 | python3-libs 3.6.8-56.el8_9 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 fixed in 3.6.8-70.el8_10 | 1.2% Low-Moderate Risk | 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-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-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 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 fixed in 3.6.8-77.el8_10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-48560 | NONE0 | python3-libs 3.6.8-56.el8_9 fixed in 3.6.8-56.el8_9.2 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2024-6232 | NONE0 | python3-libs 3.6.8-56.el8_9 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 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 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 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4224 | NONE0 | python3-libs 3.6.8-56.el8_9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-7210 | NONE0 | python3-libs 3.6.8-56.el8_9 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2019-9674 | NONE0 | python3-libs 3.6.8-56.el8_9 No fix yet | 5.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-7592 | NONE0 | python3-libs 3.6.8-56.el8_9 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-25062 | NONE0 | python3-libxml2 2.9.7-16.el8_8.1 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-16.el8_8.1 fixed in 2.9.7-20.el8_10 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-32415 | NONE0 | python3-libxml2 2.9.7-16.el8_8.1 fixed in 2.9.7-21.el8_10.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-6021 | NONE0 | python3-libxml2 2.9.7-16.el8_8.1 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-16.el8_8.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-27113 | NONE0 | python3-libxml2 2.9.7-16.el8_8.1 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 fixed in 1.24.2-9.el8_10 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-66471 | NONE0 | python3-urllib3 1.24.2-5.el8 fixed in 1.24.2-9.el8_10 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-21441 | NONE0 | python3-urllib3 1.24.2-5.el8 fixed in 1.24.2-9.el8_10 | 2.7% 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-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 | python3-libs 3.6.8-56.el8_9 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-2026-54369 | NONE0 | acl 2.2.53-1.el8 fixed in 2.4.0-1.el8_10 | 0.1% 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 | python3-libs 3.6.8-56.el8_9 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 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 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 fixed in 3.6.8-73.el8_10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4878 | NONE0 | libcap 2.48-5.el8_8 fixed in 2.48-6.el8_10.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-44604 | NONE0 | python3-rpm 4.14.3-26.el8 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-44604 | NONE0 | rpm-build-libs 4.14.3-26.el8 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-44604 | NONE0 | rpm-libs 4.14.3-26.el8 No fix yet | 0.6% 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 | python3-libs 3.6.8-56.el8_9 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 fixed in 3.6.8-74.el8_10 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2021-35938 | NONE0 | python3-rpm 4.14.3-26.el8 fixed in 4.14.3-28.el8_9 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-35939 | NONE0 | python3-rpm 4.14.3-26.el8 fixed in 4.14.3-28.el8_9 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-35938 | NONE0 | rpm-build-libs 4.14.3-26.el8 fixed in 4.14.3-28.el8_9 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-35939 | NONE0 | rpm-build-libs 4.14.3-26.el8 fixed in 4.14.3-28.el8_9 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-35938 | NONE0 | rpm-libs 4.14.3-26.el8 fixed in 4.14.3-28.el8_9 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-35939 | NONE0 | rpm-libs 4.14.3-26.el8 fixed in 4.14.3-28.el8_9 | 0.5% Theoretical Threat | 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-9149 | NONE0 | libsolv 0.7.20-6.el8 No fix yet | 0.3% 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-2022-48564 | NONE0 | python3-libs 3.6.8-56.el8_9 fixed in 3.6.8-56.el8_9.2 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-11972 | NONE0 | python3-libs 3.6.8-56.el8_9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-39615 | NONE0 | python3-libxml2 2.9.7-16.el8_8.1 fixed in 2.9.7-18.el8_9 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-45322 | NONE0 | python3-libxml2 2.9.7-16.el8_8.1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-37891 | NONE0 | python3-urllib3 1.24.2-5.el8 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-2021-35937 | NONE0 | python3-rpm 4.14.3-26.el8 fixed in 4.14.3-28.el8_9 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-35937 | NONE0 | rpm-build-libs 4.14.3-26.el8 fixed in 4.14.3-28.el8_9 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-35937 | NONE0 | rpm-libs 4.14.3-26.el8 fixed in 4.14.3-28.el8_9 | 0.3% 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-2024-0450 | NONE0 | python3-libs 3.6.8-56.el8_9 fixed in 3.6.8-62.el8_10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-1757 | NONE0 | python3-libxml2 2.9.7-16.el8_8.1 No fix yet | 0.2% 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-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-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-2025-14104 | NONE0 | libuuid 2.32.1-43.el8 fixed in 2.32.1-48.el8_10 | 0.2% 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 No fix yet | 0.2% 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-2026-5713 | NONE0 | python3-libs 3.6.8-56.el8_9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-0990 | NONE0 | python3-libxml2 2.9.7-16.el8_8.1 No fix yet | 0.8% 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.3% 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-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-2023-24056 | NONE0 | libpkgconf 1.4.2-1.el8 No fix yet | 0.5% Theoretical Threat | 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-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 | python3-libs 3.6.8-56.el8_9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42308 | NONE0 | python3-libs 3.6.8-56.el8_9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6075 | NONE0 | python3-libs 3.6.8-56.el8_9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-9714 | NONE0 | python3-libxml2 2.9.7-16.el8_8.1 fixed in 2.9.7-21.el8_10.4 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-34459 | NONE0 | python3-libxml2 2.9.7-16.el8_8.1 fixed in 2.9.7-21.el8_10.5 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-44605 | NONE0 | python3-rpm 4.14.3-26.el8 No fix yet | — | Not Applicable |
| CVE-2026-44605 | NONE0 | rpm-build-libs 4.14.3-26.el8 No fix yet | — | Not Applicable |
| CVE-2026-44605 | NONE0 | rpm-libs 4.14.3-26.el8 No fix yet | — | 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-13595 | NONE0 | libblkid 2.32.1-43.el8 No fix yet | 0.1% 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-2026-13595 | NONE0 | libsmartcols 2.32.1-43.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libuuid 2.32.1-43.el8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45409 | NONE0 | python3-idna 2.5-5.el8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-27043 | NONE0 | python3-libs 3.6.8-56.el8_9 fixed in 3.6.8-56.el8_9.3 | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-12084 | NONE0 | python3-libs 3.6.8-56.el8_9 fixed in 3.6.8-72.el8_10 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-12781 | NONE0 | python3-libs 3.6.8-56.el8_9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-3276 | NONE0 | python3-libs 3.6.8-56.el8_9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-4360 | NONE0 | python3-libs 3.6.8-56.el8_9 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 fixed in 1.24.2-10.el8_10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-4516 | NONE0 | python3-libs 3.6.8-56.el8_9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-0397 | NONE0 | python3-libs 3.6.8-56.el8_9 No fix yet | 0.8% 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 | python3-libs 3.6.8-56.el8_9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0672 | NONE0 | python3-libs 3.6.8-56.el8_9 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-27456 | NONE0 | libblkid 2.32.1-43.el8 No fix yet | 0.1% 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-2026-27456 | NONE0 | libuuid 2.32.1-43.el8 No fix yet | 0.1% 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-2025-11468 | NONE0 | python3-libs 3.6.8-56.el8_9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0865 | NONE0 | python3-libs 3.6.8-56.el8_9 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 No fix yet | 0.6% 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-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 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-8291 | NONE0 | python3-libs 3.6.8-56.el8_9 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-45803 | NONE0 | python3-urllib3 1.24.2-5.el8 fixed in 1.24.2-5.el8_9.2 | 0.5% 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-11168 | NONE0 | python3-libs 3.6.8-56.el8_9 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 fixed in 3.6.8-67.el8_10 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-0989 | NONE0 | python3-libxml2 2.9.7-16.el8_8.1 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-2026-4519 | NONE0 | python3-libs 3.6.8-56.el8_9 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 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-2297 | NONE0 | python3-libs 3.6.8-56.el8_9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3479 | NONE0 | python3-libs 3.6.8-56.el8_9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1795 | NONE0 | python3-libs 3.6.8-56.el8_9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-0992 | NONE0 | python3-libxml2 2.9.7-16.el8_8.1 No fix yet | 0.4% 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-2025-6170 | NONE0 | python3-libxml2 2.9.7-16.el8_8.1 fixed in 2.9.7-21.el8_10.6 | 0.2% Theoretical Threat | Not Applicable |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.