Last scanned:
This base/runtime image is a clean foundation for building production images. The image is officially published and highly trusted, and the vulnerability scan found only 4 exposed vulnerabilities, none of which reached a high severity level. The maximum exposed severity is 5.95, and there are no critical findings in the post-exploitation surface. This low risk profile makes it suitable for use as a building block in production environments. 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-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.22 fixed in 1:1.0.2k-24.amzn2.0.23 | 0.3% Theoretical Threat | Directly Exposed |
| 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-84782 | LOW2.26 | openssl-libs 1:1.0.2k-24.amzn2.0.22 fixed in 1:1.0.2k-24.amzn2.0.23 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-54872 | LOW1.81 | openssl-libs 1:1.0.2k-24.amzn2.0.22 fixed in 1:1.0.2k-24.amzn2.0.23 | 0.3% 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.