Last scanned:
This base/runtime image is a clean foundation for building production images. It is an official Docker Hub image pinned by digest, which supports its trusted reputation. Although the scan reports 18 exposed and 25 post-exploit-only findings, none reach severity 6.0; the maximum exposed severity is 5.95 and the maximum post-exploit severity is 3.57. No CVE IDs appear in the provided top findings, so there is no specific high-impact inherited issue to remediate before using it as a base. 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 | python3-rpm 4.16.1.3-29.amzn2023.0.7 fixed in 4.16.1.3-29.amzn2023.0.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-84233 | MEDIUM5.95 | python3-rpm 4.16.1.3-29.amzn2023.0.7 fixed in 4.16.1.3-29.amzn2023.0.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78367 | MEDIUM5.95 | rpm-build-libs 4.16.1.3-29.amzn2023.0.7 fixed in 4.16.1.3-29.amzn2023.0.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-84233 | MEDIUM5.95 | rpm-build-libs 4.16.1.3-29.amzn2023.0.7 fixed in 4.16.1.3-29.amzn2023.0.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78367 | MEDIUM5.95 | rpm-libs 4.16.1.3-29.amzn2023.0.7 fixed in 4.16.1.3-29.amzn2023.0.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-84233 | MEDIUM5.95 | rpm-libs 4.16.1.3-29.amzn2023.0.7 fixed in 4.16.1.3-29.amzn2023.0.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78367 | MEDIUM5.95 | rpm-sign-libs 4.16.1.3-29.amzn2023.0.7 fixed in 4.16.1.3-29.amzn2023.0.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-84233 | MEDIUM5.95 | rpm-sign-libs 4.16.1.3-29.amzn2023.0.7 fixed in 4.16.1.3-29.amzn2023.0.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86137 | MEDIUM5.18 | libxml2 2.10.4-1.amzn2023.0.20 fixed in 2.10.4-1.amzn2023.0.21 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM4.5 | 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-84784 | MEDIUM4.5 | 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-75804 | MEDIUM4.5 | 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-75806 | MEDIUM4.5 | 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-84784 | MEDIUM4.5 | 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-78367 | LOW3.57 | rpm 4.16.1.3-29.amzn2023.0.7 fixed in 4.16.1.3-29.amzn2023.0.8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-84233 | LOW3.57 | rpm 4.16.1.3-29.amzn2023.0.7 fixed in 4.16.1.3-29.amzn2023.0.8 | 0.2% Theoretical Threat | Post-Exploit |
| 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-74860 | LOW2.6 | libxml2 2.10.4-1.amzn2023.0.20 fixed in 2.10.4-1.amzn2023.0.21 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-86138 | LOW2.39 | libxml2 2.10.4-1.amzn2023.0.20 fixed in 2.10.4-1.amzn2023.0.21 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-86140 | LOW2.39 | libxml2 2.10.4-1.amzn2023.0.20 fixed in 2.10.4-1.amzn2023.0.21 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-86142 | LOW2.39 | libxml2 2.10.4-1.amzn2023.0.20 fixed in 2.10.4-1.amzn2023.0.21 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-86144 | LOW2.39 | libxml2 2.10.4-1.amzn2023.0.20 fixed in 2.10.4-1.amzn2023.0.21 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-89161 | LOW2.39 | pcre2 10.40-1.amzn2023.0.3 fixed in 10.40-1.amzn2023.0.4 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-97689 | LOW2.29 | python3-pip-wheel 21.3.1-2.amzn2023.0.21 fixed in 21.3.1-2.amzn2023.0.22 | 0.3% Theoretical Threat | Post-Exploit |
| 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-86143 | LOW2.23 | libxml2 2.10.4-1.amzn2023.0.20 fixed in 2.10.4-1.amzn2023.0.21 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.89 | curl-minimal 8.21.0-5.amzn2023.0.1 fixed in 8.21.0-5.amzn2023.0.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.89 | libcurl-minimal 8.21.0-5.amzn2023.0.1 fixed in 8.21.0-5.amzn2023.0.2 | 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-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-89161 | NONE0 | pcre2-syntax 10.40-1.amzn2023.0.3 fixed in 10.40-1.amzn2023.0.4 | 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.