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. An attacker who could get crafted Brotli-compressed data to an application in an image built on this base could execute code or leak data, and CVE-2026-111497 is already being exploited in the wild. Real exposure depends on whether such an application exists, since this needs a non-default setup, and CVE-2026-76957 likewise only matters if an app parses untrusted XML with custom encodings. The remaining findings are mostly denial-of-service or low-impact and do not drive this verdict. 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.
Hardening plan for this image · 5 steps. The first closes an actively exploited CVE.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-111497 | HIGH8 | libbrotli 1.0.9-4.amzn2023.0.2 fixed in 1.1.0-1.amzn2023.0.2 | 55.5% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2026-76957 | MEDIUM6.24 | expat 2.6.3-1.amzn2023.0.6 fixed in 2.8.3-1.amzn2023.0.1 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-15308 | MEDIUM6 | python3 3.9.25-1.amzn2023.0.8 fixed in 3.9.25-1.amzn2023.0.9 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-15308 | MEDIUM6 | python3-libs 3.9.25-1.amzn2023.0.8 fixed in 3.9.25-1.amzn2023.0.9 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54872 | MEDIUM5.9 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63073 | MEDIUM5.9 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-72897 | MEDIUM5.9 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75805 | MEDIUM5.9 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54872 | MEDIUM5.9 | openssl-libs 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63073 | MEDIUM5.9 | openssl-libs 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-72897 | MEDIUM5.9 | openssl-libs 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75805 | MEDIUM5.9 | openssl-libs 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56404 | MEDIUM5.52 | expat 2.6.3-1.amzn2023.0.6 fixed in 2.8.3-1.amzn2023.0.1 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56405 | MEDIUM5.52 | expat 2.6.3-1.amzn2023.0.6 fixed in 2.8.3-1.amzn2023.0.1 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56408 | MEDIUM5.52 | expat 2.6.3-1.amzn2023.0.6 fixed in 2.8.3-1.amzn2023.0.1 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56410 | MEDIUM5.52 | expat 2.6.3-1.amzn2023.0.6 fixed in 2.8.3-1.amzn2023.0.1 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56411 | MEDIUM5.52 | expat 2.6.3-1.amzn2023.0.6 fixed in 2.8.3-1.amzn2023.0.1 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-40468 | MEDIUM5.34 | gawk 5.1.0-3.amzn2023.0.3 fixed in 5.1.0-3.amzn2023.0.4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42772 | MEDIUM5.3 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54873 | MEDIUM5.3 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-75804 | MEDIUM5.3 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM5.3 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.5 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.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42772 | MEDIUM5.3 | openssl-libs 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54873 | MEDIUM5.3 | openssl-libs 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-75804 | MEDIUM5.3 | openssl-libs 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM5.3 | openssl-libs 1:3.5.5-1.amzn2023.0.5 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.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4360 | MEDIUM5.3 | python3-libs 3.9.25-1.amzn2023.0.8 fixed in 3.9.25-1.amzn2023.0.9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56409 | MEDIUM5.2 | expat 2.6.3-1.amzn2023.0.6 fixed in 2.8.3-1.amzn2023.0.1 | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-88807 | MEDIUM4.98 | libXrender 0.9.11-6.amzn2023.0.1 fixed in 0.9.11-6.amzn2023.0.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86145 | MEDIUM4.92 | pcre2 10.40-1.amzn2023.0.3 fixed in 10.40-1.amzn2023.0.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86145 | MEDIUM4.92 | pcre2-syntax 10.40-1.amzn2023.0.3 fixed in 10.40-1.amzn2023.0.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | MEDIUM4.72 | expat 2.6.3-1.amzn2023.0.6 fixed in 2.8.3-1.amzn2023.0.1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56412 | MEDIUM4.72 | expat 2.6.3-1.amzn2023.0.6 fixed in 2.8.3-1.amzn2023.0.1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-89161 | MEDIUM4.68 | pcre2 10.40-1.amzn2023.0.3 fixed in 10.40-1.amzn2023.0.4 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-89161 | MEDIUM4.68 | pcre2-syntax 10.40-1.amzn2023.0.3 fixed in 10.40-1.amzn2023.0.4 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-103111 | MEDIUM4.56 | pcre2 10.40-1.amzn2023.0.3 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.3 fixed in 10.40-1.amzn2023.0.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66046 | MEDIUM4.5 | 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-40467 | MEDIUM4.5 | gawk 5.1.0-3.amzn2023.0.3 fixed in 5.1.0-3.amzn2023.0.4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40553 | MEDIUM4.5 | gawk 5.1.0-3.amzn2023.0.3 fixed in 5.1.0-3.amzn2023.0.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-88806 | MEDIUM4.5 | libX11 1.8.10-2.amzn2023.0.1 fixed in 1.8.10-2.amzn2023.0.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88806 | MEDIUM4.5 | libX11-common 1.8.10-2.amzn2023.0.1 fixed in 1.8.10-2.amzn2023.0.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78659 | MEDIUM4.5 | libcap 2.73-1.amzn2023.0.7 fixed in 2.73-1.amzn2023.0.8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-78667 | MEDIUM4.5 | libcap 2.73-1.amzn2023.0.7 fixed in 2.73-1.amzn2023.0.8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-94440 | MEDIUM4.5 | libcap 2.73-1.amzn2023.0.7 fixed in 2.73-1.amzn2023.0.8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-14456 | MEDIUM4.5 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.7-2.amzn2023.0.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-14457 | MEDIUM4.5 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-18798 | MEDIUM4.5 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.1 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54874 | MEDIUM4.5 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63072 | MEDIUM4.5 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM4.5 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM4.5 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63076 | MEDIUM4.5 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.1 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14456 | MEDIUM4.5 | openssl-libs 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.7-2.amzn2023.0.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-14457 | MEDIUM4.5 | openssl-libs 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-18798 | MEDIUM4.5 | openssl-libs 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.1 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54874 | MEDIUM4.5 | openssl-libs 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63072 | MEDIUM4.5 | openssl-libs 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM4.5 | openssl-libs 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM4.5 | openssl-libs 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63076 | MEDIUM4.5 | openssl-libs 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.1 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-84782 | MEDIUM4.44 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-84782 | MEDIUM4.44 | openssl-libs 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-19553 | MEDIUM4.44 | python3-libs 3.9.25-1.amzn2023.0.8 fixed in 3.9.25-1.amzn2023.0.11 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-16118 | MEDIUM4.26 | glib2 2.82.2-770.amzn2023 fixed in 2.82.2-771.amzn2023 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78367 | MEDIUM4.2 | python3-rpm 4.16.1.3-29.amzn2023.0.6 fixed in 4.16.1.3-29.amzn2023.0.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-84233 | MEDIUM4.2 | python3-rpm 4.16.1.3-29.amzn2023.0.6 fixed in 4.16.1.3-29.amzn2023.0.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78367 | MEDIUM4.2 | rpm-build-libs 4.16.1.3-29.amzn2023.0.6 fixed in 4.16.1.3-29.amzn2023.0.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-84233 | MEDIUM4.2 | rpm-build-libs 4.16.1.3-29.amzn2023.0.6 fixed in 4.16.1.3-29.amzn2023.0.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78367 | MEDIUM4.2 | rpm-libs 4.16.1.3-29.amzn2023.0.6 fixed in 4.16.1.3-29.amzn2023.0.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-84233 | MEDIUM4.2 | rpm-libs 4.16.1.3-29.amzn2023.0.6 fixed in 4.16.1.3-29.amzn2023.0.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78367 | MEDIUM4.2 | rpm-sign-libs 4.16.1.3-29.amzn2023.0.6 fixed in 4.16.1.3-29.amzn2023.0.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-84233 | MEDIUM4.2 | rpm-sign-libs 4.16.1.3-29.amzn2023.0.6 fixed in 4.16.1.3-29.amzn2023.0.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-8925 | MEDIUM4.14 | curl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-8927 | MEDIUM4.14 | curl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-8932 | MEDIUM4.14 | curl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9079 | MEDIUM4.14 | curl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-9080 | MEDIUM4.14 | curl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9545 | MEDIUM4.14 | curl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | MEDIUM4.14 | curl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-113470 | MEDIUM4.14 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-8925 | MEDIUM4.14 | libcurl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-8927 | MEDIUM4.14 | libcurl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-8932 | MEDIUM4.14 | libcurl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9079 | MEDIUM4.14 | libcurl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-9080 | MEDIUM4.14 | libcurl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9545 | MEDIUM4.14 | libcurl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | MEDIUM4.14 | libcurl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11979 | MEDIUM4.14 | libxml2 2.10.4-1.amzn2023.0.19 fixed in 2.10.4-1.amzn2023.0.20 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-74860 | MEDIUM4.14 | libxml2 2.10.4-1.amzn2023.0.19 fixed in 2.10.4-1.amzn2023.0.21 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-86138 | MEDIUM4.14 | libxml2 2.10.4-1.amzn2023.0.19 fixed in 2.10.4-1.amzn2023.0.21 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86140 | MEDIUM4.14 | libxml2 2.10.4-1.amzn2023.0.19 fixed in 2.10.4-1.amzn2023.0.21 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86142 | MEDIUM4.14 | libxml2 2.10.4-1.amzn2023.0.19 fixed in 2.10.4-1.amzn2023.0.21 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86143 | MEDIUM4.14 | libxml2 2.10.4-1.amzn2023.0.19 fixed in 2.10.4-1.amzn2023.0.21 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86144 | MEDIUM4.14 | libxml2 2.10.4-1.amzn2023.0.19 fixed in 2.10.4-1.amzn2023.0.21 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56109 | MEDIUM4.08 | alsa-lib 1.2.7.2-1.amzn2023.0.3 fixed in 1.2.7.2-1.amzn2023.0.4 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-61308 | MEDIUM4.08 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.20+10-1.amzn2023.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-91398 | MEDIUM4.08 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91403 | MEDIUM4.08 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11856 | LOW3.9 | curl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-8924 | LOW3.9 | curl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-87294 | LOW3.9 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-91382 | LOW3.9 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-91395 | LOW3.9 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-91396 | LOW3.9 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-91411 | LOW3.9 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11856 | LOW3.9 | libcurl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-8924 | LOW3.9 | libcurl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-89160 | LOW3.9 | pcre2 10.40-1.amzn2023.0.3 fixed in 10.40-1.amzn2023.0.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-89160 | LOW3.9 | pcre2-syntax 10.40-1.amzn2023.0.3 fixed in 10.40-1.amzn2023.0.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-7774 | LOW3.9 | python3-libs 3.9.25-1.amzn2023.0.8 fixed in 3.9.25-1.amzn2023.0.9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.7 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.5 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.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.7 | openssl-fips-provider-latest 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.7 | openssl-libs 1:3.5.5-1.amzn2023.0.5 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.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.7 | openssl-libs 1:3.5.5-1.amzn2023.0.5 fixed in 1:3.5.8-1.amzn2023.0.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86137 | LOW3.66 | libxml2 2.10.4-1.amzn2023.0.19 fixed in 2.10.4-1.amzn2023.0.21 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56131 | LOW3.6 | expat 2.6.3-1.amzn2023.0.6 fixed in 2.8.3-1.amzn2023.0.1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-83374 | LOW3.54 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-83387 | LOW3.54 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-91394 | LOW3.54 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-91462 | LOW3.54 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-89156 | LOW3.54 | pcre2 10.40-1.amzn2023.0.3 fixed in 10.40-1.amzn2023.0.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-89156 | LOW3.54 | pcre2-syntax 10.40-1.amzn2023.0.3 fixed in 10.40-1.amzn2023.0.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-44605 | LOW3.3 | python3-rpm 4.16.1.3-29.amzn2023.0.6 fixed in 4.16.1.3-29.amzn2023.0.7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44605 | LOW3.3 | rpm 4.16.1.3-29.amzn2023.0.6 fixed in 4.16.1.3-29.amzn2023.0.7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44605 | LOW3.3 | rpm-build-libs 4.16.1.3-29.amzn2023.0.6 fixed in 4.16.1.3-29.amzn2023.0.7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44605 | LOW3.3 | rpm-libs 4.16.1.3-29.amzn2023.0.6 fixed in 4.16.1.3-29.amzn2023.0.7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44605 | LOW3.3 | rpm-sign-libs 4.16.1.3-29.amzn2023.0.6 fixed in 4.16.1.3-29.amzn2023.0.7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-87293 | LOW3.24 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-70907 | LOW3.18 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.20+10-1.amzn2023.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-83380 | LOW3.18 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-83400 | LOW3.18 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-87291 | LOW3.18 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-91332 | LOW3.18 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-91373 | LOW3.18 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-91410 | LOW3.18 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-91418 | LOW3.18 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-91451 | LOW3.18 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-91452 | LOW3.18 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-91453 | LOW3.18 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-91463 | LOW3.18 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91464 | LOW3.18 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4360 | LOW3.18 | python3 3.9.25-1.amzn2023.0.8 fixed in 3.9.25-1.amzn2023.0.9 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-45409 | LOW3.18 | python3-pip-wheel 21.3.1-2.amzn2023.0.20 fixed in 21.3.1-2.amzn2023.0.21 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-92392 | LOW2.92 | curl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.3 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-92392 | LOW2.92 | libcurl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.3 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-8926 | LOW2.88 | curl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-83381 | LOW2.88 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91374 | LOW2.88 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91415 | LOW2.88 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91487 | LOW2.88 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-8926 | LOW2.88 | libcurl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-10536 | LOW2.82 | curl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-91375 | LOW2.82 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-91379 | LOW2.82 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-10536 | LOW2.82 | libcurl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-97689 | LOW2.7 | python3-pip-wheel 21.3.1-2.amzn2023.0.20 fixed in 21.3.1-2.amzn2023.0.22 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-19553 | LOW2.66 | python3 3.9.25-1.amzn2023.0.8 fixed in 3.9.25-1.amzn2023.0.11 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-78367 | LOW2.52 | rpm 4.16.1.3-29.amzn2023.0.6 fixed in 4.16.1.3-29.amzn2023.0.8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-84233 | LOW2.52 | rpm 4.16.1.3-29.amzn2023.0.6 fixed in 4.16.1.3-29.amzn2023.0.8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-11586 | LOW2.48 | curl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | 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 | 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-11586 | LOW2.48 | libcurl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.1 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | 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-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-91380 | LOW2.4 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7774 | LOW2.34 | python3 3.9.25-1.amzn2023.0.8 fixed in 3.9.25-1.amzn2023.0.9 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW2.22 | curl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-60589 | LOW2.22 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.20+10-1.amzn2023.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-83376 | LOW2.22 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-83378 | LOW2.22 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-87255 | LOW2.22 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-87290 | LOW2.22 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-87292 | LOW2.22 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-87367 | LOW2.22 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-91334 | LOW2.22 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91381 | LOW2.22 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91409 | LOW2.22 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-91461 | LOW2.22 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-80230 | LOW2.22 | libcurl-minimal 8.17.0-1.amzn2023.0.3 fixed in 8.21.0-5.amzn2023.0.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-91397 | LOW2.16 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-91400 | LOW1.86 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-91335 | LOW1.56 | java-17-amazon-corretto-headless 1:17.0.20+8-1.amzn2023.1 fixed in 1:17.0.21.0.10-1.amzn2023.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-113470 | NONE0 | ca-certificates 2025.2.76-1.0.amzn2023.0.3 fixed in 2025.2.76-1.0.amzn2023.0.4 | 0.5% Theoretical Threat | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.