Last scanned:
This image is acceptable for production, but remediating the identified vulnerabilities is recommended to reduce the attack surface. The scan found 26 exposed findings and 119 post-exploit findings, and the only exposed finding at or above severity 6.0 is CVE-2026-97689, a memory-exhaustion flaw in the bundled urllib3 that a malicious or compromised endpoint could trigger to crash the CLI. The remaining findings are lower severity or only matter after the container is already compromised, so they do not change the verdict. Updating the python3-pip-wheel package to a fixed version is the practical step to close the flaw.
Hardening plan for this image · 5 steps
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-97689 | MEDIUM6 | python3-pip-wheel 21.3.1-2.amzn2023.0.21 fixed in 21.3.1-2.amzn2023.0.22 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-19553 | MEDIUM5.92 | python3 3.9.25-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.11 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-19553 | MEDIUM5.92 | python3-libs 3.9.25-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.11 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-75806 | MEDIUM5.3 | openssl-fips-provider-latest 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-84784 | MEDIUM5.3 | openssl-fips-provider-latest 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM5.3 | openssl-libs 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-84784 | MEDIUM5.3 | openssl-libs 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7017 | MEDIUM5 | perl-HTTP-Tiny 0.092-2.amzn2023.0.2 fixed in 0.092-2.amzn2023.0.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-103111 | MEDIUM4.56 | pcre2 10.40-1.amzn2023.0.4 fixed in 10.40-1.amzn2023.0.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-103111 | MEDIUM4.56 | pcre2-syntax 10.40-1.amzn2023.0.4 fixed in 10.40-1.amzn2023.0.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.7 | 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.7 | openssl-fips-provider-latest 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.7 | 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.7 | openssl-libs 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-54872 | LOW3.54 | 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-72897 | LOW3.54 | 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-75805 | LOW3.54 | 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-54872 | LOW3.54 | 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-72897 | LOW3.54 | 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-75805 | LOW3.54 | 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-42772 | LOW3.18 | 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 | Directly Exposed |
| CVE-2026-54873 | LOW3.18 | openssl-fips-provider-latest 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-75804 | LOW3.18 | 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 | Directly Exposed |
| CVE-2026-42772 | LOW3.18 | openssl-libs 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54873 | LOW3.18 | openssl-libs 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-75804 | LOW3.18 | openssl-libs 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86145 | LOW2.95 | pcre2 10.40-1.amzn2023.0.4 fixed in 10.40-1.amzn2023.0.5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-86145 | LOW2.95 | pcre2-syntax 10.40-1.amzn2023.0.4 fixed in 10.40-1.amzn2023.0.5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-92392 | LOW2.92 | curl-minimal 8.21.0-5.amzn2023.0.2 fixed in 8.21.0-5.amzn2023.0.3 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-92392 | LOW2.92 | libcurl-minimal 8.21.0-5.amzn2023.0.2 fixed in 8.21.0-5.amzn2023.0.3 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-78659 | LOW2.7 | libcap 2.73-1.amzn2023.0.7 fixed in 2.73-1.amzn2023.0.8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-78667 | LOW2.7 | libcap 2.73-1.amzn2023.0.7 fixed in 2.73-1.amzn2023.0.8 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-94440 | LOW2.7 | libcap 2.73-1.amzn2023.0.7 fixed in 2.73-1.amzn2023.0.8 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-84782 | LOW2.66 | openssl-fips-provider-latest 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-84782 | LOW2.66 | openssl-libs 1:3.5.8-1.amzn2023.0.1 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-113470 | LOW2.48 | ca-certificates 2025.2.76-1.0.amzn2023.0.3 fixed in 2025.2.76-1.0.amzn2023.0.4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.48 | perl-AutoLoader 5.74-477.amzn2023.0.9 fixed in 5.74-477.amzn2023.0.10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW2.48 | perl-AutoLoader 5.74-477.amzn2023.0.9 fixed in 5.74-477.amzn2023.0.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.48 | perl-B 1.80-477.amzn2023.0.9 fixed in 1.80-477.amzn2023.0.10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW2.48 | perl-B 1.80-477.amzn2023.0.9 fixed in 1.80-477.amzn2023.0.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.48 | perl-Class-Struct 0.66-477.amzn2023.0.9 fixed in 0.66-477.amzn2023.0.10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW2.48 | perl-Class-Struct 0.66-477.amzn2023.0.9 fixed in 0.66-477.amzn2023.0.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.48 | perl-DynaLoader 1.47-477.amzn2023.0.9 fixed in 1.47-477.amzn2023.0.10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW2.48 | perl-DynaLoader 1.47-477.amzn2023.0.9 fixed in 1.47-477.amzn2023.0.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.48 | perl-Errno 1.30-477.amzn2023.0.9 fixed in 1.30-477.amzn2023.0.10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW2.48 | perl-Errno 1.30-477.amzn2023.0.9 fixed in 1.30-477.amzn2023.0.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.48 | perl-Fcntl 1.13-477.amzn2023.0.9 fixed in 1.13-477.amzn2023.0.10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW2.48 | perl-Fcntl 1.13-477.amzn2023.0.9 fixed in 1.13-477.amzn2023.0.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.48 | perl-File-Basename 2.85-477.amzn2023.0.9 fixed in 2.85-477.amzn2023.0.10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW2.48 | perl-File-Basename 2.85-477.amzn2023.0.9 fixed in 2.85-477.amzn2023.0.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.48 | perl-File-Copy 2.34-477.amzn2023.0.9 fixed in 2.34-477.amzn2023.0.10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW2.48 | perl-File-Copy 2.34-477.amzn2023.0.9 fixed in 2.34-477.amzn2023.0.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.48 | perl-File-stat 1.09-477.amzn2023.0.9 fixed in 1.09-477.amzn2023.0.10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW2.48 | perl-File-stat 1.09-477.amzn2023.0.9 fixed in 1.09-477.amzn2023.0.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.48 | perl-FileHandle 2.03-477.amzn2023.0.9 fixed in 2.03-477.amzn2023.0.10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW2.48 | perl-FileHandle 2.03-477.amzn2023.0.9 fixed in 2.03-477.amzn2023.0.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.48 | perl-Getopt-Std 1.12-477.amzn2023.0.9 fixed in 1.12-477.amzn2023.0.10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW2.48 | perl-Getopt-Std 1.12-477.amzn2023.0.9 fixed in 1.12-477.amzn2023.0.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.48 | perl-IO 1.43-477.amzn2023.0.9 fixed in 1.43-477.amzn2023.0.10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW2.48 | perl-IO 1.43-477.amzn2023.0.9 fixed in 1.43-477.amzn2023.0.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.48 | perl-IPC-Open3 1.21-477.amzn2023.0.9 fixed in 1.21-477.amzn2023.0.10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW2.48 | perl-IPC-Open3 1.21-477.amzn2023.0.9 fixed in 1.21-477.amzn2023.0.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.48 | perl-NDBM_File 1.15-477.amzn2023.0.9 fixed in 1.15-477.amzn2023.0.10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW2.48 | perl-NDBM_File 1.15-477.amzn2023.0.9 fixed in 1.15-477.amzn2023.0.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.48 | perl-POSIX 1.94-477.amzn2023.0.9 fixed in 1.94-477.amzn2023.0.10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW2.48 | perl-POSIX 1.94-477.amzn2023.0.9 fixed in 1.94-477.amzn2023.0.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.48 | perl-SelectSaver 1.02-477.amzn2023.0.9 fixed in 1.02-477.amzn2023.0.10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW2.48 | perl-SelectSaver 1.02-477.amzn2023.0.9 fixed in 1.02-477.amzn2023.0.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-57433 | LOW2.48 | perl-Storable 1:3.37-522.amzn2023.0.2 fixed in 1:3.37-522.amzn2023.0.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.48 | perl-Symbol 1.08-477.amzn2023.0.9 fixed in 1.08-477.amzn2023.0.10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW2.48 | perl-Symbol 1.08-477.amzn2023.0.9 fixed in 1.08-477.amzn2023.0.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.48 | perl-base 2.27-477.amzn2023.0.9 fixed in 2.27-477.amzn2023.0.10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW2.48 | perl-base 2.27-477.amzn2023.0.9 fixed in 2.27-477.amzn2023.0.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.48 | perl-if 0.60.800-477.amzn2023.0.9 fixed in 0.60.800-477.amzn2023.0.10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW2.48 | perl-if 0.60.800-477.amzn2023.0.9 fixed in 0.60.800-477.amzn2023.0.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.48 | perl-interpreter 4:5.32.1-477.amzn2023.0.9 fixed in 4:5.32.1-477.amzn2023.0.10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW2.48 | perl-interpreter 4:5.32.1-477.amzn2023.0.9 fixed in 4:5.32.1-477.amzn2023.0.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.48 | perl-libs 4:5.32.1-477.amzn2023.0.9 fixed in 4:5.32.1-477.amzn2023.0.10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW2.48 | perl-libs 4:5.32.1-477.amzn2023.0.9 fixed in 4:5.32.1-477.amzn2023.0.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.48 | perl-mro 1.23-477.amzn2023.0.9 fixed in 1.23-477.amzn2023.0.10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW2.48 | perl-mro 1.23-477.amzn2023.0.9 fixed in 1.23-477.amzn2023.0.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.48 | perl-overload 1.31-477.amzn2023.0.9 fixed in 1.31-477.amzn2023.0.10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW2.48 | perl-overload 1.31-477.amzn2023.0.9 fixed in 1.31-477.amzn2023.0.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.48 | perl-overloading 0.02-477.amzn2023.0.9 fixed in 0.02-477.amzn2023.0.10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW2.48 | perl-overloading 0.02-477.amzn2023.0.9 fixed in 0.02-477.amzn2023.0.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.48 | perl-subs 1.03-477.amzn2023.0.9 fixed in 1.03-477.amzn2023.0.10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW2.48 | perl-subs 1.03-477.amzn2023.0.9 fixed in 1.03-477.amzn2023.0.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.48 | perl-vars 1.05-477.amzn2023.0.9 fixed in 1.05-477.amzn2023.0.10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW2.48 | perl-vars 1.05-477.amzn2023.0.9 fixed in 1.05-477.amzn2023.0.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-89160 | LOW2.34 | pcre2 10.40-1.amzn2023.0.4 fixed in 10.40-1.amzn2023.0.5 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-89160 | LOW2.34 | pcre2-syntax 10.40-1.amzn2023.0.4 fixed in 10.40-1.amzn2023.0.5 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW2.34 | perl-AutoLoader 5.74-477.amzn2023.0.9 fixed in 5.74-477.amzn2023.0.11 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW2.34 | perl-B 1.80-477.amzn2023.0.9 fixed in 1.80-477.amzn2023.0.11 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW2.34 | perl-Class-Struct 0.66-477.amzn2023.0.9 fixed in 0.66-477.amzn2023.0.11 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW2.34 | perl-DynaLoader 1.47-477.amzn2023.0.9 fixed in 1.47-477.amzn2023.0.11 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW2.34 | perl-Errno 1.30-477.amzn2023.0.9 fixed in 1.30-477.amzn2023.0.11 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW2.34 | perl-Fcntl 1.13-477.amzn2023.0.9 fixed in 1.13-477.amzn2023.0.11 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW2.34 | perl-File-Basename 2.85-477.amzn2023.0.9 fixed in 2.85-477.amzn2023.0.11 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW2.34 | perl-File-Copy 2.34-477.amzn2023.0.9 fixed in 2.34-477.amzn2023.0.11 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW2.34 | perl-File-stat 1.09-477.amzn2023.0.9 fixed in 1.09-477.amzn2023.0.11 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW2.34 | perl-FileHandle 2.03-477.amzn2023.0.9 fixed in 2.03-477.amzn2023.0.11 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW2.34 | perl-Getopt-Std 1.12-477.amzn2023.0.9 fixed in 1.12-477.amzn2023.0.11 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW2.34 | perl-IO 1.43-477.amzn2023.0.9 fixed in 1.43-477.amzn2023.0.11 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW2.34 | perl-IPC-Open3 1.21-477.amzn2023.0.9 fixed in 1.21-477.amzn2023.0.11 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW2.34 | perl-NDBM_File 1.15-477.amzn2023.0.9 fixed in 1.15-477.amzn2023.0.11 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW2.34 | perl-POSIX 1.94-477.amzn2023.0.9 fixed in 1.94-477.amzn2023.0.11 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW2.34 | perl-SelectSaver 1.02-477.amzn2023.0.9 fixed in 1.02-477.amzn2023.0.11 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW2.34 | perl-Symbol 1.08-477.amzn2023.0.9 fixed in 1.08-477.amzn2023.0.11 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW2.34 | perl-base 2.27-477.amzn2023.0.9 fixed in 2.27-477.amzn2023.0.11 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW2.34 | perl-if 0.60.800-477.amzn2023.0.9 fixed in 0.60.800-477.amzn2023.0.11 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW2.34 | perl-interpreter 4:5.32.1-477.amzn2023.0.9 fixed in 4:5.32.1-477.amzn2023.0.11 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW2.34 | perl-libs 4:5.32.1-477.amzn2023.0.9 fixed in 4:5.32.1-477.amzn2023.0.11 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW2.34 | perl-mro 1.23-477.amzn2023.0.9 fixed in 1.23-477.amzn2023.0.11 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW2.34 | perl-overload 1.31-477.amzn2023.0.9 fixed in 1.31-477.amzn2023.0.11 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW2.34 | perl-overloading 0.02-477.amzn2023.0.9 fixed in 0.02-477.amzn2023.0.11 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW2.34 | perl-subs 1.03-477.amzn2023.0.9 fixed in 1.03-477.amzn2023.0.11 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW2.34 | perl-vars 1.05-477.amzn2023.0.9 fixed in 1.05-477.amzn2023.0.11 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-89156 | LOW2.12 | pcre2 10.40-1.amzn2023.0.4 fixed in 10.40-1.amzn2023.0.5 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-89156 | LOW2.12 | pcre2-syntax 10.40-1.amzn2023.0.4 fixed in 10.40-1.amzn2023.0.5 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl-AutoLoader 5.74-477.amzn2023.0.9 fixed in 5.74-477.amzn2023.0.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl-B 1.80-477.amzn2023.0.9 fixed in 1.80-477.amzn2023.0.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl-Class-Struct 0.66-477.amzn2023.0.9 fixed in 0.66-477.amzn2023.0.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl-DynaLoader 1.47-477.amzn2023.0.9 fixed in 1.47-477.amzn2023.0.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl-Errno 1.30-477.amzn2023.0.9 fixed in 1.30-477.amzn2023.0.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl-Fcntl 1.13-477.amzn2023.0.9 fixed in 1.13-477.amzn2023.0.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl-File-Basename 2.85-477.amzn2023.0.9 fixed in 2.85-477.amzn2023.0.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl-File-Copy 2.34-477.amzn2023.0.9 fixed in 2.34-477.amzn2023.0.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl-File-stat 1.09-477.amzn2023.0.9 fixed in 1.09-477.amzn2023.0.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl-FileHandle 2.03-477.amzn2023.0.9 fixed in 2.03-477.amzn2023.0.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl-Getopt-Std 1.12-477.amzn2023.0.9 fixed in 1.12-477.amzn2023.0.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl-IO 1.43-477.amzn2023.0.9 fixed in 1.43-477.amzn2023.0.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl-IPC-Open3 1.21-477.amzn2023.0.9 fixed in 1.21-477.amzn2023.0.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl-NDBM_File 1.15-477.amzn2023.0.9 fixed in 1.15-477.amzn2023.0.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl-POSIX 1.94-477.amzn2023.0.9 fixed in 1.94-477.amzn2023.0.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl-SelectSaver 1.02-477.amzn2023.0.9 fixed in 1.02-477.amzn2023.0.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl-Symbol 1.08-477.amzn2023.0.9 fixed in 1.08-477.amzn2023.0.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl-base 2.27-477.amzn2023.0.9 fixed in 2.27-477.amzn2023.0.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl-if 0.60.800-477.amzn2023.0.9 fixed in 0.60.800-477.amzn2023.0.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl-interpreter 4:5.32.1-477.amzn2023.0.9 fixed in 4:5.32.1-477.amzn2023.0.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl-libs 4:5.32.1-477.amzn2023.0.9 fixed in 4:5.32.1-477.amzn2023.0.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl-mro 1.23-477.amzn2023.0.9 fixed in 1.23-477.amzn2023.0.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl-overload 1.31-477.amzn2023.0.9 fixed in 1.31-477.amzn2023.0.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl-overloading 0.02-477.amzn2023.0.9 fixed in 0.02-477.amzn2023.0.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl-subs 1.03-477.amzn2023.0.9 fixed in 1.03-477.amzn2023.0.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl-vars 1.05-477.amzn2023.0.9 fixed in 1.05-477.amzn2023.0.11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | NONE0 | perl-locale 1.09-477.amzn2023.0.9 fixed in 1.09-477.amzn2023.0.10 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-57432 | NONE0 | perl-locale 1.09-477.amzn2023.0.9 fixed in 1.09-477.amzn2023.0.10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-19487 | NONE0 | perl-locale 1.09-477.amzn2023.0.9 fixed in 1.09-477.amzn2023.0.11 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-15534 | NONE0 | perl-locale 1.09-477.amzn2023.0.9 fixed in 1.09-477.amzn2023.0.11 | 0.2% Theoretical Threat | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.