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 impactful inherited risks are CVE-2026-66046 in expat and CVE-2026-63075 in openssl-libs. An attacker could cause denial of service through crafted XML or sustained QUIC traffic against applications built on this base image, while DTLS handshake flaws could crash a process or expose heap memory. Post-exploit findings are present but low severity, with max 3.82 and none >=6.0. Applications that do not parse untrusted XML or enable QUIC/DTLS fully avoid those specific risks, but other inherited packages should still be patched before production. 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-66046 | MEDIUM6.38 | expat 2.6.3-1.amzn2023.0.6 fixed in 2.8.3-1.amzn2023.0.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM6.38 | openssl-libs 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-84782 | MEDIUM6.29 | openssl-fips-provider-latest 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-84782 | MEDIUM6.29 | openssl-libs 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86143 | MEDIUM6.21 | 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-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-63073 | MEDIUM5.9 | openssl-fips-provider-latest 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63073 | MEDIUM5.9 | openssl-libs 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56404 | MEDIUM5.87 | expat 2.6.3-1.amzn2023.0.6 fixed in 2.8.3-1.amzn2023.0.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56405 | MEDIUM5.87 | expat 2.6.3-1.amzn2023.0.6 fixed in 2.8.3-1.amzn2023.0.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56410 | MEDIUM5.87 | expat 2.6.3-1.amzn2023.0.6 fixed in 2.8.3-1.amzn2023.0.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56411 | MEDIUM5.87 | expat 2.6.3-1.amzn2023.0.6 fixed in 2.8.3-1.amzn2023.0.1 | 0.1% 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-50219 | MEDIUM5.02 | expat 2.6.3-1.amzn2023.0.6 fixed in 2.8.3-1.amzn2023.0.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56412 | MEDIUM5.02 | expat 2.6.3-1.amzn2023.0.6 fixed in 2.8.3-1.amzn2023.0.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54872 | MEDIUM5.02 | openssl-fips-provider-latest 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-72897 | MEDIUM5.02 | openssl-fips-provider-latest 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75805 | MEDIUM5.02 | openssl-fips-provider-latest 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54872 | MEDIUM5.02 | openssl-libs 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-72897 | MEDIUM5.02 | openssl-libs 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75805 | MEDIUM5.02 | openssl-libs 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42772 | MEDIUM4.5 | openssl-fips-provider-latest 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54873 | MEDIUM4.5 | openssl-fips-provider-latest 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75804 | MEDIUM4.5 | openssl-fips-provider-latest 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM4.5 | openssl-fips-provider-latest 1:3.5.7-2.amzn2023.0.2 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.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42772 | MEDIUM4.5 | openssl-libs 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54873 | MEDIUM4.5 | openssl-libs 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75804 | MEDIUM4.5 | openssl-libs 1:3.5.7-2.amzn2023.0.2 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.7-2.amzn2023.0.2 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.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8927 | LOW3.82 | curl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | curl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9079 | LOW3.82 | curl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | curl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9079 | LOW3.82 | libcurl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | libcurl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-97689 | LOW3.82 | 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-56131 | LOW3.82 | expat 2.6.3-1.amzn2023.0.6 fixed in 2.8.3-1.amzn2023.0.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | LOW3.77 | curl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW3.72 | curl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW3.72 | libcurl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.5% Theoretical Threat | Post-Exploit |
| 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-8924 | LOW3.31 | curl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | curl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | libcurl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-35189 | LOW3.15 | openssl-fips-provider-latest 1:3.5.7-2.amzn2023.0.2 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.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.15 | openssl-fips-provider-latest 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.15 | openssl-libs 1:3.5.7-2.amzn2023.0.2 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.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.15 | openssl-libs 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-8925 | LOW2.92 | curl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-8925 | LOW2.92 | libcurl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-14457 | LOW2.7 | openssl-fips-provider-latest 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.1 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-18798 | LOW2.7 | openssl-fips-provider-latest 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.1 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63076 | LOW2.7 | openssl-fips-provider-latest 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.1 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-14457 | LOW2.7 | openssl-libs 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.1 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-18798 | LOW2.7 | openssl-libs 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.1 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63076 | LOW2.7 | openssl-libs 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.1 | 1.6% Low-Moderate Risk | Post-Exploit |
| 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-8286 | LOW2.48 | curl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | LOW2.48 | curl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | LOW2.48 | libcurl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | LOW2.48 | libcurl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | curl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | libcurl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | curl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | libcurl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-76957 | LOW2.39 | expat 2.6.3-1.amzn2023.0.6 fixed in 2.8.3-1.amzn2023.0.1 | 0.1% 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-12064 | LOW2.29 | curl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-11586 | LOW2.29 | curl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW2.29 | libcurl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-11586 | LOW2.29 | libcurl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-54874 | LOW2.29 | openssl-fips-provider-latest 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63072 | LOW2.29 | openssl-fips-provider-latest 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.1 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-63074 | LOW2.29 | openssl-fips-provider-latest 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63075 | LOW2.29 | openssl-fips-provider-latest 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-54874 | LOW2.29 | openssl-libs 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63072 | LOW2.29 | openssl-libs 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.1 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-63074 | LOW2.29 | openssl-libs 1:3.5.7-2.amzn2023.0.2 fixed in 1:3.5.8-1.amzn2023.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.89 | curl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.89 | libcurl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.2 | 0.4% 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 |
| CVE-2026-56408 | NONE0 | expat 2.6.3-1.amzn2023.0.6 fixed in 2.8.3-1.amzn2023.0.1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56409 | NONE0 | expat 2.6.3-1.amzn2023.0.6 fixed in 2.8.3-1.amzn2023.0.1 | 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.