Last scanned:
This base/runtime image is a clean foundation for building production images. It is an official, digest-pinned Docker image with a trust score of 100. The provided stats do show 5 exposed-surface findings and 32 post-exploit-only findings, but their max severities are 5.95 and 3.98 respectively, with zero findings at severity 6.0 or higher, so they do not meet the thresholds for higher verdict bands. No CVE IDs are present in the provided top findings, so no specific vulnerability is called out for remediation in this assessment. Images built on this base inherit that low-risk posture, but teams should still scan the final image after adding application layers. 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-78367 | MEDIUM5.95 | python2-rpm 4.11.3-48.amzn2.0.5 fixed in 4.11.3-48.amzn2.0.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78367 | MEDIUM5.95 | rpm-build-libs 4.11.3-48.amzn2.0.5 fixed in 4.11.3-48.amzn2.0.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78367 | MEDIUM5.95 | rpm-libs 4.11.3-48.amzn2.0.5 fixed in 4.11.3-48.amzn2.0.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86137 | MEDIUM5.18 | libxml2 2.9.1-6.amzn2.5.26 fixed in 2.9.1-6.amzn2.5.27 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-57455 | LOW3.98 | vim-minimal 2:9.0.2153-1.amzn2.0.9 fixed in 2:9.0.2153-1.amzn2.0.11 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-73073 | LOW3.98 | vim-minimal 2:9.0.2153-1.amzn2.0.9 fixed in 2:9.0.2153-1.amzn2.0.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-73076 | LOW3.98 | vim-minimal 2:9.0.2153-1.amzn2.0.9 fixed in 2:9.0.2153-1.amzn2.0.10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-73077 | LOW3.98 | vim-minimal 2:9.0.2153-1.amzn2.0.9 fixed in 2:9.0.2153-1.amzn2.0.10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-73072 | LOW3.72 | vim-minimal 2:9.0.2153-1.amzn2.0.9 fixed in 2:9.0.2153-1.amzn2.0.10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-78367 | LOW3.57 | rpm 4.11.3-48.amzn2.0.5 fixed in 4.11.3-48.amzn2.0.6 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-73074 | LOW3.42 | vim-minimal 2:9.0.2153-1.amzn2.0.9 fixed in 2:9.0.2153-1.amzn2.0.10 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-35189 | LOW3.15 | openssl-libs 1:1.0.2k-24.amzn2.0.21 fixed in 1:1.0.2k-24.amzn2.0.23 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-55892 | LOW2.8 | vim-minimal 2:9.0.2153-1.amzn2.0.9 fixed in 2:9.0.2153-1.amzn2.0.11 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-59857 | LOW2.8 | vim-minimal 2:9.0.2153-1.amzn2.0.9 fixed in 2:9.0.2153-1.amzn2.0.11 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-73078 | LOW2.69 | vim-minimal 2:9.0.2153-1.amzn2.0.9 fixed in 2:9.0.2153-1.amzn2.0.10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-74860 | LOW2.6 | libxml2 2.9.1-6.amzn2.5.26 fixed in 2.9.1-6.amzn2.5.27 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-52859 | LOW2.51 | vim-minimal 2:9.0.2153-1.amzn2.0.9 fixed in 2:9.0.2153-1.amzn2.0.11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | LOW2.48 | curl 8.3.0-1.amzn2.0.12 fixed in 8.3.0-1.amzn2.0.13 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | LOW2.48 | libcurl 8.3.0-1.amzn2.0.12 fixed in 8.3.0-1.amzn2.0.13 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-86138 | LOW2.39 | libxml2 2.9.1-6.amzn2.5.26 fixed in 2.9.1-6.amzn2.5.27 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-86140 | LOW2.39 | libxml2 2.9.1-6.amzn2.5.26 fixed in 2.9.1-6.amzn2.5.27 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-86142 | LOW2.39 | libxml2 2.9.1-6.amzn2.5.26 fixed in 2.9.1-6.amzn2.5.27 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-86144 | LOW2.39 | libxml2 2.9.1-6.amzn2.5.26 fixed in 2.9.1-6.amzn2.5.27 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW2.29 | curl 8.3.0-1.amzn2.0.12 fixed in 8.3.0-1.amzn2.0.13 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-66046 | LOW2.29 | expat 2.1.0-15.amzn2.0.8 fixed in 2.1.0-15.amzn2.0.9 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW2.29 | libcurl 8.3.0-1.amzn2.0.12 fixed in 8.3.0-1.amzn2.0.13 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-54874 | LOW2.29 | openssl-libs 1:1.0.2k-24.amzn2.0.21 fixed in 1:1.0.2k-24.amzn2.0.22 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63072 | LOW2.29 | openssl-libs 1:1.0.2k-24.amzn2.0.21 fixed in 1:1.0.2k-24.amzn2.0.22 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-84782 | LOW2.26 | openssl-libs 1:1.0.2k-24.amzn2.0.21 fixed in 1:1.0.2k-24.amzn2.0.23 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-86143 | LOW2.23 | libxml2 2.9.1-6.amzn2.5.26 fixed in 2.9.1-6.amzn2.5.27 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW1.99 | curl 8.3.0-1.amzn2.0.12 fixed in 8.3.0-1.amzn2.0.13 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW1.99 | libcurl 8.3.0-1.amzn2.0.12 fixed in 8.3.0-1.amzn2.0.13 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-13608 | LOW1.89 | curl 8.3.0-1.amzn2.0.12 fixed in 8.3.0-1.amzn2.0.13 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.89 | curl 8.3.0-1.amzn2.0.12 fixed in 8.3.0-1.amzn2.0.13 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13608 | LOW1.89 | libcurl 8.3.0-1.amzn2.0.12 fixed in 8.3.0-1.amzn2.0.13 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.89 | libcurl 8.3.0-1.amzn2.0.12 fixed in 8.3.0-1.amzn2.0.13 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-54872 | LOW1.81 | openssl-libs 1:1.0.2k-24.amzn2.0.21 fixed in 1:1.0.2k-24.amzn2.0.23 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-73078 | NONE0 | vim-data 2:9.0.2153-1.amzn2.0.9 fixed in 2:9.0.2153-1.amzn2.0.10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52859 | NONE0 | vim-data 2:9.0.2153-1.amzn2.0.9 fixed in 2:9.0.2153-1.amzn2.0.11 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-57455 | NONE0 | vim-data 2:9.0.2153-1.amzn2.0.9 fixed in 2:9.0.2153-1.amzn2.0.11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-73073 | NONE0 | vim-data 2:9.0.2153-1.amzn2.0.9 fixed in 2:9.0.2153-1.amzn2.0.11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-73076 | NONE0 | vim-data 2:9.0.2153-1.amzn2.0.9 fixed in 2:9.0.2153-1.amzn2.0.10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-73077 | NONE0 | vim-data 2:9.0.2153-1.amzn2.0.9 fixed in 2:9.0.2153-1.amzn2.0.10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-73072 | NONE0 | vim-data 2:9.0.2153-1.amzn2.0.9 fixed in 2:9.0.2153-1.amzn2.0.10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-73074 | NONE0 | vim-data 2:9.0.2153-1.amzn2.0.9 fixed in 2:9.0.2153-1.amzn2.0.10 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55892 | NONE0 | vim-data 2:9.0.2153-1.amzn2.0.9 fixed in 2:9.0.2153-1.amzn2.0.11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-59857 | NONE0 | vim-data 2:9.0.2153-1.amzn2.0.9 fixed in 2:9.0.2153-1.amzn2.0.11 | 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.