Last scanned:
This image poses a critical security risk and must not be used in production, especially as an internet-facing service. An attacker could exploit CVE-2024-2961 to achieve remote code execution if the server performs character set conversion to ISO-2022-CN-EXT, or leverage CVE-2023-48795 to bypass SSH integrity checks. Note that CVE-2024-2961 requires non-default configuration; however, other vulnerabilities are directly exploitable without special conditions.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2024-2961 | HIGH8 | glibc 2.28-236.0.1.el8.7 fixed in 2.28-251.0.2.el8_10.1 | 88.3% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2024-2961 | HIGH8 | glibc-common 2.28-236.0.1.el8.7 fixed in 2.28-251.0.2.el8_10.1 | 88.3% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2024-2961 | HIGH8 | glibc-minimal-langpack 2.28-236.0.1.el8.7 fixed in 2.28-251.0.2.el8_10.1 | 88.3% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33845 | HIGH7.73 | gnutls 3.6.16-8.el8_9 fixed in 3.6.16-8.el8_10.6 | 0.8% 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-2024-33599 | HIGH7.6 | glibc 2.28-236.0.1.el8.7 fixed in 2.28-251.0.2.el8_10.2 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | glibc-common 2.28-236.0.1.el8.7 fixed in 2.28-251.0.2.el8_10.2 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | glibc-minimal-langpack 2.28-236.0.1.el8.7 fixed in 2.28-251.0.2.el8_10.2 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-52425 | HIGH7.5 | expat 2.2.5-11.0.1.el8 fixed in 2.2.5-11.0.1.el8_9.1 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-45490 | HIGH7.5 | expat 2.2.5-11.0.1.el8 fixed in 2.2.5-15.0.1.el8_10 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-8176 | HIGH7.5 | expat 2.2.5-11.0.1.el8 fixed in 2.2.5-17.0.1.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-8.el8_9 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-8.el8_9 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-8.el8_9 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-2025-6021 | HIGH7.5 | libxml2 2.9.7-18.el8_9 fixed in 2.9.7-21.el8_10.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-25062 | HIGH7.5 | libxml2 2.9.7-18.el8_9 fixed in 2.9.7-18.el8_10.1 | 1.4% 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-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-2024-37371 | HIGH7.28 | krb5-libs 1.18.2-26.0.1.el8_9 fixed in 1.18.2-29.0.1.el8_10 | 1.9% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| 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-42013 | MEDIUM6.97 | gnutls 3.6.16-8.el8_9 fixed in 3.6.16-8.el8_10.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM6.97 | gnutls 3.6.16-8.el8_9 fixed in 3.6.16-8.el8_10.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-32990 | MEDIUM6.97 | gnutls 3.6.16-8.el8_9 fixed in 3.6.16-8.el8_10.4 | 0.7% 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 | 85.0% Actively Exploited | Directly Exposed |
| 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-2026-48864 | MEDIUM6.63 | libsolv 0.7.20-6.el8 fixed in 0.7.20-7.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7425 | MEDIUM6.63 | libxml2 2.9.7-18.el8_9 fixed in 2.9.7-21.el8_10.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49043 | MEDIUM6.63 | libxml2 2.9.7-18.el8_9 fixed in 2.9.7-18.el8_10.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-32988 | MEDIUM6.56 | gnutls 3.6.16-8.el8_9 fixed in 3.6.16-8.el8_10.4 | 1.2% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| 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-18.el8_9 fixed in 2.9.7-19.el8_10 | 0.4% Theoretical Threat | 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.0.1.el8 fixed in 2.5.0-2.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | krb5-libs 1.18.2-26.0.1.el8_9 fixed in 1.18.2-34.0.1.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | krb5-libs 1.18.2-26.0.1.el8_9 fixed in 1.18.2-34.0.1.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | krb5-libs 1.18.2-26.0.1.el8_9 fixed in 1.18.2-29.0.1.el8_10 | 0.7% 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-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-2025-32414 | MEDIUM6.38 | libxml2 2.9.7-18.el8_9 fixed in 2.9.7-20.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-32415 | MEDIUM6.38 | libxml2 2.9.7-18.el8_9 fixed in 2.9.7-21.el8_10.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.38 | openssl-libs 1:1.1.1k-12.el8_9 fixed in 1:1.1.1k-17.el8_6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-3833 | MEDIUM6.29 | gnutls 3.6.16-8.el8_9 fixed in 3.6.16-8.el8_10.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM6.29 | gnutls 3.6.16-8.el8_9 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-12.el8_9 fixed in 1:1.1.1k-15.el8_6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM6.03 | gnutls 3.6.16-8.el8_9 fixed in 3.6.16-8.el8_10.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | glibc 2.28-236.0.1.el8.7 fixed in 2.28-251.0.3.el8_10.22 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | glibc-common 2.28-236.0.1.el8.7 fixed in 2.28-251.0.3.el8_10.22 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | glibc-minimal-langpack 2.28-236.0.1.el8.7 fixed in 2.28-251.0.3.el8_10.22 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4878 | MEDIUM5.95 | libcap 2.48-6.el8_9 fixed in 2.48-6.el8_10.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50602 | MEDIUM5.9 | expat 2.2.5-11.0.1.el8 fixed in 2.2.5-16.0.1.el8_10 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | krb5-libs 1.18.2-26.0.1.el8_9 fixed in 1.18.2-27.0.1.el8_10 | 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-5535 | MEDIUM5.9 | openssl-libs 1:1.1.1k-12.el8_9 fixed in 1:1.1.1k-14.el8_6 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35938 | MEDIUM5.7 | rpm-libs 4.14.3-26.el8 fixed in 4.14.3-28.0.2.el8_9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-35939 | MEDIUM5.7 | rpm-libs 4.14.3-26.el8 fixed in 4.14.3-28.0.2.el8_9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.61 | gnutls 3.6.16-8.el8_9 fixed in 3.6.16-8.el8_10.6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-4741 | MEDIUM5.6 | openssl-libs 1:1.1.1k-12.el8_9 fixed in 1:1.1.1k-16.el8_6 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | openssl-libs 1:1.1.1k-12.el8_9 fixed in 1:1.1.1k-14.el8_10 | 1.7% 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-2025-6395 | MEDIUM5.52 | gnutls 3.6.16-8.el8_9 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.0.1.el8_9 fixed in 1.18.2-31.0.1.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-34459 | MEDIUM5.5 | libxml2 2.9.7-18.el8_9 fixed in 2.9.7-21.el8_10.5 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35937 | MEDIUM5.44 | rpm-libs 4.14.3-26.el8 fixed in 4.14.3-28.0.2.el8_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-59375 | MEDIUM5.3 | expat 2.2.5-11.0.1.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.0.1.el8.7 fixed in 2.28-251.0.2.el8_10.2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | glibc-common 2.28-236.0.1.el8.7 fixed in 2.28-251.0.2.el8_10.2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | glibc-minimal-langpack 2.28-236.0.1.el8.7 fixed in 2.28-251.0.2.el8_10.2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-12243 | MEDIUM5.3 | gnutls 3.6.16-8.el8_9 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-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-2025-14104 | MEDIUM5.18 | libblkid 2.32.1-43.0.1.el8 fixed in 2.32.1-48.0.1.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount 2.32.1-43.0.1.el8 fixed in 2.32.1-48.0.1.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libsmartcols 2.32.1-43.0.1.el8 fixed in 2.32.1-48.0.1.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid 2.32.1-43.0.1.el8 fixed in 2.32.1-48.0.1.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | glibc 2.28-236.0.1.el8.7 fixed in 2.28-251.0.4.el8_10.31 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | glibc-common 2.28-236.0.1.el8.7 fixed in 2.28-251.0.4.el8_10.31 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | glibc-minimal-langpack 2.28-236.0.1.el8.7 fixed in 2.28-251.0.4.el8_10.31 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | krb5-libs 1.18.2-26.0.1.el8_9 fixed in 1.18.2-27.0.1.el8_10 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | krb5-libs 1.18.2-26.0.1.el8_9 fixed in 1.18.2-32.0.1.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-7008 | MEDIUM5.02 | systemd-libs 239-78.0.3.el8 fixed in 239-82.0.1.el8 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-45447 | MEDIUM4.86 | openssl 1:1.1.1k-12.el8_9 fixed in 1:1.1.1k-16.el8_6 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-43804 | MEDIUM4.86 | python39-libs 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.18-3.module+el8.10.0+90269+2fa22b99 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-21626 | MEDIUM4.74 | github.com/opencontainers/runc v1.1.0 fixed in 1.1.12 | 18.1% High Exploitation Risk | Post-ExploitContext importance: MEDIUM |
| CVE-2025-0395 | MEDIUM4.67 | glibc 2.28-236.0.1.el8.7 fixed in 2.28-251.0.3.el8_10.16 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | glibc-common 2.28-236.0.1.el8.7 fixed in 2.28-251.0.3.el8_10.16 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | glibc-minimal-langpack 2.28-236.0.1.el8.7 fixed in 2.28-251.0.3.el8_10.16 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-9714 | MEDIUM4.67 | libxml2 2.9.7-18.el8_9 fixed in 2.9.7-21.el8_10.4 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-48795 | MEDIUM4.6 | paramiko 2.11.0 fixed in 3.4.0 | 93.3% Actively Exploited | Post-Exploit |
| CVE-2025-4517 | MEDIUM4.56 | python39 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.25-2.module+el8.10.0+90733+27f37730 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-4517 | MEDIUM4.56 | python39-libs 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.25-2.module+el8.10.0+90733+27f37730 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-4138 | MEDIUM4.5 | python39 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.25-2.module+el8.10.0+90733+27f37730 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-3651 | MEDIUM4.5 | python39 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.19-1.module+el8.10.0+90341+71ca88f4 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2024-6232 | MEDIUM4.5 | python39 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.20-1.module+el8.10.0+90419+54594e05 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-4138 | MEDIUM4.5 | python39-libs 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.25-2.module+el8.10.0+90733+27f37730 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-3651 | MEDIUM4.5 | python39-libs 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.19-1.module+el8.10.0+90341+71ca88f4 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2024-6232 | MEDIUM4.5 | python39-libs 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.20-1.module+el8.10.0+90419+54594e05 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-39689 | MEDIUM4.5 | certifi 2023.7.22 fixed in 2024.7.4 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-50782 | MEDIUM4.5 | cryptography 41.0.3 fixed in 42.0.0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-0915 | MEDIUM4.5 | glibc 2.28-236.0.1.el8.7 fixed in 2.28-251.0.4.el8_10.31 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc 2.28-236.0.1.el8.7 fixed in 2.28-251.0.4.el8_10.37 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | glibc-common 2.28-236.0.1.el8.7 fixed in 2.28-251.0.4.el8_10.31 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-common 2.28-236.0.1.el8.7 fixed in 2.28-251.0.4.el8_10.37 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | glibc-minimal-langpack 2.28-236.0.1.el8.7 fixed in 2.28-251.0.4.el8_10.31 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-minimal-langpack 2.28-236.0.1.el8.7 fixed in 2.28-251.0.4.el8_10.37 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM4.5 | gnutls 3.6.16-8.el8_9 fixed in 3.6.16-8.el8_10.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-28834 | MEDIUM4.5 | gnutls 3.6.16-8.el8_9 fixed in 3.6.16-8.el8_9.3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-14831 | MEDIUM4.5 | gnutls 3.6.16-8.el8_9 fixed in 3.6.16-8.el8_10.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc 2.28-236.0.1.el8.7 fixed in 2.28-251.0.4.el8_10.38 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-common 2.28-236.0.1.el8.7 fixed in 2.28-251.0.4.el8_10.38 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-minimal-langpack 2.28-236.0.1.el8.7 fixed in 2.28-251.0.4.el8_10.38 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-0938 | MEDIUM4.08 | python39 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.25-2.module+el8.10.0+90733+27f37730 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0938 | MEDIUM4.08 | python39-libs 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.25-2.module+el8.10.0+90733+27f37730 | 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-2025-4598 | MEDIUM4 | systemd-libs 239-78.0.3.el8 fixed in 239-82.0.4.el8_10.5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | glibc 2.28-236.0.1.el8.7 fixed in 2.28-251.0.2.el8_10.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | glibc-common 2.28-236.0.1.el8.7 fixed in 2.28-251.0.2.el8_10.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | glibc-minimal-langpack 2.28-236.0.1.el8.7 fixed in 2.28-251.0.2.el8_10.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6597 | LOW3.98 | python39 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.19-1.module+el8.10.0+90341+71ca88f4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-9287 | LOW3.98 | python39 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.25-2.module+el8.10.0+90733+27f37730 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-6597 | LOW3.98 | python39-libs 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.19-1.module+el8.10.0+90341+71ca88f4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-9287 | LOW3.98 | python39-libs 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.25-2.module+el8.10.0+90733+27f37730 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-31133 | LOW3.98 | github.com/opencontainers/runc v1.1.0 fixed in 1.2.8, 1.3.3, 1.4.0-rc.3 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2022-29162 | LOW3.98 | github.com/opencontainers/runc v1.1.0 fixed in 1.1.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-28642 | LOW3.98 | github.com/opencontainers/runc v1.1.0 fixed in 1.1.5 | 0.3% 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-2023-23931 | LOW3.9 | python39 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.18-3.module+el8.10.0+90269+2fa22b99 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-23931 | LOW3.9 | python39-libs 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.18-3.module+el8.10.0+90269+2fa22b99 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28390 | LOW3.82 | openssl 1:1.1.1k-12.el8_9 fixed in 1:1.1.1k-17.el8_6 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-4435 | LOW3.82 | python39 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.25-2.module+el8.10.0+90733+27f37730 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2255 | LOW3.82 | python39 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.20-1.module+el8.10.0+90419+54594e05 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-8194 | LOW3.82 | python39 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.20-2.module+el8.10.0+90647+49247197 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-4435 | LOW3.82 | python39-libs 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.25-2.module+el8.10.0+90733+27f37730 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2255 | LOW3.82 | python39-libs 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.20-1.module+el8.10.0+90419+54594e05 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-8194 | LOW3.82 | python39-libs 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.20-2.module+el8.10.0+90647+49247197 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-26130 | LOW3.82 | cryptography 41.0.3 fixed in 42.0.4 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2023-49083 | LOW3.82 | cryptography 41.0.3 fixed in 41.0.6 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2025-52565 | LOW3.82 | github.com/opencontainers/runc v1.1.0 fixed in 1.2.8, 1.3.3, 1.4.0-rc.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-52881 | LOW3.82 | github.com/opencontainers/runc v1.1.0 fixed in 1.2.8, 1.3.3, 1.4.0-rc.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69419 | LOW3.77 | openssl 1:1.1.1k-12.el8_9 fixed in 1:1.1.1k-15.el8_6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-3596 | LOW3.73 | krb5-libs 1.18.2-26.0.1.el8_9 fixed in 1.18.2-30.0.1.el8_10 | 14.9% High Exploitation Risk | Post-Exploit |
| CVE-2025-4330 | LOW3.72 | python39 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.25-2.module+el8.10.0+90733+27f37730 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-4330 | LOW3.72 | python39-libs 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.25-2.module+el8.10.0+90733+27f37730 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-6965 | LOW3.61 | sqlite-libs 3.26.0-19.0.1.el8_9 fixed in 3.26.0-20.el8_10 | 73.5% Actively Exploited | 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-2023-27561 | LOW3.57 | github.com/opencontainers/runc v1.1.0 fixed in 1.1.5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-8058 | LOW3.57 | glibc 2.28-236.0.1.el8.7 fixed in 2.28-251.0.3.el8_10.25 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | glibc-common 2.28-236.0.1.el8.7 fixed in 2.28-251.0.3.el8_10.25 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | glibc-minimal-langpack 2.28-236.0.1.el8.7 fixed in 2.28-251.0.3.el8_10.25 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-5535 | LOW3.54 | openssl 1:1.1.1k-12.el8_9 fixed in 1:1.1.1k-14.el8_6 | 5.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-40897 | LOW3.54 | python39 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.18-3.module+el8.10.0+90269+2fa22b99 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-40897 | LOW3.54 | python39-libs 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.18-3.module+el8.10.0+90269+2fa22b99 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2019-12900 | LOW3.53 | bzip2 1.0.6-26.el8 fixed in 1.0.6-28.el8_10 | 8.1% 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-2024-45491 | LOW3.53 | expat 2.2.5-11.0.1.el8 fixed in 2.2.5-15.0.1.el8_10 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-45492 | LOW3.53 | expat 2.2.5-11.0.1.el8 fixed in 2.2.5-15.0.1.el8_10 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42010 | LOW3.53 | gnutls 3.6.16-8.el8_9 fixed in 3.6.16-8.el8_10.6 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-56171 | LOW3.53 | libxml2 2.9.7-18.el8_9 fixed in 2.9.7-19.el8_10 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-6923 | LOW3.47 | python39 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.19-7.module+el8.10.0+90395+b6c4aad1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2024-6923 | LOW3.47 | python39-libs 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.19-7.module+el8.10.0+90395+b6c4aad1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2021-35938 | LOW3.42 | rpm 4.14.3-26.el8 fixed in 4.14.3-28.0.2.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.0.2.el8_9 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-33602 | LOW3.4 | glibc 2.28-236.0.1.el8.7 fixed in 2.28-251.0.2.el8_10.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | glibc-common 2.28-236.0.1.el8.7 fixed in 2.28-251.0.2.el8_10.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | glibc-minimal-langpack 2.28-236.0.1.el8.7 fixed in 2.28-251.0.2.el8_10.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-9820 | LOW3.4 | gnutls 3.6.16-8.el8_9 fixed in 3.6.16-8.el8_10.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-4741 | LOW3.36 | openssl 1:1.1.1k-12.el8_9 fixed in 1:1.1.1k-16.el8_6 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2025-9230 | LOW3.36 | openssl 1:1.1.1k-12.el8_9 fixed in 1:1.1.1k-14.el8_10 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-26007 | LOW3.31 | cryptography 41.0.3 fixed in 46.0.5 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-0727 | LOW3.3 | cryptography 41.0.3 fixed in 42.0.2 | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-49796 | LOW3.28 | libxml2 2.9.7-18.el8_9 fixed in 2.9.7-21.el8_10.1 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2021-35937 | LOW3.26 | rpm 4.14.3-26.el8 fixed in 4.14.3-28.0.2.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-2023-25809 | LOW3.21 | github.com/opencontainers/runc v1.1.0 fixed in 1.1.5 | 0.3% 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-27043 | LOW3.18 | python39 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.18-3.module+el8.10.0+90269+2fa22b99 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-8088 | LOW3.18 | python39 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.19-7.module+el8.10.0+90395+b6c4aad1 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27043 | LOW3.18 | python39-libs 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.18-3.module+el8.10.0+90269+2fa22b99 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-8088 | LOW3.18 | python39-libs 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.19-7.module+el8.10.0+90395+b6c4aad1 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-6345 | LOW3.17 | python39 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.19-7.module+el8.10.0+90395+b6c4aad1 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2025-47273 | LOW3.17 | python39 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.20-2.module+el8.10.0+90647+49247197 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-6345 | LOW3.17 | python39-libs 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.19-7.module+el8.10.0+90395+b6c4aad1 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2025-47273 | LOW3.17 | python39-libs 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.20-2.module+el8.10.0+90647+49247197 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-0450 | LOW3.16 | python39 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.19-1.module+el8.10.0+90341+71ca88f4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-0450 | LOW3.16 | python39-libs 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.19-1.module+el8.10.0+90341+71ca88f4 | 0.3% 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-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-27459 | LOW3 | pyOpenSSL 23.2.0 fixed in 26.0.0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-5318 | LOW2.92 | libssh 0.9.6-10.el8_8 fixed in 0.9.6-15.el8_10 | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2019-17543 | LOW2.92 | lz4-libs 1.8.3-3.el8_4 fixed in 1.8.3-5.el8_10 | 9.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl-libs 1:1.1.1k-12.el8_9 fixed in 1:1.1.1k-16.el8_6 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-43804 | LOW2.92 | python39 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.18-3.module+el8.10.0+90269+2fa22b99 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2020-11023 | LOW2.86 | libgcc 8.5.0-20.0.1.el8 fixed in 8.5.0-23.0.1.el8_10 | 83.8% Actively Exploited | Post-Exploit |
| CVE-2020-11023 | LOW2.86 | libstdc++ 8.5.0-20.0.1.el8 fixed in 8.5.0-23.0.1.el8_10 | 83.8% Actively Exploited | Post-Exploit |
| CVE-2025-6075 | LOW2.8 | python39 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.25-2.module+el8.10.0+90733+27f37730 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-6075 | LOW2.8 | python39-libs 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.25-2.module+el8.10.0+90733+27f37730 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-49794 | LOW2.78 | libxml2 2.9.7-18.el8_9 fixed in 2.9.7-21.el8_10.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-34073 | LOW2.7 | cryptography 41.0.3 fixed in 46.0.6 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27448 | LOW2.7 | pyOpenSSL 23.2.0 fixed in 26.0.0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-4516 | LOW2.6 | python39 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.25-2.module+el8.10.0+90733+27f37730 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-4516 | LOW2.6 | python39-libs 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.25-2.module+el8.10.0+90733+27f37730 | 0.2% 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-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 | python39 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.19-7.module+el8.10.0+90395+b6c4aad1 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4032 | LOW2.22 | python39-libs 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.19-7.module+el8.10.0+90395+b6c4aad1 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-6069 | LOW2.19 | python39 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.25-2.module+el8.10.0+90733+27f37730 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8291 | LOW2.19 | python39 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.25-2.module+el8.10.0+90733+27f37730 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-6069 | LOW2.19 | python39-libs 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.25-2.module+el8.10.0+90733+27f37730 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8291 | LOW2.19 | python39-libs 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.25-2.module+el8.10.0+90733+27f37730 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-6170 | LOW2.12 | libxml2 2.9.7-18.el8_9 fixed in 2.9.7-21.el8_10.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-11168 | LOW1.89 | python39 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.25-2.module+el8.10.0+90733+27f37730 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-11168 | LOW1.89 | python39-libs 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.25-2.module+el8.10.0+90733+27f37730 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-45310 | LOW1.84 | github.com/opencontainers/runc v1.1.0 fixed in 1.1.14, 1.2.0-rc.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-44405 | LOW1.73 | paramiko 2.11.0 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-5642 | LOW1.38 | python39 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.25-2.module+el8.10.0+90733+27f37730 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-5642 | LOW1.38 | python39-libs 3.9.18-1.module+el8.9.0+90071+8dc52a4f fixed in 3.9.25-2.module+el8.10.0+90733+27f37730 | 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-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.3 fixed in 48.0.1 | — | Not Applicable |
| GHSA-h4gh-qq45-vh27 | NONE0 | cryptography 41.0.3 fixed in 43.0.1 | — | Not Applicable |
| GHSA-v8gr-m533-ghj9 | NONE0 | cryptography 41.0.3 fixed in 41.0.4 | — | Not Applicable |
| CVE-2026-41579 | NONE0 | github.com/opencontainers/runc v1.1.0 fixed in 1.3.6, 1.4.3, 1.5.0-rc.3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-39824 | NONE0 | golang.org/x/sys v0.0.0-20220907062415-87db552b00fd 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.