Last scanned:
This base/runtime image is a clean foundation for building production images. It has no exposed vulnerabilities, and the few post-exploit-only findings are very low severity (max 2.7), presenting no practical risk in this context. Being an official image pinned by digest adds an extra layer of integrity and reproducibility for downstream builds. 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-45409 | LOW2.7 | python3-pip-wheel 21.3.1-2.amzn2023.0.20 fixed in 21.3.1-2.amzn2023.0.21 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-14456 | LOW2.29 | openssl-fips-provider-latest 1:3.5.7-2.amzn2023.0.1 fixed in 1:3.5.7-2.amzn2023.0.2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-14456 | LOW2.29 | openssl-libs 1:3.5.7-2.amzn2023.0.1 fixed in 1:3.5.7-2.amzn2023.0.2 | 0.7% 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.