Last scanned:
This base/runtime image is a clean foundation for building production images. It does ship some inherited findings: 11 exposed-surface findings and 16 post-exploit-only findings are reported. However, none of those reach severity 6.0 or higher, with maximum severities of 5.95 and 3.57 respectively, and no top findings with CVE IDs were provided. The image is an official Docker Hub image pinned by digest, and its pre-calculated threat score is 0. Any images built on it should still follow normal dependency and vulnerability scanning, but the current inputs do not indicate a production-blocking inherited risk. 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-66046 | MEDIUM5.1 | expat 2.1.0-15.amzn2.0.8 fixed in 2.1.0-15.amzn2.0.9 | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-74860 | MEDIUM4.33 | libxml2 2.9.1-6.amzn2.5.26 fixed in 2.9.1-6.amzn2.5.27 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54874 | LOW3.83 | openssl-libs 1:1.0.2k-24.amzn2.0.21 fixed in 1:1.0.2k-24.amzn2.0.22 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63072 | LOW3.83 | openssl-libs 1:1.0.2k-24.amzn2.0.21 fixed in 1:1.0.2k-24.amzn2.0.22 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-84782 | LOW3.77 | openssl-libs 1:1.0.2k-24.amzn2.0.21 fixed in 1:1.0.2k-24.amzn2.0.23 | 0.4% Theoretical Threat | Directly Exposed |
| 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-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-54872 | LOW3.01 | 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-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-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-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 |
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.