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 are high severity. The overall threat score is 0, suggesting that this image poses minimal risk when used as a building block for other applications. 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-35189 | LOW3.15 | openssl-fips-provider-latest 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35191 | LOW3.15 | openssl-fips-provider-latest 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.15 | openssl-libs 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35191 | LOW3.15 | openssl-libs 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-84782 | LOW2.26 | openssl-fips-provider-latest 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-84782 | LOW2.26 | openssl-libs 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-54872 | LOW1.81 | openssl-fips-provider-latest 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-72897 | LOW1.81 | openssl-fips-provider-latest 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-75805 | LOW1.81 | openssl-fips-provider-latest 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-54872 | LOW1.81 | openssl-libs 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-72897 | LOW1.81 | openssl-libs 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-75805 | LOW1.81 | openssl-libs 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42772 | LOW1.62 | openssl-fips-provider-latest 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54873 | LOW1.62 | openssl-fips-provider-latest 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-75804 | LOW1.62 | openssl-fips-provider-latest 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-75806 | LOW1.62 | openssl-fips-provider-latest 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-84784 | LOW1.62 | openssl-fips-provider-latest 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42772 | LOW1.62 | openssl-libs 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54873 | LOW1.62 | openssl-libs 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-75804 | LOW1.62 | openssl-libs 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-75806 | LOW1.62 | openssl-libs 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-84784 | LOW1.62 | openssl-libs 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-97689 | NONE0 | python3-pip-wheel 21.3.1-2.amzn2023.0.21 fixed in 21.3.1-2.amzn2023.0.22 | 0.3% 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.