Last scanned:
This image is safe for production use. Although 39 exposed and 52 post-exploit findings are present, all are low severity (max 5.87) and pose no practical threat in this context. The image is officially maintained and pinned by digest.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-56132 | MEDIUM5.87 | expat 2.6.3-1.amzn2023.0.4 fixed in 2.6.3-1.amzn2023.0.5 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM5.87 | expat 2.6.3-1.amzn2023.0.4 fixed in 2.6.3-1.amzn2023.0.6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM5.87 | expat 2.6.3-1.amzn2023.0.4 fixed in 2.6.3-1.amzn2023.0.6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-9149 | MEDIUM5.52 | libsolv 0.7.22-1.amzn2023.0.3 fixed in 0.7.22-1.amzn2023.0.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-9150 | MEDIUM5.52 | libsolv 0.7.22-1.amzn2023.0.3 fixed in 0.7.22-1.amzn2023.0.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54370 | MEDIUM5.35 | libacl 2.3.1-2.amzn2023.0.2 fixed in 2.4.0-1.amzn2023.0.1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM5.35 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.4 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.4 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM5.35 | openssl-libs 1:3.5.5-1.amzn2023.0.4 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | openssl-libs 1:3.5.5-1.amzn2023.0.4 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.02 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.4 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.02 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.4 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.4 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.4 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.02 | openssl-libs 1:3.5.5-1.amzn2023.0.4 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.02 | openssl-libs 1:3.5.5-1.amzn2023.0.4 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | openssl-libs 1:3.5.5-1.amzn2023.0.4 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | openssl-libs 1:3.5.5-1.amzn2023.0.4 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23679 | MEDIUM4.67 | libusbx 1.0.24-2.amzn2023.0.2 fixed in 1.0.24-2.amzn2023.0.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.4 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | openssl-libs 1:3.5.5-1.amzn2023.0.4 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.4 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.4 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | openssl-libs 1:3.5.5-1.amzn2023.0.4 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | openssl-libs 1:3.5.5-1.amzn2023.0.4 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | krb5-libs 1.21.3-7.amzn2023.0.1 fixed in 1.21.3-8.amzn2023.0.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM4.25 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.4 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM4.25 | openssl-libs 1:3.5.5-1.amzn2023.0.4 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.4 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | openssl-libs 1:3.5.5-1.amzn2023.0.4 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | LOW3.01 | python3 3.9.25-1.amzn2023.0.5 fixed in 3.9.25-1.amzn2023.0.8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9669 | LOW3.01 | python3-libs 3.9.25-1.amzn2023.0.5 fixed in 3.9.25-1.amzn2023.0.8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6653 | LOW3 | libxml2 2.10.4-1.amzn2023.0.18 fixed in 2.10.4-1.amzn2023.0.19 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.4 fixed in 1:3.5.5-1.amzn2023.0.5 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl-libs 1:3.5.5-1.amzn2023.0.4 fixed in 1:3.5.5-1.amzn2023.0.5 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-0864 | LOW2.8 | python3 3.9.25-1.amzn2023.0.5 fixed in 3.9.25-1.amzn2023.0.8 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0864 | LOW2.8 | python3-libs 3.9.25-1.amzn2023.0.5 fixed in 3.9.25-1.amzn2023.0.8 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-8643 | LOW2.8 | python3-pip-wheel 21.3.1-2.amzn2023.0.19 fixed in 21.3.1-2.amzn2023.0.20 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58016 | LOW2.78 | glib2 2.82.2-769.amzn2023 fixed in 2.82.2-770.amzn2023 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-33845 | LOW2.78 | gnutls 3.8.3-8.amzn2023.0.3 fixed in 3.8.3-8.amzn2023.0.4 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | LOW2.78 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.4 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | LOW2.78 | openssl-libs 1:3.5.5-1.amzn2023.0.4 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48863 | LOW2.7 | libsolv 0.7.22-1.amzn2023.0.3 fixed in 0.7.22-1.amzn2023.0.4 | — | Post-Exploit |
| CVE-2026-3276 | LOW2.7 | python3 3.9.25-1.amzn2023.0.5 fixed in 3.9.25-1.amzn2023.0.8 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3446 | LOW2.7 | python3 3.9.25-1.amzn2023.0.5 fixed in 3.9.25-1.amzn2023.0.7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW2.7 | python3-libs 3.9.25-1.amzn2023.0.5 fixed in 3.9.25-1.amzn2023.0.8 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3446 | LOW2.7 | python3-libs 3.9.25-1.amzn2023.0.5 fixed in 3.9.25-1.amzn2023.0.7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-58014 | LOW2.63 | glib2 2.82.2-769.amzn2023 fixed in 2.82.2-770.amzn2023 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58010 | LOW2.51 | glib2 2.82.2-769.amzn2023 fixed in 2.82.2-770.amzn2023 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58012 | LOW2.51 | glib2 2.82.2-769.amzn2023 fixed in 2.82.2-770.amzn2023 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58013 | LOW2.51 | glib2 2.82.2-769.amzn2023 fixed in 2.82.2-770.amzn2023 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42013 | LOW2.51 | gnutls 3.8.3-8.amzn2023.0.3 fixed in 3.8.10-4.amzn2023.0.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48864 | LOW2.39 | libsolv 0.7.22-1.amzn2023.0.3 fixed in 0.7.22-1.amzn2023.0.4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-26740 | LOW2.29 | giflib 5.2.1-9.amzn2023.0.3 fixed in 5.2.1-9.amzn2023.0.4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-58011 | LOW2.29 | glib2 2.82.2-769.amzn2023 fixed in 2.82.2-770.amzn2023 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58015 | LOW2.29 | glib2 2.82.2-769.amzn2023 fixed in 2.82.2-770.amzn2023 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34183 | LOW2.29 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.4 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-34183 | LOW2.29 | openssl-libs 1:3.5.5-1.amzn2023.0.4 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW2.29 | python3 3.9.25-1.amzn2023.0.5 fixed in 3.9.25-1.amzn2023.0.7 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW2.29 | python3-libs 3.9.25-1.amzn2023.0.5 fixed in 3.9.25-1.amzn2023.0.7 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-42011 | LOW2.26 | gnutls 3.8.3-8.amzn2023.0.3 fixed in 3.8.10-4.amzn2023.0.2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW2.26 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.4 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW2.26 | openssl-libs 1:3.5.5-1.amzn2023.0.4 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42012 | LOW2.17 | gnutls 3.8.3-8.amzn2023.0.3 fixed in 3.8.10-4.amzn2023.0.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-54369 | LOW2.17 | libacl 2.3.1-2.amzn2023.0.2 fixed in 2.4.0-1.amzn2023.0.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW1.99 | python3 3.9.25-1.amzn2023.0.5 fixed in 3.9.25-1.amzn2023.0.8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW1.99 | python3-libs 3.9.25-1.amzn2023.0.5 fixed in 3.9.25-1.amzn2023.0.8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5419 | LOW1.89 | gnutls 3.8.3-8.amzn2023.0.3 fixed in 3.8.10-4.amzn2023.0.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW1.87 | python3 3.9.25-1.amzn2023.0.5 fixed in 3.9.25-1.amzn2023.0.6 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW1.87 | python3-libs 3.9.25-1.amzn2023.0.5 fixed in 3.9.25-1.amzn2023.0.6 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW1.68 | python3 3.9.25-1.amzn2023.0.5 fixed in 3.9.25-1.amzn2023.0.7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3 3.9.25-1.amzn2023.0.5 fixed in 3.9.25-1.amzn2023.0.7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW1.68 | python3-libs 3.9.25-1.amzn2023.0.5 fixed in 3.9.25-1.amzn2023.0.7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3-libs 3.9.25-1.amzn2023.0.5 fixed in 3.9.25-1.amzn2023.0.7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gnupg2 2.3.7-1.amzn2023.0.8 fixed in 2.3.7-1.amzn2023.0.9 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gnupg2-smime 2.3.7-1.amzn2023.0.8 fixed in 2.3.7-1.amzn2023.0.9 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56407 | NONE0 | expat 2.6.3-1.amzn2023.0.4 fixed in 2.6.3-1.amzn2023.0.6 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50593 | NONE0 | graphite2 1.3.14-7.amzn2023.0.2 fixed in 1.3.14-7.amzn2023.0.3 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid 2.37.4-1.amzn2023.0.4 fixed in 2.37.4-1.amzn2023.0.5 | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libfdisk 2.37.4-1.amzn2023.0.4 fixed in 2.37.4-1.amzn2023.0.5 | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount 2.37.4-1.amzn2023.0.4 fixed in 2.37.4-1.amzn2023.0.5 | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libsmartcols 2.37.4-1.amzn2023.0.4 fixed in 2.37.4-1.amzn2023.0.5 | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libuuid 2.37.4-1.amzn2023.0.4 fixed in 2.37.4-1.amzn2023.0.5 | — | Not Applicable |
| CVE-2026-11940 | NONE0 | python3 3.9.25-1.amzn2023.0.5 fixed in 3.9.25-1.amzn2023.0.8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3 3.9.25-1.amzn2023.0.5 fixed in 3.9.25-1.amzn2023.0.7 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | python3-libs 3.9.25-1.amzn2023.0.5 fixed in 3.9.25-1.amzn2023.0.8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3-libs 3.9.25-1.amzn2023.0.5 fixed in 3.9.25-1.amzn2023.0.7 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-11822 | NONE0 | sqlite-libs 3.40.0-1.amzn2023.0.7 fixed in 3.40.0-1.amzn2023.0.8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | sqlite-libs 3.40.0-1.amzn2023.0.7 fixed in 3.40.0-1.amzn2023.0.8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | util-linux 2.37.4-1.amzn2023.0.4 fixed in 2.37.4-1.amzn2023.0.5 | — | Not Applicable |
| CVE-2026-53615 | NONE0 | util-linux-core 2.37.4-1.amzn2023.0.4 fixed in 2.37.4-1.amzn2023.0.5 | — | 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.