Last scanned:
This base/runtime image is a clean foundation for building production images. While it carries 9 exposed and 43 post-exploit-only findings, their maximum severities are 5.87 and 3.98 respectively, all below the 6.0 threshold, so they pose no practical risk in this context. The image is an official Docker image pinned by digest, and the threat score of 0 reinforces its safe profile for production use. 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-56132 | MEDIUM5.87 | expat 2.1.0-15.amzn2.0.6 fixed in 2.1.0-15.amzn2.0.7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM5.87 | expat 2.1.0-15.amzn2.0.6 fixed in 2.1.0-15.amzn2.0.8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM5.87 | expat 2.1.0-15.amzn2.0.6 fixed in 2.1.0-15.amzn2.0.8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56407 | MEDIUM5.87 | expat 2.1.0-15.amzn2.0.6 fixed in 2.1.0-15.amzn2.0.8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | openssl-libs 1:1.0.2k-24.amzn2.0.17 fixed in 1:1.0.2k-24.amzn2.0.21 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | krb5-libs 1.15.1-55.amzn2.2.9 fixed in 1.15.1-55.amzn2.2.10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52858 | LOW3.98 | vim-minimal 2:9.0.2153-1.amzn2.0.4 fixed in 2:9.0.2153-1.amzn2.0.7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-52860 | LOW3.98 | vim-minimal 2:9.0.2153-1.amzn2.0.4 fixed in 2:9.0.2153-1.amzn2.0.7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55693 | LOW3.98 | vim-minimal 2:9.0.2153-1.amzn2.0.4 fixed in 2:9.0.2153-1.amzn2.0.8 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-55895 | LOW3.98 | vim-minimal 2:9.0.2153-1.amzn2.0.4 fixed in 2:9.0.2153-1.amzn2.0.8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-57456 | LOW3.98 | vim-minimal 2:9.0.2153-1.amzn2.0.4 fixed in 2:9.0.2153-1.amzn2.0.8 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-41411 | LOW3.72 | vim-minimal 2:9.0.2153-1.amzn2.0.4 fixed in 2:9.0.2153-1.amzn2.0.6 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58051 | LOW3.31 | libssh2 1.4.3-12.amzn2.2.6 fixed in 1.4.3-12.amzn2.2.8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6766 | LOW3.11 | nss-tools 3.90.0-2.amzn2.0.2 fixed in 3.90.0-2.amzn2.0.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6767 | LOW3.11 | nss-tools 3.90.0-2.amzn2.0.2 fixed in 3.90.0-2.amzn2.0.3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6772 | LOW3.11 | nss-tools 3.90.0-2.amzn2.0.2 fixed in 3.90.0-2.amzn2.0.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.11 | python 2.7.18-1.amzn2.0.18 fixed in 2.7.18-1.amzn2.0.20 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.11 | python-libs 2.7.18-1.amzn2.0.18 fixed in 2.7.18-1.amzn2.0.20 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6653 | LOW3 | libxml2 2.9.1-6.amzn2.5.24 fixed in 2.9.1-6.amzn2.5.25 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl-libs 1:1.0.2k-24.amzn2.0.17 fixed in 1:1.0.2k-24.amzn2.0.21 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-58016 | LOW2.78 | glib2 2.56.1-9.amzn2.0.13 fixed in 2.56.1-9.amzn2.0.14 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-7598 | LOW2.78 | libssh2 1.4.3-12.amzn2.2.6 fixed in 1.4.3-12.amzn2.2.7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-28388 | LOW2.7 | openssl-libs 1:1.0.2k-24.amzn2.0.17 fixed in 1:1.0.2k-24.amzn2.0.20 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28389 | LOW2.7 | openssl-libs 1:1.0.2k-24.amzn2.0.17 fixed in 1:1.0.2k-24.amzn2.0.20 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28390 | LOW2.7 | openssl-libs 1:1.0.2k-24.amzn2.0.17 fixed in 1:1.0.2k-24.amzn2.0.20 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-47167 | LOW2.7 | vim-minimal 2:9.0.2153-1.amzn2.0.4 fixed in 2:9.0.2153-1.amzn2.0.7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-47162 | LOW2.69 | vim-minimal 2:9.0.2153-1.amzn2.0.4 fixed in 2:9.0.2153-1.amzn2.0.7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-34982 | LOW2.51 | vim-minimal 2:9.0.2153-1.amzn2.0.4 fixed in 2:9.0.2153-1.amzn2.0.5 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | LOW2.48 | python 2.7.18-1.amzn2.0.18 fixed in 2.7.18-1.amzn2.0.19 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | LOW2.48 | python-libs 2.7.18-1.amzn2.0.18 fixed in 2.7.18-1.amzn2.0.19 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-58050 | LOW2.29 | libssh2 1.4.3-12.amzn2.2.6 fixed in 1.4.3-12.amzn2.2.8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4786 | LOW2.17 | python 2.7.18-1.amzn2.0.18 fixed in 2.7.18-1.amzn2.0.19 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-4786 | LOW2.17 | python-libs 2.7.18-1.amzn2.0.18 fixed in 2.7.18-1.amzn2.0.19 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW1.99 | python 2.7.18-1.amzn2.0.18 fixed in 2.7.18-1.amzn2.0.21 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW1.99 | python-libs 2.7.18-1.amzn2.0.18 fixed in 2.7.18-1.amzn2.0.21 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6766 | LOW1.87 | nss 3.90.0-2.amzn2.0.2 fixed in 3.90.0-2.amzn2.0.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6767 | LOW1.87 | nss 3.90.0-2.amzn2.0.2 fixed in 3.90.0-2.amzn2.0.3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6772 | LOW1.87 | nss 3.90.0-2.amzn2.0.2 fixed in 3.90.0-2.amzn2.0.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6766 | LOW1.87 | nss-sysinit 3.90.0-2.amzn2.0.2 fixed in 3.90.0-2.amzn2.0.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6767 | LOW1.87 | nss-sysinit 3.90.0-2.amzn2.0.2 fixed in 3.90.0-2.amzn2.0.3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6772 | LOW1.87 | nss-sysinit 3.90.0-2.amzn2.0.2 fixed in 3.90.0-2.amzn2.0.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW1.81 | openssl-libs 1:1.0.2k-24.amzn2.0.17 fixed in 1:1.0.2k-24.amzn2.0.21 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-34180 | LOW1.8 | openssl-libs 1:1.0.2k-24.amzn2.0.17 fixed in 1:1.0.2k-24.amzn2.0.21 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4046 | LOW1.62 | glibc 2.26-64.amzn2.0.5 fixed in 2.26-64.amzn2.0.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4046 | LOW1.62 | glibc-common 2.26-64.amzn2.0.5 fixed in 2.26-64.amzn2.0.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4046 | LOW1.62 | glibc-langpack-en 2.26-64.amzn2.0.5 fixed in 2.26-64.amzn2.0.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4046 | LOW1.62 | glibc-minimal-langpack 2.26-64.amzn2.0.5 fixed in 2.26-64.amzn2.0.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4046 | LOW1.62 | libcrypt 2.26-64.amzn2.0.5 fixed in 2.26-64.amzn2.0.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42766 | LOW1.62 | openssl-libs 1:1.0.2k-24.amzn2.0.17 fixed in 1:1.0.2k-24.amzn2.0.21 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-47162 | NONE0 | vim-data 2:9.0.2153-1.amzn2.0.4 fixed in 2:9.0.2153-1.amzn2.0.7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-34982 | NONE0 | vim-data 2:9.0.2153-1.amzn2.0.4 fixed in 2:9.0.2153-1.amzn2.0.5 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52858 | NONE0 | vim-data 2:9.0.2153-1.amzn2.0.4 fixed in 2:9.0.2153-1.amzn2.0.7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52860 | NONE0 | vim-data 2:9.0.2153-1.amzn2.0.4 fixed in 2:9.0.2153-1.amzn2.0.7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55693 | NONE0 | vim-data 2:9.0.2153-1.amzn2.0.4 fixed in 2:9.0.2153-1.amzn2.0.8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55895 | NONE0 | vim-data 2:9.0.2153-1.amzn2.0.4 fixed in 2:9.0.2153-1.amzn2.0.8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57456 | NONE0 | vim-data 2:9.0.2153-1.amzn2.0.4 fixed in 2:9.0.2153-1.amzn2.0.8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-41411 | NONE0 | vim-data 2:9.0.2153-1.amzn2.0.4 fixed in 2:9.0.2153-1.amzn2.0.6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-47167 | NONE0 | vim-data 2:9.0.2153-1.amzn2.0.4 fixed in 2:9.0.2153-1.amzn2.0.7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid 2.30.2-2.amzn2.0.13 fixed in 2.30.2-2.amzn2.0.14 | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount 2.30.2-2.amzn2.0.13 fixed in 2.30.2-2.amzn2.0.14 | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libuuid 2.30.2-2.amzn2.0.13 fixed in 2.30.2-2.amzn2.0.14 | — | 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.
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.