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-2026-42010 to bypass authentication and gain unauthorized access to the database. Disabling RSA-PSK ciphersuites would fully mitigate this vulnerability. Note: CVE-2026-42010 only applies if RSA-PSK is enabled in the TLS configuration. The image also contains 51 other vulnerabilities, with two additional high-severity issues affecting certificate validation.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-42010 | HIGH7.84 | gnutls 3.8.3-10.el9_7 fixed in 3.8.10-4.el9_8 | 1.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42011 | MEDIUM6.29 | gnutls 3.8.3-10.el9_7 fixed in 3.8.10-4.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM6.03 | gnutls 3.8.3-10.el9_7 fixed in 3.8.10-4.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4878 | MEDIUM5.95 | libcap 2.48-10.el9 fixed in 2.48-10.el9_8.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1 4.16.0-9.el9 fixed in 4.16.0-10.el9_8 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.61 | gnutls 3.8.3-10.el9_7 fixed in 3.8.10-4.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42013 | MEDIUM5.58 | gnutls 3.8.3-10.el9_7 fixed in 3.8.10-4.el9_8 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-5260 | MEDIUM5.58 | gnutls 3.8.3-10.el9_7 fixed in 3.8.10-4.el9_8 | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-14512 | MEDIUM5.52 | glib2 2.68.4-18.el9_7.1 fixed in 2.68.4-19.el9_8.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc 2.34-231.0.1.el9_7.10 fixed in 2.34-270.0.1.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc-common 2.34-231.0.1.el9_7.10 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-231.0.1.el9_7.10 fixed in 2.34-270.0.1.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5351 | MEDIUM5.52 | libssh 0.10.4-17.el9_7 fixed in 0.10.4-18.el9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-34459 | MEDIUM5.5 | libxml2 2.9.13-14.el9_7 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-17.el9_7 fixed in 0.10.4-18.el9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM5.35 | openssl-libs 1:3.5.1-7.0.1.el9_7 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.5.1-7.0.1.el9_7 fixed in 1:3.5.5-4.0.1.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM5.1 | krb5-libs 1.21.1-8.0.1.el9_6 fixed in 1.21.1-10.0.1.el9_8 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-40356 | MEDIUM5.1 | krb5-libs 1.21.1-8.0.1.el9_6 fixed in 1.21.1-10.0.1.el9_8 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-3833 | MEDIUM5.03 | gnutls 3.8.3-10.el9_7 fixed in 3.8.10-4.el9_8 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-31790 | MEDIUM5.02 | openssl-libs 1:3.5.1-7.0.1.el9_7 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.5.1-7.0.1.el9_7 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.5.1-7.0.1.el9_7 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.5.1-7.0.1.el9_7 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.5.1-7.0.1.el9_7 fixed in 1:3.5.5-4.0.1.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0967 | MEDIUM4.67 | libssh 0.10.4-17.el9_7 fixed in 0.10.4-18.el9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | openssl-libs 1:3.5.1-7.0.1.el9_7 fixed in 1:3.5.5-4.0.1.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc 2.34-231.0.1.el9_7.10 fixed in 2.34-270.0.1.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-common 2.34-231.0.1.el9_7.10 fixed in 2.34-270.0.1.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-minimal-langpack 2.34-231.0.1.el9_7.10 fixed in 2.34-270.0.1.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM4.5 | gnutls 3.8.3-10.el9_7 fixed in 3.8.10-4.el9_8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | openssl-libs 1:3.5.1-7.0.1.el9_7 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.5.1-7.0.1.el9_7 fixed in 1:3.5.5-4.0.1.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc 2.34-231.0.1.el9_7.10 fixed in 2.34-272.0.1.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-common 2.34-231.0.1.el9_7.10 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-231.0.1.el9_7.10 fixed in 2.34-272.0.1.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM4.25 | openssl-libs 1:3.5.1-7.0.1.el9_7 fixed in 1:3.5.5-4.0.1.el9_8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-8114 | MEDIUM4 | libssh 0.10.4-17.el9_7 fixed in 0.10.4-18.el9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4877 | LOW3.82 | libssh 0.10.4-17.el9_7 fixed in 0.10.4-18.el9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | glibc 2.34-231.0.1.el9_7.10 fixed in 2.34-270.0.1.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | glibc-common 2.34-231.0.1.el9_7.10 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-231.0.1.el9_7.10 fixed in 2.34-270.0.1.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | LOW3.21 | openssl 1:3.5.1-7.0.1.el9_7 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.5.1-7.0.1.el9_7 fixed in 1:3.5.5-4.0.1.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3832 | LOW3.15 | gnutls 3.8.3-10.el9_7 fixed in 3.8.10-4.el9_8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-5419 | LOW3.15 | gnutls 3.8.3-10.el9_7 fixed in 3.8.10-4.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | openssl-libs 1:3.5.1-7.0.1.el9_7 fixed in 1:3.5.5-4.0.1.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4878 | LOW3.06 | libssh 0.10.4-17.el9_7 fixed in 0.10.4-18.el9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | LOW3.01 | openssl 1:3.5.1-7.0.1.el9_7 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.5.1-7.0.1.el9_7 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.5.1-7.0.1.el9_7 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-18.el9_7.1 fixed in 2.68.4-19.el9_8.1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-39892 | LOW3 | cryptography 45.0.7 fixed in 46.0.7 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-27459 | LOW3 | pyOpenSSL 25.1.0 fixed in 26.0.0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-6357 | LOW2.96 | pip 25.2 fixed in 26.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl 1:3.5.1-7.0.1.el9_7 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.5.1-7.0.1.el9_7 fixed in 1:3.5.5-4.0.1.el9_8 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-7383 | LOW2.8 | openssl 1:3.5.1-7.0.1.el9_7 fixed in 1:3.5.5-4.0.1.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8643 | LOW2.8 | pip 25.2 fixed in 26.1.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-0965 | LOW2.8 | libssh 0.10.4-17.el9_7 fixed in 0.10.4-18.el9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-33845 | LOW2.78 | gnutls 3.8.3-10.el9_7 fixed in 3.8.10-4.el9_8 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | LOW2.78 | openssl 1:3.5.1-7.0.1.el9_7 fixed in 1:3.5.5-4.0.1.el9_8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | LOW2.78 | openssl-libs 1:3.5.1-7.0.1.el9_7 fixed in 1:3.5.5-4.0.1.el9_8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-33846 | LOW2.7 | gnutls 3.8.3-10.el9_7 fixed in 3.8.10-4.el9_8 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42009 | LOW2.7 | gnutls 3.8.3-10.el9_7 fixed in 3.8.10-4.el9_8 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-2100 | LOW2.7 | p11-kit 0.25.3-3.el9_5 fixed in 0.26.2-1.el9 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-2100 | LOW2.7 | p11-kit-trust 0.25.3-3.el9_5 fixed in 0.26.2-1.el9 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42766 | LOW2.7 | openssl 1:3.5.1-7.0.1.el9_7 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.5.1-7.0.1.el9_7 fixed in 1:3.5.5-4.0.1.el9_8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-34073 | LOW2.7 | cryptography 45.0.7 fixed in 46.0.6 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8869 | LOW2.7 | pip 25.2 fixed in 25.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-27448 | LOW2.7 | pyOpenSSL 25.1.0 fixed in 26.0.0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8277 | LOW2.63 | libssh 0.10.4-17.el9_7 fixed in 0.10.4-18.el9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0968 | LOW2.63 | libssh 0.10.4-17.el9_7 fixed in 0.10.4-18.el9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | LOW2.55 | openssl 1:3.5.1-7.0.1.el9_7 fixed in 1:3.5.5-4.0.1.el9_8 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3219 | LOW2.55 | pip 25.2 fixed in 26.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0966 | LOW2.51 | libssh 0.10.4-17.el9_7 fixed in 0.10.4-18.el9 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-48864 | LOW2.39 | libsolv 0.7.24-3.el9 fixed in 0.7.24-6.el9_8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-29111 | LOW2.39 | systemd-libs 252-55.0.3.el9_7.8 fixed in 252-67.0.1.el9_8.2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-28390 | LOW2.29 | openssl 1:3.5.1-7.0.1.el9_7 fixed in 1:3.5.5-4.0.1.el9_8 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-34183 | LOW2.29 | openssl 1:3.5.1-7.0.1.el9_7 fixed in 1:3.5.5-4.0.1.el9_8 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-28390 | LOW2.29 | openssl-libs 1:3.5.1-7.0.1.el9_7 fixed in 1:3.5.5-4.0.1.el9_8 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-34183 | LOW2.29 | openssl-libs 1:3.5.1-7.0.1.el9_7 fixed in 1:3.5.5-4.0.1.el9_8 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69277 | LOW2.29 | PyNaCl 1.5.0 fixed in 1.6.2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW2.26 | openssl 1:3.5.1-7.0.1.el9_7 fixed in 1:3.5.5-4.0.1.el9_8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW2.26 | openssl-libs 1:3.5.1-7.0.1.el9_7 fixed in 1:3.5.5-4.0.1.el9_8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils-single 8.32-39.0.1.el9 fixed in 8.32-41.0.1.el9_8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6170 | LOW2.12 | libxml2 2.9.13-14.el9_7 fixed in 2.9.13-14.el9_8.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-26007 | LOW1.99 | cryptography 45.0.7 fixed in 46.0.5 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1703 | LOW1.99 | pip 25.2 fixed in 26.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-45446 | LOW1.89 | openssl 1:3.5.1-7.0.1.el9_7 fixed in 1:3.5.5-4.0.1.el9_8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31790 | LOW1.81 | openssl 1:3.5.1-7.0.1.el9_7 fixed in 1:3.5.5-2.0.1.el9_8 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-42764 | LOW1.81 | openssl 1:3.5.1-7.0.1.el9_7 fixed in 1:3.5.5-4.0.1.el9_8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-44405 | LOW1.73 | paramiko 4.0.0 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68121 | NONE0 | stdlib v1.24.6 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39822 | NONE0 | stdlib v1.24.6 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-61726 | NONE0 | stdlib v1.24.6 fixed in 1.24.12, 1.25.6 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2025-61729 | NONE0 | stdlib v1.24.6 fixed in 1.24.11, 1.25.5 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-25679 | NONE0 | stdlib v1.24.6 fixed in 1.25.8, 1.26.1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-27145 | NONE0 | stdlib v1.24.6 fixed in 1.25.11, 1.26.4 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-32280 | NONE0 | stdlib v1.24.6 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32281 | NONE0 | stdlib v1.24.6 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-32283 | NONE0 | stdlib v1.24.6 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-33811 | NONE0 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-33814 | NONE0 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39820 | NONE0 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39836 | NONE0 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42499 | NONE0 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42504 | NONE0 | stdlib v1.24.6 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-58183 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61728 | NONE0 | stdlib v1.24.6 fixed in 1.24.12, 1.25.6 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61727 | NONE0 | stdlib v1.24.6 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39825 | NONE0 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32282 | NONE0 | stdlib v1.24.6 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-32289 | NONE0 | stdlib v1.24.6 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-32288 | NONE0 | stdlib v1.24.6 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-27142 | NONE0 | stdlib v1.24.6 fixed in 1.25.8, 1.26.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39823 | NONE0 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39826 | NONE0 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-47912 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58185 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-58187 | NONE0 | stdlib v1.24.6 fixed in 1.24.9, 1.25.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58188 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58189 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61723 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61724 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61725 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61730 | NONE0 | stdlib v1.24.6 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42505 | NONE0 | stdlib v1.24.6 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.24.6 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58186 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-27139 | NONE0 | stdlib v1.24.6 fixed in 1.25.8, 1.26.1 | 0.2% Theoretical Threat | Not Applicable |
| GHSA-537c-gmf6-5ccf | NONE0 | cryptography 45.0.7 fixed in 48.0.1 | — | Not Applicable |
| CVE-2026-39824 | NONE0 | golang.org/x/sys v0.1.0 fixed in 0.44.0 | 0.1% Theoretical Threat | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.