Last scanned:
This base/runtime image carries significant vulnerabilities that any image built on it would inherit; remediate them in the final image before production. An attacker exploiting the GnuTLS certificate validation bypass (CVE-2026-42011) could spoof a legitimate service or intercept sensitive communications; the OpenSSL CMS flaw (CVE-2026-34182) could allow forging authenticated messages. While no finding reaches critical severity, the cumulative exposure (80 findings) means any image built on this base should use updated packages; note that CVE-2026-40356 (krb5) only applies when a NegoEx mechanism is registered, limiting its real-world reach. Note: this is a general-purpose base/runtime image — many findings live in components that an application built on top may never load, so actual exploitability depends on the final image. For an accurate risk picture, re-scan the final application image with context.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-45186 | MEDIUM6.38 | expat 2.7.1-1.el10_1.3 fixed in 2.7.3-1.el10_2.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | krb5-libs 1.21.3-9.el10_1 fixed in 1.21.3-10.el10_2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.38 | python3-libs 3.12.12-3.el10_1.3 fixed in 3.12.13-2.el10_2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3833 | MEDIUM6.29 | gnutls 3.8.10-3.el10_1 fixed in 3.8.10-4.el10_2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM6.29 | gnutls 3.8.10-3.el10_1 fixed in 3.8.10-4.el10_2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | openssl-libs 1:3.5.1-7.el10_1.alma.1 fixed in 1:3.5.5-4.el10_2.alma.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM6.03 | gnutls 3.8.10-3.el10_1 fixed in 3.8.10-4.el10_2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54369 | MEDIUM6.03 | libacl 2.3.2-4.el10 fixed in 2.4.0-1.el10_2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4786 | MEDIUM6.03 | python3-libs 3.12.12-3.el10_1.3 fixed in 3.12.13-2.el10_2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4878 | MEDIUM5.95 | libcap 2.69-7.el10_1.1 fixed in 2.69-7.el10_2.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1 4.20.0-1.el10 fixed in 4.20.0-5.el10_2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.9 | openssl-libs 1:3.5.1-7.el10_1.alma.1 fixed in 1:3.5.5-4.el10_2.alma.1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.9 | openssl-libs 1:3.5.1-7.el10_1.alma.1 fixed in 1:3.5.5-2.el10_2.alma.1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42010 | MEDIUM5.88 | gnutls 3.8.10-3.el10_1 fixed in 3.8.10-4.el10_2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.61 | gnutls 3.8.10-3.el10_1 fixed in 3.8.10-4.el10_2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14512 | MEDIUM5.52 | glib2 2.80.4-10.el10_1.12 fixed in 2.80.4-12.el10_2.13 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc 2.39-58.el10_1.7.alma.1 fixed in 2.39-121.el10_2.alma.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | glibc 2.39-58.el10_1.7.alma.1 fixed in 2.39-128.el10_2.alma.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc-common 2.39-58.el10_1.7.alma.1 fixed in 2.39-121.el10_2.alma.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | glibc-common 2.39-58.el10_1.7.alma.1 fixed in 2.39-128.el10_2.alma.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc-minimal-langpack 2.39-58.el10_1.7.alma.1 fixed in 2.39-121.el10_2.alma.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | glibc-minimal-langpack 2.39-58.el10_1.7.alma.1 fixed in 2.39-128.el10_2.alma.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9149 | MEDIUM5.52 | libsolv 0.7.29-8.el10.alma.1 fixed in 0.7.33-5.el10_2.alma.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-9150 | MEDIUM5.52 | libsolv 0.7.29-8.el10.alma.1 fixed in 0.7.33-5.el10_2.alma.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-34459 | MEDIUM5.5 | libxml2 2.12.5-9.el10_0 fixed in 2.12.5-10.el10_2.1 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54370 | MEDIUM5.35 | libacl 2.3.2-4.el10 fixed in 2.4.0-1.el10_2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM5.35 | openssl-libs 1:3.5.1-7.el10_1.alma.1 fixed in 1:3.5.5-4.el10_2.alma.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | openssl-libs 1:3.5.1-7.el10_1.alma.1 fixed in 1:3.5.5-4.el10_2.alma.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-59375 | MEDIUM5.3 | python3-libs 3.12.12-3.el10_1.3 fixed in 3.12.13-2.el10_2 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc 2.39-58.el10_1.7.alma.1 fixed in 2.39-128.el10_2.alma.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc-common 2.39-58.el10_1.7.alma.1 fixed in 2.39-128.el10_2.alma.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc-minimal-langpack 2.39-58.el10_1.7.alma.1 fixed in 2.39-128.el10_2.alma.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.02 | openssl-libs 1:3.5.1-7.el10_1.alma.1 fixed in 1:3.5.5-4.el10_2.alma.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | openssl-libs 1:3.5.1-7.el10_1.alma.1 fixed in 1:3.5.5-4.el10_2.alma.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | openssl-libs 1:3.5.1-7.el10_1.alma.1 fixed in 1:3.5.5-4.el10_2.alma.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-14087 | MEDIUM5 | glib2 2.80.4-10.el10_1.12 fixed in 2.80.4-12.el10_2.13 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | openssl-libs 1:3.5.1-7.el10_1.alma.1 fixed in 1:3.5.5-4.el10_2.alma.1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45447 | MEDIUM4.86 | openssl-libs 1:3.5.1-7.el10_1.alma.1 fixed in 1:3.5.5-4.el10_2.alma.1 | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | openssl-libs 1:3.5.1-7.el10_1.alma.1 fixed in 1:3.5.5-4.el10_2.alma.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM4.67 | python3-libs 3.12.12-3.el10_1.3 fixed in 3.12.13-2.el10_2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6075 | MEDIUM4.67 | python3-libs 3.12.12-3.el10_1.3 fixed in 3.12.13-2.el10_2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | MEDIUM4.64 | glib2 2.80.4-10.el10_1.12 fixed in 2.80.4-12.el10_2.14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33845 | MEDIUM4.64 | gnutls 3.8.10-3.el10_1 fixed in 3.8.10-4.el10_2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | MEDIUM4.64 | openssl-libs 1:3.5.1-7.el10_1.alma.1 fixed in 1:3.5.5-4.el10_2.alma.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33846 | MEDIUM4.5 | gnutls 3.8.10-3.el10_1 fixed in 3.8.10-4.el10_2 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42009 | MEDIUM4.5 | gnutls 3.8.10-3.el10_1 fixed in 3.8.10-4.el10_2 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34183 | MEDIUM4.5 | openssl-libs 1:3.5.1-7.el10_1.alma.1 fixed in 1:3.5.5-4.el10_2.alma.1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28390 | MEDIUM4.5 | openssl-libs 1:3.5.1-7.el10_1.alma.1 fixed in 1:3.5.5-3.el10_2.alma.1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-2100 | MEDIUM4.5 | p11-kit 0.25.5-7.el10 fixed in 0.26.2-1.el10 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-2100 | MEDIUM4.5 | p11-kit-trust 0.25.5-7.el10 fixed in 0.26.2-1.el10 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc 2.39-58.el10_1.7.alma.1 fixed in 2.39-124.el10_2.alma.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-common 2.39-58.el10_1.7.alma.1 fixed in 2.39-124.el10_2.alma.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-minimal-langpack 2.39-58.el10_1.7.alma.1 fixed in 2.39-124.el10_2.alma.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM4.5 | gnutls 3.8.10-3.el10_1 fixed in 3.8.10-4.el10_2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | openssl-libs 1:3.5.1-7.el10_1.alma.1 fixed in 1:3.5.5-4.el10_2.alma.1 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | openssl-libs 1:3.5.1-7.el10_1.alma.1 fixed in 1:3.5.5-4.el10_2.alma.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc 2.39-58.el10_1.7.alma.1 fixed in 2.39-126.el10_2.alma.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc 2.39-58.el10_1.7.alma.1 fixed in 2.39-128.el10_2.alma.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-common 2.39-58.el10_1.7.alma.1 fixed in 2.39-126.el10_2.alma.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc-common 2.39-58.el10_1.7.alma.1 fixed in 2.39-128.el10_2.alma.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-minimal-langpack 2.39-58.el10_1.7.alma.1 fixed in 2.39-126.el10_2.alma.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc-minimal-langpack 2.39-58.el10_1.7.alma.1 fixed in 2.39-128.el10_2.alma.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42013 | MEDIUM4.18 | gnutls 3.8.10-3.el10_1 fixed in 3.8.10-4.el10_2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM4.18 | gnutls 3.8.10-3.el10_1 fixed in 3.8.10-4.el10_2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-6100 | MEDIUM4.13 | python3-libs 3.12.12-3.el10_1.3 fixed in 3.12.13-2.el10_2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | MEDIUM4.08 | python3-libs 3.12.12-3.el10_1.3 fixed in 3.12.13-2.el10_2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.08 | python3-libs 3.12.12-3.el10_1.3 fixed in 3.12.13-2.el10_2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | LOW3.83 | krb5-libs 1.21.3-9.el10_1 fixed in 1.21.3-10.el10_2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | LOW3.83 | python3-libs 3.12.12-3.el10_1.3 fixed in 3.12.13-2.el10_2.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | LOW3.83 | python3-libs 3.12.12-3.el10_1.3 fixed in 3.12.13-2.el10_2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | python3-libs 3.12.12-3.el10_1.3 fixed in 3.12.13-2.el10_2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-35177 | LOW3.62 | vim-minimal 2:9.1.083-6.el10_1.4 fixed in 2:9.1.083-9.el10_2.3 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4438 | LOW3.4 | glibc 2.39-58.el10_1.7.alma.1 fixed in 2.39-121.el10_2.alma.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | glibc-common 2.39-58.el10_1.7.alma.1 fixed in 2.39-121.el10_2.alma.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | glibc-minimal-langpack 2.39-58.el10_1.7.alma.1 fixed in 2.39-121.el10_2.alma.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3832 | LOW3.15 | gnutls 3.8.10-3.el10_1 fixed in 3.8.10-4.el10_2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-5419 | LOW3.15 | gnutls 3.8.10-3.el10_1 fixed in 3.8.10-4.el10_2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | openssl-libs 1:3.5.1-7.el10_1.alma.1 fixed in 1:3.5.5-4.el10_2.alma.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | LOW2.8 | python3 3.12.12-3.el10_1.3 fixed in 3.12.13-2.el10_2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6075 | LOW2.8 | python3 3.12.12-3.el10_1.3 fixed in 3.12.13-2.el10_2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW2.8 | python3-libs 3.12.12-3.el10_1.3 fixed in 3.12.13-2.el10_2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | python3-libs 3.12.12-3.el10_1.3 fixed in 3.12.13-2.el10_2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-48964 | LOW2.7 | iputils 20240905-4.el10 fixed in 20240905-5.el10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-34982 | LOW2.51 | vim-minimal 2:9.1.083-6.el10_1.4 fixed in 2:9.1.083-9.el10_2.2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | LOW2.48 | python3 3.12.12-3.el10_1.3 fixed in 3.12.13-2.el10_2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | LOW2.45 | python3 3.12.12-3.el10_1.3 fixed in 3.12.13-2.el10_2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.45 | python3 3.12.12-3.el10_1.3 fixed in 3.12.13-2.el10_2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48864 | LOW2.39 | libsolv 0.7.29-8.el10.alma.1 fixed in 0.7.33-5.el10_2.alma.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-29111 | LOW2.39 | systemd-libs 257-13.el10.alma.1 fixed in 257-23.el10_2.1.alma.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-15308 | LOW2.29 | python3 3.12.12-3.el10_1.3 fixed in 3.12.13-2.el10_2.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3644 | LOW2.29 | python3 3.12.12-3.el10_1.3 fixed in 3.12.13-2.el10_2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW2.29 | python3 3.12.12-3.el10_1.3 fixed in 3.12.13-2.el10_2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW2.29 | python3 3.12.12-3.el10_1.3 fixed in 3.12.13-2.el10_2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils-single 9.5-6.el10 fixed in 9.5-8.el10_2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4786 | LOW2.17 | python3 3.12.12-3.el10_1.3 fixed in 3.12.13-2.el10_2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-6170 | LOW2.12 | libxml2 2.12.5-9.el10_0 fixed in 2.12.5-10.el10_2.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59375 | LOW1.91 | python3 3.12.12-3.el10_1.3 fixed in 3.12.13-2.el10_2 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-2297 | LOW1.68 | python3 3.12.12-3.el10_1.3 fixed in 3.12.13-2.el10_2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4519 | LOW1.68 | python3 3.12.12-3.el10_1.3 fixed in 3.12.13-2.el10_2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-34982 | NONE0 | vim-data 2:9.1.083-6.el10_1.4 fixed in 2:9.1.083-9.el10_2.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-29111 | NONE0 | systemd 257-13.el10.alma.1 fixed in 257-23.el10_2.1.alma.1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-29111 | NONE0 | systemd-pam 257-13.el10.alma.1 fixed in 257-23.el10_2.1.alma.1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-41411 | NONE0 | vim-data 2:9.1.083-6.el10_1.4 fixed in 2:9.1.083-9.el10_2.4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-35177 | NONE0 | vim-data 2:9.1.083-6.el10_1.4 fixed in 2:9.1.083-9.el10_2.3 | 0.1% Theoretical Threat | Not Applicable |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.