Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker could cause denial of service via vulnerabilities in openssl (CVE-2024-6119) and libexpat (CVE-2024-45490), or memory corruption via openssl (CVE-2026-45445). Many high-severity findings require non-default configurations: for example, CVE-2024-6119 only applies if MySQL is configured to require X.509 client certificate name checks, which is not the default. Disabling unused features such as DTLS (affects gnutls CVEs) or using network segmentation to restrict inbound connections can mitigate several risks. All post-exploit findings require prior access and are low severity.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2024-6119 | HIGH7.8 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.0.7-28.0.1.el9_4 | 66.6% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2024-6119 | HIGH7.8 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.0.7-28.0.1.el9_4 | 66.6% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2026-45445 | HIGH7.73 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-45490 | HIGH7.5 | expat 2.5.0-2.el9_4 fixed in 2.5.0-2.el9_4.1 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-8176 | HIGH7.5 | expat 2.5.0-2.el9_4 fixed in 2.5.0-5.el9_6 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33846 | HIGH7.5 | gnutls 3.8.3-4.el9_4 fixed in 3.8.10-4.el9_8 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42009 | HIGH7.5 | gnutls 3.8.3-4.el9_4 fixed in 3.8.10-4.el9_8 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5121 | HIGH7.5 | libarchive 3.5.3-4.el9 fixed in 3.5.3-9.el9_7 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-6021 | HIGH7.5 | libxml2 2.9.13-6.el9_4 fixed in 2.9.13-10.el9_6 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-2100 | HIGH7.5 | p11-kit 0.25.3-2.el9 fixed in 0.26.2-1.el9 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-2100 | HIGH7.5 | p11-kit-trust 0.25.3-2.el9 fixed in 0.26.2-1.el9 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-39689 | HIGH7.5 | certifi 2024.2.2 fixed in 2024.7.4 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-12797 | HIGH7.4 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.2.2-6.0.1.el9_5.1 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-52533 | HIGH7 | glib2 2.68.4-14.el9 fixed in 2.68.4-16.el9_6.2 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42013 | MEDIUM6.97 | gnutls 3.8.3-4.el9_4 fixed in 3.8.10-4.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM6.97 | gnutls 3.8.3-4.el9_4 fixed in 3.8.10-4.el9_8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-32990 | MEDIUM6.97 | gnutls 3.8.3-4.el9_4 fixed in 3.8.3-6.el9_6.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-0966 | MEDIUM6.97 | libssh 0.10.4-13.el9 fixed in 0.10.4-18.el9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | glibc 2.34-100.0.1.el9_4.2 fixed in 2.34-231.0.1.el9_7.10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | glibc-common 2.34-100.0.1.el9_4.2 fixed in 2.34-231.0.1.el9_7.10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | glibc-minimal-langpack 2.34-100.0.1.el9_4.2 fixed in 2.34-231.0.1.el9_7.10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-5914 | MEDIUM6.63 | libarchive 3.5.3-4.el9 fixed in 3.5.3-6.el9_6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-25724 | MEDIUM6.63 | libarchive 3.5.3-4.el9 fixed in 3.5.3-5.el9_6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48864 | MEDIUM6.63 | libsolv 0.7.24-2.el9 fixed in 0.7.24-6.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7425 | MEDIUM6.63 | libxml2 2.9.13-6.el9_4 fixed in 2.9.13-11.el9_6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49043 | MEDIUM6.63 | libxml2 2.9.13-6.el9_4 fixed in 2.9.13-6.el9_5.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | systemd-libs 252-32.0.2.el9_4 fixed in 252-67.0.1.el9_8.2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13601 | MEDIUM6.54 | glib2 2.68.4-14.el9 fixed in 2.68.4-18.el9_7.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-24928 | MEDIUM6.54 | libxml2 2.9.13-6.el9_4 fixed in 2.9.13-6.el9_5.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45186 | MEDIUM6.38 | expat 2.5.0-2.el9_4 fixed in 2.5.0-6.el9_8.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | krb5-libs 1.21.1-1.0.1.el9 fixed in 1.21.1-10.0.1.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | krb5-libs 1.21.1-1.0.1.el9 fixed in 1.21.1-10.0.1.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | krb5-libs 1.21.1-1.0.1.el9 fixed in 1.21.1-2.0.1.el9_4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-4111 | MEDIUM6.38 | libarchive 3.5.3-4.el9 fixed in 3.5.3-7.el9_7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-4424 | MEDIUM6.38 | libarchive 3.5.3-4.el9 fixed in 3.5.3-9.el9_7 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-6176 | MEDIUM6.38 | libbrotli 1.0.9-6.el9 fixed in 1.0.9-9.el9_7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-27135 | MEDIUM6.38 | libnghttp2 1.43.0-5.el9_4.3 fixed in 1.43.0-6.el9_7.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-32414 | MEDIUM6.38 | libxml2 2.9.13-6.el9_4 fixed in 2.9.13-12.el9_6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-32415 | MEDIUM6.38 | libxml2 2.9.13-6.el9_4 fixed in 2.9.13-12.el9_6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.5.1-7.0.1.el9_7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.38 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-34183 | MEDIUM6.38 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3833 | MEDIUM6.29 | gnutls 3.8.3-4.el9_4 fixed in 3.8.10-4.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM6.29 | gnutls 3.8.3-4.el9_4 fixed in 3.8.10-4.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.5.1-7.0.1.el9_7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM6.03 | gnutls 3.8.3-4.el9_4 fixed in 3.8.10-4.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | glibc 2.34-100.0.1.el9_4.2 fixed in 2.34-168.0.1.el9_6.19 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | glibc-common 2.34-100.0.1.el9_4.2 fixed in 2.34-168.0.1.el9_6.19 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | glibc-minimal-langpack 2.34-100.0.1.el9_4.2 fixed in 2.34-168.0.1.el9_6.19 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4878 | MEDIUM5.95 | libcap 2.48-9.el9_2 fixed in 2.48-10.el9_8.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50602 | MEDIUM5.9 | expat 2.5.0-2.el9_4 fixed in 2.5.0-3.el9_5.1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | krb5-libs 1.21.1-1.0.1.el9 fixed in 1.21.1-3.0.1.el9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt 1.10.0-10.el9_2 fixed in 1.10.0-11.el9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1 4.16.0-8.el9_1 fixed in 4.16.0-10.el9_8 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-5535 | MEDIUM5.9 | openssl-fips-provider 3.0.7-2.0.1.el9 fixed in 3.0.7-6.0.1.el9_5 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-5535 | MEDIUM5.9 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.2.2-6.0.1.el9_5 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.61 | gnutls 3.8.3-4.el9_4 fixed in 3.8.10-4.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-4741 | MEDIUM5.6 | openssl-fips-provider 3.0.7-2.0.1.el9 fixed in 3.0.7-6.0.1.el9_5 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4741 | MEDIUM5.6 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.2.2-6.0.1.el9_5 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.5.1-4.0.1.el9_7 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14512 | MEDIUM5.52 | glib2 2.68.4-14.el9 fixed in 2.68.4-19.el9_8.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc 2.34-100.0.1.el9_4.2 fixed in 2.34-270.0.1.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc-common 2.34-100.0.1.el9_4.2 fixed in 2.34-270.0.1.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc-minimal-langpack 2.34-100.0.1.el9_4.2 fixed in 2.34-270.0.1.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6395 | MEDIUM5.52 | gnutls 3.8.3-4.el9_4 fixed in 3.8.3-6.el9_6.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | krb5-libs 1.21.1-1.0.1.el9 fixed in 1.21.1-6.0.1.el9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-5351 | MEDIUM5.52 | libssh 0.10.4-13.el9 fixed in 0.10.4-18.el9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-34459 | MEDIUM5.5 | libxml2 2.9.13-6.el9_4 fixed in 2.9.13-14.el9_8.1 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-0964 | MEDIUM5.35 | libssh 0.10.4-13.el9 fixed in 0.10.4-18.el9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM5.35 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-59375 | MEDIUM5.3 | expat 2.5.0-2.el9_4 fixed in 2.5.0-5.el9_7.1 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-12243 | MEDIUM5.3 | gnutls 3.8.3-4.el9_4 fixed in 3.8.3-6.el9 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-32989 | MEDIUM5.3 | gnutls 3.8.3-4.el9_4 fixed in 3.8.3-6.el9_6.2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-12133 | MEDIUM5.3 | libtasn1 4.16.0-8.el9_1 fixed in 4.16.0-9.el9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4603 | MEDIUM5.3 | openssl-fips-provider 3.0.7-2.0.1.el9 fixed in 3.0.7-6.0.1.el9_5 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4603 | MEDIUM5.3 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.2.2-6.0.1.el9_5 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid 2.37.4-18.0.1.el9 fixed in 2.37.4-21.0.1.el9_7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount 2.37.4-18.0.1.el9 fixed in 2.37.4-21.0.1.el9_7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libsmartcols 2.37.4-18.0.1.el9 fixed in 2.37.4-21.0.1.el9_7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid 2.37.4-18.0.1.el9 fixed in 2.37.4-21.0.1.el9_7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11187 | MEDIUM5.18 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.5.1-7.0.1.el9_7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | glibc 2.34-100.0.1.el9_4.2 fixed in 2.34-231.0.1.el9_7.10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | glibc-common 2.34-100.0.1.el9_4.2 fixed in 2.34-231.0.1.el9_7.10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | glibc-minimal-langpack 2.34-100.0.1.el9_4.2 fixed in 2.34-231.0.1.el9_7.10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | krb5-libs 1.21.1-1.0.1.el9 fixed in 1.21.1-3.0.1.el9 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | krb5-libs 1.21.1-1.0.1.el9 fixed in 1.21.1-8.0.1.el9_6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15468 | MEDIUM5.02 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.5.1-7.0.1.el9_7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-66199 | MEDIUM5.02 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.5.1-7.0.1.el9_7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.5.1-7.0.1.el9_7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.5.1-7.0.1.el9_7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.02 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-2.0.1.el9_8 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.02 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.02 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-2511 | MEDIUM4.81 | openssl-fips-provider 3.0.7-2.0.1.el9 fixed in 3.0.7-6.0.1.el9_5 | 54.0% Actively Exploited | Directly Exposed |
| CVE-2024-2511 | MEDIUM4.81 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.2.2-6.0.1.el9_5 | 54.0% Actively Exploited | Directly Exposed |
| CVE-2025-5702 | MEDIUM4.76 | glibc 2.34-100.0.1.el9_4.2 fixed in 2.34-168.0.1.el9_6.20 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5702 | MEDIUM4.76 | glibc-common 2.34-100.0.1.el9_4.2 fixed in 2.34-168.0.1.el9_6.20 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5702 | MEDIUM4.76 | glibc-minimal-langpack 2.34-100.0.1.el9_4.2 fixed in 2.34-168.0.1.el9_6.20 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | glibc 2.34-100.0.1.el9_4.2 fixed in 2.34-125.0.1.el9_5.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | glibc-common 2.34-100.0.1.el9_4.2 fixed in 2.34-125.0.1.el9_5.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | glibc-minimal-langpack 2.34-100.0.1.el9_4.2 fixed in 2.34-125.0.1.el9_5.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26462 | MEDIUM4.67 | krb5-libs 1.21.1-1.0.1.el9 fixed in 1.21.1-3.0.1.el9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0967 | MEDIUM4.67 | libssh 0.10.4-13.el9 fixed in 0.10.4-18.el9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9714 | MEDIUM4.67 | libxml2 2.9.13-6.el9_4 fixed in 2.9.13-14.el9_7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15469 | MEDIUM4.67 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.5.1-7.0.1.el9_7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM4.67 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.5.1-7.0.1.el9_7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-4517 | MEDIUM4.56 | python3-libs 3.9.18-3.el9 fixed in 3.9.21-2.el9_6.1 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-4138 | MEDIUM4.5 | python3 3.9.18-3.el9 fixed in 3.9.21-2.el9_6.1 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-6232 | MEDIUM4.5 | python3 3.9.18-3.el9 fixed in 3.9.19-8.el9_5.1 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-4138 | MEDIUM4.5 | python3-libs 3.9.18-3.el9 fixed in 3.9.21-2.el9_6.1 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-6232 | MEDIUM4.5 | python3-libs 3.9.18-3.el9 fixed in 3.9.19-8.el9_5.1 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-50782 | MEDIUM4.5 | cryptography 41.0.7 fixed in 42.0.0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-0915 | MEDIUM4.5 | glibc 2.34-100.0.1.el9_4.2 fixed in 2.34-231.0.1.el9_7.10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc 2.34-100.0.1.el9_4.2 fixed in 2.34-270.0.1.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | glibc-common 2.34-100.0.1.el9_4.2 fixed in 2.34-231.0.1.el9_7.10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-common 2.34-100.0.1.el9_4.2 fixed in 2.34-270.0.1.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | glibc-minimal-langpack 2.34-100.0.1.el9_4.2 fixed in 2.34-231.0.1.el9_7.10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-minimal-langpack 2.34-100.0.1.el9_4.2 fixed in 2.34-270.0.1.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM4.5 | gnutls 3.8.3-4.el9_4 fixed in 3.8.10-4.el9_8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-14831 | MEDIUM4.5 | gnutls 3.8.3-4.el9_4 fixed in 3.8.3-10.el9_7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-12797 | MEDIUM4.44 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.2.2-6.0.1.el9_5.1 | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-5450 | MEDIUM4.25 | glibc 2.34-100.0.1.el9_4.2 fixed in 2.34-272.0.1.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-common 2.34-100.0.1.el9_4.2 fixed in 2.34-272.0.1.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-minimal-langpack 2.34-100.0.1.el9_4.2 fixed in 2.34-272.0.1.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM4.25 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6100 | MEDIUM4.13 | python3 3.9.18-3.el9 fixed in 3.9.25-7.0.1.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | MEDIUM4.13 | python3-libs 3.9.18-3.el9 fixed in 3.9.25-7.0.1.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-0938 | MEDIUM4.08 | python3 3.9.18-3.el9 fixed in 3.9.21-2.el9 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0938 | MEDIUM4.08 | python3-libs 3.9.18-3.el9 fixed in 3.9.21-2.el9 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-4373 | MEDIUM4.08 | glib2 2.68.4-14.el9 fixed in 2.68.4-16.el9_6.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15467 | MEDIUM4.06 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.5.1-7.0.1.el9_7 | 47.6% High Exploitation Risk | Post-Exploit |
| CVE-2025-15467 | MEDIUM4.06 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.5.1-7.0.1.el9_7 | 47.6% High Exploitation Risk | Post-Exploit |
| CVE-2025-8114 | MEDIUM4 | libssh 0.10.4-13.el9 fixed in 0.10.4-18.el9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.5.1-7.0.1.el9_7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4598 | MEDIUM4 | systemd-libs 252-32.0.2.el9_4 fixed in 252-55.0.3.el9_7.7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-6597 | LOW3.98 | python3 3.9.18-3.el9 fixed in 3.9.18-3.el9_4.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-9287 | LOW3.98 | python3 3.9.18-3.el9 fixed in 3.9.21-1.el9_5 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-6597 | LOW3.98 | python3-libs 3.9.18-3.el9 fixed in 3.9.18-3.el9_4.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-9287 | LOW3.98 | python3-libs 3.9.18-3.el9 fixed in 3.9.21-1.el9_5 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-12718 | LOW3.88 | python3 3.9.18-3.el9 fixed in 3.9.21-2.el9_6.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-12718 | LOW3.88 | python3-libs 3.9.18-3.el9 fixed in 3.9.21-2.el9_6.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-69421 | LOW3.82 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.5.1-7.0.1.el9_7 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28390 | LOW3.82 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-34183 | LOW3.82 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-4435 | LOW3.82 | python3 3.9.18-3.el9 fixed in 3.9.21-2.el9_6.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8194 | LOW3.82 | python3 3.9.18-3.el9 fixed in 3.9.21-2.el9_6.2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-4435 | LOW3.82 | python3-libs 3.9.18-3.el9 fixed in 3.9.21-2.el9_6.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8194 | LOW3.82 | python3-libs 3.9.18-3.el9 fixed in 3.9.21-2.el9_6.2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-26130 | LOW3.82 | cryptography 41.0.7 fixed in 42.0.4 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-4877 | LOW3.82 | libssh 0.10.4-13.el9 fixed in 0.10.4-18.el9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | LOW3.77 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.5.1-7.0.1.el9_7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW3.77 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-3596 | LOW3.73 | krb5-libs 1.21.1-1.0.1.el9 fixed in 1.21.1-4.0.1.el9_5 | 14.9% High Exploitation Risk | Post-Exploit |
| CVE-2025-4330 | LOW3.72 | python3 3.9.18-3.el9 fixed in 3.9.21-2.el9_6.1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-4330 | LOW3.72 | python3-libs 3.9.18-3.el9 fixed in 3.9.21-2.el9_6.1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-4786 | LOW3.62 | python3 3.9.18-3.el9 fixed in 3.9.25-7.0.1.el9_8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW3.62 | python3 3.9.18-3.el9 fixed in 3.9.25-3.0.1.el9_7.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW3.62 | python3 3.9.18-3.el9 fixed in 3.9.25-3.0.1.el9_7.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1299 | LOW3.62 | python3 3.9.18-3.el9 fixed in 3.9.25-3.0.1.el9_7.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-4786 | LOW3.62 | python3-libs 3.9.18-3.el9 fixed in 3.9.25-7.0.1.el9_8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW3.62 | python3-libs 3.9.18-3.el9 fixed in 3.9.25-3.0.1.el9_7.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW3.62 | python3-libs 3.9.18-3.el9 fixed in 3.9.25-3.0.1.el9_7.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1299 | LOW3.62 | python3-libs 3.9.18-3.el9 fixed in 3.9.25-3.0.1.el9_7.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-6965 | LOW3.61 | sqlite-libs 3.34.1-7.el9_3 fixed in 3.34.1-9.el9_7 | 73.5% Actively Exploited | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gnupg2 2.3.3-4.el9 fixed in 2.3.3-5.el9_7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8058 | LOW3.57 | glibc 2.34-100.0.1.el9_4.2 fixed in 2.34-168.0.1.el9_6.23 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | glibc-common 2.34-100.0.1.el9_4.2 fixed in 2.34-168.0.1.el9_6.23 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | glibc-minimal-langpack 2.34-100.0.1.el9_4.2 fixed in 2.34-168.0.1.el9_6.23 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-5535 | LOW3.54 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.2.2-6.0.1.el9_5 | 5.6% Low-Moderate Risk | Post-Exploit |
| CVE-2019-12900 | LOW3.53 | bzip2 1.0.8-8.el9 fixed in 1.0.8-10.el9_5 | 8.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-12900 | LOW3.53 | bzip2-libs 1.0.8-8.el9 fixed in 1.0.8-10.el9_5 | 8.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-45491 | LOW3.53 | expat 2.5.0-2.el9_4 fixed in 2.5.0-2.el9_4.1 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-45492 | LOW3.53 | expat 2.5.0-2.el9_4 fixed in 2.5.0-2.el9_4.1 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42010 | LOW3.53 | gnutls 3.8.3-4.el9_4 fixed in 3.8.10-4.el9_8 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-56171 | LOW3.53 | libxml2 2.9.13-6.el9_4 fixed in 2.9.13-6.el9_5.2 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-6923 | LOW3.47 | python3 3.9.18-3.el9 fixed in 3.9.18-3.el9_4.5 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2024-6923 | LOW3.47 | python3-libs 3.9.18-3.el9 fixed in 3.9.18-3.el9_4.5 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-4438 | LOW3.4 | glibc 2.34-100.0.1.el9_4.2 fixed in 2.34-270.0.1.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | glibc-common 2.34-100.0.1.el9_4.2 fixed in 2.34-270.0.1.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | glibc-minimal-langpack 2.34-100.0.1.el9_4.2 fixed in 2.34-270.0.1.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9820 | LOW3.4 | gnutls 3.8.3-4.el9_4 fixed in 3.8.3-10.el9_7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW3.4 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.5.1-7.0.1.el9_7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-4741 | LOW3.36 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.2.2-6.0.1.el9_5 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2025-9230 | LOW3.36 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.5.1-4.0.1.el9_7 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-26007 | LOW3.31 | cryptography 41.0.7 fixed in 46.0.5 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-0727 | LOW3.3 | cryptography 41.0.7 fixed in 42.0.2 | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-37371 | LOW3.28 | krb5-libs 1.21.1-1.0.1.el9 fixed in 1.21.1-2.0.1.el9_4 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2025-49796 | LOW3.28 | libxml2 2.9.13-6.el9_4 fixed in 2.9.13-10.el9_6 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2024-34397 | LOW3.23 | glib2 2.68.4-14.el9 fixed in 2.68.4-14.el9_4.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | LOW3.21 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42768 | LOW3.21 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-9086 | LOW3.18 | curl 7.76.1-29.el9_4 fixed in 7.76.1-35.el9_7.3 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-9086 | LOW3.18 | libcurl 7.76.1-29.el9_4 fixed in 7.76.1-35.el9_7.3 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4603 | LOW3.18 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.2.2-6.0.1.el9_5 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-8088 | LOW3.18 | python3 3.9.18-3.el9 fixed in 3.9.19-8.el9 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-8088 | LOW3.18 | python3-libs 3.9.18-3.el9 fixed in 3.9.19-8.el9 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-0450 | LOW3.16 | python3 3.9.18-3.el9 fixed in 3.9.18-3.el9_4.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-0450 | LOW3.16 | python3-libs 3.9.18-3.el9 fixed in 3.9.18-3.el9_4.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3832 | LOW3.15 | gnutls 3.8.3-4.el9_4 fixed in 3.8.10-4.el9_8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-5419 | LOW3.15 | gnutls 3.8.3-4.el9_4 fixed in 3.8.10-4.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11187 | LOW3.11 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.5.1-7.0.1.el9_7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-2398 | LOW3.1 | curl 7.76.1-29.el9_4 fixed in 7.76.1-29.el9_4.1 | 36.1% High Exploitation Risk | Post-Exploit |
| CVE-2024-2398 | LOW3.1 | libcurl 7.76.1-29.el9_4 fixed in 7.76.1-29.el9_4.1 | 36.1% High Exploitation Risk | Post-Exploit |
| CVE-2025-4878 | LOW3.06 | libssh 0.10.4-13.el9 fixed in 0.10.4-18.el9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15468 | LOW3.01 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.5.1-7.0.1.el9_7 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-66199 | LOW3.01 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.5.1-7.0.1.el9_7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69420 | LOW3.01 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.5.1-7.0.1.el9_7 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-22796 | LOW3.01 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.5.1-7.0.1.el9_7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-31790 | LOW3.01 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-2.0.1.el9_8 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-42764 | LOW3.01 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-42769 | LOW3.01 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW3.01 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.01 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14087 | LOW3 | glib2 2.68.4-14.el9 fixed in 2.68.4-19.el9_8.1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-27459 | LOW3 | pyOpenSSL 23.3.0 fixed in 26.0.0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-32988 | LOW2.95 | gnutls 3.8.3-4.el9_4 fixed in 3.8.3-6.el9_6.2 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-5318 | LOW2.92 | libssh 0.10.4-13.el9 fixed in 0.10.4-15.el9_7 | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-5987 | LOW2.92 | libssh 0.10.4-13.el9 fixed in 0.10.4-17.el9_7 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl-libs 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2511 | LOW2.89 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.2.2-6.0.1.el9_5 | 54.0% Actively Exploited | Post-Exploit |
| CVE-2020-11023 | LOW2.86 | libgcc 11.4.1-3.0.1.el9 fixed in 11.5.0-5.0.1.el9_5 | 83.8% Actively Exploited | Post-Exploit |
| CVE-2020-11023 | LOW2.86 | libstdc++ 11.4.1-3.0.1.el9 fixed in 11.5.0-5.0.1.el9_5 | 83.8% Actively Exploited | Post-Exploit |
| CVE-2025-45582 | LOW2.86 | tar 2:1.34-6.el9_1 fixed in 2:1.34-9.el9_7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15469 | LOW2.8 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.5.1-7.0.1.el9_7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-22795 | LOW2.8 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.5.1-7.0.1.el9_7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW2.8 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-6075 | LOW2.8 | python3 3.9.18-3.el9 fixed in 3.9.25-2.0.1.el9_7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-6075 | LOW2.8 | python3-libs 3.9.18-3.el9 fixed in 3.9.25-2.0.1.el9_7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0965 | LOW2.8 | libssh 0.10.4-13.el9 fixed in 0.10.4-18.el9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-33845 | LOW2.78 | gnutls 3.8.3-4.el9_4 fixed in 3.8.10-4.el9_8 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-49794 | LOW2.78 | libxml2 2.9.13-6.el9_4 fixed in 2.9.13-10.el9_6 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | LOW2.78 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-48795 | LOW2.76 | paramiko 2.11.0 fixed in 3.4.0 | 93.3% Actively Exploited | Post-Exploit |
| CVE-2025-4517 | LOW2.74 | python3 3.9.18-3.el9 fixed in 3.9.21-2.el9_6.1 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42766 | LOW2.7 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42767 | LOW2.7 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-12084 | LOW2.7 | python3 3.9.18-3.el9 fixed in 3.9.25-3.0.1.el9_7 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-12084 | LOW2.7 | python3-libs 3.9.18-3.el9 fixed in 3.9.25-3.0.1.el9_7 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-34073 | LOW2.7 | cryptography 41.0.7 fixed in 46.0.6 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27448 | LOW2.7 | pyOpenSSL 23.3.0 fixed in 26.0.0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8277 | LOW2.63 | libssh 0.10.4-13.el9 fixed in 0.10.4-18.el9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0968 | LOW2.63 | libssh 0.10.4-13.el9 fixed in 0.10.4-18.el9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | LOW2.55 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-68160 | LOW2.4 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.5.1-7.0.1.el9_7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-0865 | LOW2.29 | python3 3.9.18-3.el9 fixed in 3.9.25-7.0.1.el9_8 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0865 | LOW2.29 | python3-libs 3.9.18-3.el9 fixed in 3.9.25-7.0.1.el9_8 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69277 | LOW2.29 | PyNaCl 1.4.0 fixed in 1.6.2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils-single 8.32-35.0.1.el9 fixed in 8.32-41.0.1.el9_8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-4032 | LOW2.22 | python3 3.9.18-3.el9 fixed in 3.9.18-3.el9_4.3 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4032 | LOW2.22 | python3-libs 3.9.18-3.el9 fixed in 3.9.18-3.el9_4.3 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-6069 | LOW2.19 | python3 3.9.18-3.el9 fixed in 3.9.25-2.0.1.el9_7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8291 | LOW2.19 | python3 3.9.18-3.el9 fixed in 3.9.25-2.0.1.el9_7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-6069 | LOW2.19 | python3-libs 3.9.18-3.el9 fixed in 3.9.25-2.0.1.el9_7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8291 | LOW2.19 | python3-libs 3.9.18-3.el9 fixed in 3.9.25-2.0.1.el9_7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-6170 | LOW2.12 | libxml2 2.9.13-6.el9_4 fixed in 2.9.13-14.el9_8.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW2.04 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.5.1-7.0.1.el9_7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45446 | LOW1.89 | openssl 1:3.0.7-27.0.3.el9 fixed in 1:3.5.5-4.0.1.el9_8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-11168 | LOW1.89 | python3 3.9.18-3.el9 fixed in 3.9.21-1.el9_5 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-11168 | LOW1.89 | python3-libs 3.9.18-3.el9 fixed in 3.9.21-1.el9_5 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | shadow-utils 2:4.9-8.el9 fixed in 2:4.9-15.el9 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-44405 | LOW1.73 | paramiko 2.11.0 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4519 | LOW1.68 | python3 3.9.18-3.el9 fixed in 3.9.25-7.0.1.el9_8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-4519 | LOW1.68 | python3-libs 3.9.18-3.el9 fixed in 3.9.25-7.0.1.el9_8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-5642 | LOW1.38 | python3 3.9.18-3.el9 fixed in 3.9.25-2.0.1.el9_7 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-5642 | LOW1.38 | python3-libs 3.9.18-3.el9 fixed in 3.9.25-2.0.1.el9_7 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-68121 | NONE0 | stdlib v1.18.2 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-24538 | NONE0 | stdlib v1.18.2 fixed in 1.19.8, 1.20.3 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-24540 | NONE0 | stdlib v1.18.2 fixed in 1.19.9, 1.20.4 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-24790 | NONE0 | stdlib v1.18.2 fixed in 1.21.11, 1.22.4 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-30580 | NONE0 | stdlib v1.18.2 fixed in 1.17.11, 1.18.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-29403 | NONE0 | stdlib v1.18.2 fixed in 1.19.10, 1.20.5 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-39822 | NONE0 | stdlib v1.18.2 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-27664 | NONE0 | stdlib v1.18.2 fixed in 1.18.6, 1.19.1 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-28131 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-2879 | NONE0 | stdlib v1.18.2 fixed in 1.18.7, 1.19.2 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-2880 | NONE0 | stdlib v1.18.2 fixed in 1.18.7, 1.19.2 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-29804 | NONE0 | stdlib v1.18.2 fixed in 1.17.11, 1.18.3 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-30630 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-30631 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-30632 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-30633 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-30634 | NONE0 | stdlib v1.18.2 fixed in 1.17.11, 1.18.3 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-30635 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-32189 | NONE0 | stdlib v1.18.2 fixed in 1.17.13, 1.18.5 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-41715 | NONE0 | stdlib v1.18.2 fixed in 1.18.7, 1.19.2 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-41716 | NONE0 | stdlib v1.18.2 fixed in 1.18.8, 1.19.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-41720 | NONE0 | stdlib v1.18.2 fixed in 1.18.9, 1.19.4 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-41722 | NONE0 | stdlib v1.18.2 fixed in 1.19.6, 1.20.1 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2022-41723 | NONE0 | stdlib v1.18.2 fixed in 1.19.6, 1.20.1 | 4.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-41724 | NONE0 | stdlib v1.18.2 fixed in 1.19.6, 1.20.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-41725 | NONE0 | stdlib v1.18.2 fixed in 1.19.6, 1.20.1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-24534 | NONE0 | stdlib v1.18.2 fixed in 1.19.8, 1.20.3 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2023-24536 | NONE0 | stdlib v1.18.2 fixed in 1.19.8, 1.20.3 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-24537 | NONE0 | stdlib v1.18.2 fixed in 1.19.8, 1.20.3 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-39325 | NONE0 | stdlib v1.18.2 fixed in 1.20.10, 1.21.3 | 3.8% Low-Moderate Risk | Not Applicable |
| CVE-2023-45283 | NONE0 | stdlib v1.18.2 fixed in 1.20.11, 1.21.4, 1.20.12, 1.21.5 | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2023-45287 | NONE0 | stdlib v1.18.2 fixed in 1.20.0 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-45288 | NONE0 | stdlib v1.18.2 fixed in 1.21.9, 1.22.2 | 92.0% Actively Exploited | Not Applicable |
| CVE-2024-34156 | NONE0 | stdlib v1.18.2 fixed in 1.22.7, 1.23.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-61726 | NONE0 | stdlib v1.18.2 fixed in 1.24.12, 1.25.6 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2025-61729 | NONE0 | stdlib v1.18.2 fixed in 1.24.11, 1.25.5 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-25679 | NONE0 | stdlib v1.18.2 fixed in 1.25.8, 1.26.1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-27145 | NONE0 | stdlib v1.18.2 fixed in 1.25.11, 1.26.4 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-32280 | NONE0 | stdlib v1.18.2 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32281 | NONE0 | stdlib v1.18.2 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-32283 | NONE0 | stdlib v1.18.2 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-33811 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-33814 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39820 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39836 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42499 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42504 | NONE0 | stdlib v1.18.2 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-58183 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61728 | NONE0 | stdlib v1.18.2 fixed in 1.24.12, 1.25.6 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-24539 | NONE0 | stdlib v1.18.2 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-29400 | NONE0 | stdlib v1.18.2 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-29458 | NONE0 | ncurses-libs 6.2-10.20210508.el9 fixed in 6.2-10.20210508.el9_6.2 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-47907 | NONE0 | stdlib v1.18.2 fixed in 1.23.12, 1.24.6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-4673 | NONE0 | stdlib v1.18.2 fixed in 1.23.10, 1.24.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-1705 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-32148 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-29406 | NONE0 | stdlib v1.18.2 fixed in 1.19.11, 1.20.6 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-24785 | NONE0 | stdlib v1.18.2 fixed in 1.21.8, 1.22.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-47906 | NONE0 | stdlib v1.18.2 fixed in 1.23.12, 1.24.6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61727 | NONE0 | stdlib v1.18.2 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39825 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32282 | NONE0 | stdlib v1.18.2 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-39318 | NONE0 | stdlib v1.18.2 fixed in 1.20.8, 1.21.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-39319 | NONE0 | stdlib v1.18.2 fixed in 1.20.8, 1.21.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-32289 | NONE0 | stdlib v1.18.2 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-24783 | NONE0 | stdlib v1.18.2 fixed in 1.21.8, 1.22.1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-24791 | NONE0 | stdlib v1.18.2 fixed in 1.21.12, 1.22.5 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2024-34155 | NONE0 | stdlib v1.18.2 fixed in 1.22.7, 1.23.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-34158 | NONE0 | stdlib v1.18.2 fixed in 1.22.7, 1.23.1 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2024-45336 | NONE0 | stdlib v1.18.2 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-1962 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-24789 | NONE0 | stdlib v1.18.2 fixed in 1.21.11, 1.22.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32288 | NONE0 | stdlib v1.18.2 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-24784 | NONE0 | stdlib v1.18.2 fixed in 1.21.8, 1.22.1 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-22871 | NONE0 | stdlib v1.18.2 fixed in 1.23.8, 1.24.2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-27142 | NONE0 | stdlib v1.18.2 fixed in 1.25.8, 1.26.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39823 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39826 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-41717 | NONE0 | stdlib v1.18.2 fixed in 1.18.9, 1.19.4 | 5.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-24532 | NONE0 | stdlib v1.18.2 fixed in 1.19.7, 1.20.2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-29409 | NONE0 | stdlib v1.18.2 fixed in 1.19.12, 1.20.7, 1.21.0-rc.4 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-39326 | NONE0 | stdlib v1.18.2 fixed in 1.20.12, 1.21.5 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-45284 | NONE0 | stdlib v1.18.2 fixed in 1.20.11, 1.21.4 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45289 | NONE0 | stdlib v1.18.2 fixed in 1.21.8, 1.22.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-45290 | NONE0 | stdlib v1.18.2 fixed in 1.21.8, 1.22.1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-22866 | NONE0 | stdlib v1.18.2 fixed in 1.22.12, 1.23.6, 1.24.0-rc.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22873 | NONE0 | stdlib v1.18.2 fixed in 1.23.9, 1.24.3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-47912 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58185 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-58187 | NONE0 | stdlib v1.18.2 fixed in 1.24.9, 1.25.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58188 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58189 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61723 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61724 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61725 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61730 | NONE0 | stdlib v1.18.2 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42505 | NONE0 | stdlib v1.18.2 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42507 | NONE0 | stdlib v1.18.2 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58186 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-22870 | NONE0 | stdlib v1.18.2 fixed in 1.23.7, 1.24.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-45341 | NONE0 | stdlib v1.18.2 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-30629 | NONE0 | stdlib v1.18.2 fixed in 1.17.11, 1.18.3 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-27139 | NONE0 | stdlib v1.18.2 fixed in 1.25.8, 1.26.1 | 0.2% Theoretical Threat | Not Applicable |
| GHSA-537c-gmf6-5ccf | NONE0 | cryptography 41.0.7 fixed in 48.0.1 | — | Not Applicable |
| GHSA-h4gh-qq45-vh27 | NONE0 | cryptography 41.0.7 fixed in 43.0.1 | — | Not Applicable |
| CVE-2026-39824 | NONE0 | golang.org/x/sys v0.13.0 fixed in 0.44.0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-0913 | NONE0 | stdlib v1.18.2 fixed in 1.23.10, 1.24.4 | 0.2% Theoretical Threat | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.