Last scanned:
This base/runtime image carries significant vulnerabilities that any image built on it would inherit; remediate them in the final image before production. The most severe risks include memory-corruption and code-execution flaws (CVE-2026-6100, CVE-2026-48864) that could lead to arbitrary code execution or information disclosure, as well as numerous denial-of-service conditions in glib and krb5 that may crash services. However, none of the exposed findings reach severity 7.0, and post-exploit findings are negligible (max severity 3.01), so the overall threat remains at a caution level rather than dangerous. Note that CVE-2026-6100 only applies to Python code that reuses decompressor instances after a MemoryError, so the practical exposure depends on the application's usage. 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-6100 | MEDIUM6.88 | python3-libs 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-48864 | MEDIUM6.63 | libsolv 0.7.22-1.amzn2023.0.2 fixed in 0.7.22-1.amzn2023.0.4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | glib2 2.82.2-769.amzn2023 fixed in 2.82.2-770.amzn2023 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | glib2 2.82.2-769.amzn2023 fixed in 2.82.2-770.amzn2023 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | krb5-libs 1.21.3-6.amzn2023.0.1 fixed in 1.21.3-7.amzn2023.0.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | krb5-libs 1.21.3-6.amzn2023.0.1 fixed in 1.21.3-7.amzn2023.0.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33811 | MEDIUM6.38 | libcap 2.73-1.amzn2023.0.6 fixed in 2.73-1.amzn2023.0.7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM6.38 | libcap 2.73-1.amzn2023.0.6 fixed in 2.73-1.amzn2023.0.7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39820 | MEDIUM6.38 | libcap 2.73-1.amzn2023.0.6 fixed in 2.73-1.amzn2023.0.7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42499 | MEDIUM6.38 | libcap 2.73-1.amzn2023.0.6 fixed in 2.73-1.amzn2023.0.7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-41989 | MEDIUM6.38 | libgcrypt 1.10.2-1.amzn2023.0.2 fixed in 1.10.2-1.amzn2023.0.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27135 | MEDIUM6.38 | libnghttp2 1.59.0-3.amzn2023.0.1 fixed in 1.59.0-3.amzn2023.0.2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-48863 | MEDIUM6.38 | libsolv 0.7.22-1.amzn2023.0.2 fixed in 0.7.22-1.amzn2023.0.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | python3-libs 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.38 | python3-libs 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | python3-libs 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | openssl-libs 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54369 | MEDIUM6.03 | 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-1299 | MEDIUM6.03 | python3-libs 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4786 | MEDIUM6.03 | python3-libs 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.9 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.4 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.9 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.9 | openssl-libs 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.4 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.9 | openssl-libs 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.5 | 1.2% Low-Moderate Risk | Directly Exposed |
| 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-56407 | 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.2 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.2 fixed in 0.7.22-1.amzn2023.0.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | python3-libs 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.8 | 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.3 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.3 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM5.35 | openssl-libs 1:3.5.5-1.amzn2023.0.3 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.3 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | python3-libs 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.02 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.02 | openssl-libs 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | openssl-libs 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | openssl-libs 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | python3-libs 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.5 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | openssl-libs 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.5 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | openssl-libs 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | python3-libs 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27142 | MEDIUM4.59 | libcap 2.73-1.amzn2023.0.6 fixed in 2.73-1.amzn2023.0.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39823 | MEDIUM4.59 | libcap 2.73-1.amzn2023.0.6 fixed in 2.73-1.amzn2023.0.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc 2.34-231.amzn2023.0.3 fixed in 2.34-231.amzn2023.0.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-common 2.34-231.amzn2023.0.3 fixed in 2.34-231.amzn2023.0.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-minimal-langpack 2.34-231.amzn2023.0.3 fixed in 2.34-231.amzn2023.0.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.5 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | openssl-libs 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.5 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | openssl-libs 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | python3-libs 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3446 | MEDIUM4.5 | python3-libs 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | krb5-libs 1.21.3-6.amzn2023.0.1 fixed in 1.21.3-8.amzn2023.0.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | MEDIUM4.08 | python3-libs 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.08 | python3-libs 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | LOW3.82 | python3-libs 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0865 | LOW3.82 | python3-libs 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | openssl-libs 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | LOW3.01 | python3 3.9.25-1.amzn2023.0.3 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.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6357 | LOW2.96 | python3-pip-wheel 21.3.1-2.amzn2023.0.16 fixed in 21.3.1-2.amzn2023.0.19 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.5 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl-libs 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.5 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-0864 | LOW2.8 | python3 3.9.25-1.amzn2023.0.3 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.16 fixed in 21.3.1-2.amzn2023.0.20 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW2.8 | python3-libs 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | python3-libs 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | python3-libs 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | python3-libs 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.7 | 0.2% Theoretical Threat | Directly Exposed |
| 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-45445 | LOW2.78 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | LOW2.78 | openssl-libs 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-28388 | LOW2.7 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.4 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28389 | LOW2.7 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.4 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28390 | LOW2.7 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.4 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34183 | LOW2.7 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.5 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28388 | LOW2.7 | openssl-libs 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.4 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28389 | LOW2.7 | openssl-libs 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.4 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28390 | LOW2.7 | openssl-libs 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.4 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34183 | LOW2.7 | openssl-libs 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.5 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3276 | LOW2.7 | python3 3.9.25-1.amzn2023.0.3 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.3 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-28387 | LOW2.48 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.4 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28387 | LOW2.48 | openssl-libs 1:3.5.5-1.amzn2023.0.3 fixed in 1:3.5.5-1.amzn2023.0.4 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | LOW2.48 | python3 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.5 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | LOW2.45 | python3 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.45 | python3 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3644 | LOW2.29 | python3 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW2.29 | python3 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW2.29 | python3 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.7 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-11468 | LOW2.29 | python3 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0865 | LOW2.29 | python3 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-1299 | LOW2.17 | python3 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-4786 | LOW2.17 | python3 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.5 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW1.99 | python3 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-1703 | LOW1.99 | python3-pip-wheel 21.3.1-2.amzn2023.0.16 fixed in 21.3.1-2.amzn2023.0.17 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3805 | LOW1.93 | curl-minimal 8.17.0-1.amzn2023.0.2 fixed in 8.17.0-1.amzn2023.0.3 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3805 | LOW1.93 | libcurl-minimal 8.17.0-1.amzn2023.0.2 fixed in 8.17.0-1.amzn2023.0.3 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW1.87 | python3 3.9.25-1.amzn2023.0.3 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.3 fixed in 3.9.25-1.amzn2023.0.7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4519 | LOW1.68 | python3 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.68 | python3 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3 3.9.25-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gnupg2-minimal 2.3.7-1.amzn2023.0.7 fixed in 2.3.7-1.amzn2023.0.9 | 0.1% Theoretical Threat | Post-Exploit |
| 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 | 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.3 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.3 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.3 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.3 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 |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
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.