Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker could exploit CVE-2025-15467 to achieve remote code execution or denial of service, and CVE-2025-27817 to read arbitrary files and perform SSRF, potentially exposing sensitive data. Applying security patches for these libraries and restricting network access to the service are essential before any production use.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2025-15467 | CRITICAL10 | openssl-libs 1:3.0.8-1.amzn2023.0.14 fixed in 1:3.2.2-1.amzn2023.0.4 | 47.6% High Exploitation Risk | Directly Exposed |
| CVE-2025-27817 | CRITICAL10 | org.apache.kafka:kafka-clients 3.7.1 fixed in 3.9.1 | 64.7% Actively Exploited | Directly Exposed |
| CVE-2025-6965 | CRITICAL10 | sqlite-libs 3.40.0-1.amzn2023.0.4 fixed in 3.40.0-1.amzn2023.0.6 | 74.4% Actively Exploited | Directly Exposed |
| CVE-2024-56171 | CRITICAL9.8 | libxml2 2.10.4-1.amzn2023.0.6 fixed in 2.10.4-1.amzn2023.0.9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-6119 | CRITICAL9.75 | openssl-libs 1:3.0.8-1.amzn2023.0.14 fixed in 1:3.0.8-1.amzn2023.0.15 | 66.6% Actively Exploited | Directly Exposed |
| CVE-2025-49796 | CRITICAL9.1 | libxml2 2.10.4-1.amzn2023.0.6 fixed in 2.10.4-1.amzn2023.0.12 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-48734 | HIGH8.8 | commons-beanutils:commons-beanutils 1.9.4 fixed in 1.11.0 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2025-68121 | HIGH8.5 | libcap 2.48-2.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-14087 | HIGH8.33 | glib2 2.74.7-689.amzn2023.0.2 fixed in 2.82.2-769.amzn2023 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-6653 | HIGH8.33 | libxml2 2.10.4-1.amzn2023.0.6 fixed in 2.10.4-1.amzn2023.0.19 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42581 | HIGH8.33 | io.netty:netty-codec-http 4.1.108.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42581 | HIGH8.33 | io.netty:netty-codec-http 4.1.112.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45447 | HIGH8.1 | openssl-libs 1:3.0.8-1.amzn2023.0.14 fixed in 1:3.5.5-1.amzn2023.0.5 | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | glib2 2.74.7-689.amzn2023.0.2 fixed in 2.82.2-770.amzn2023 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-49794 | HIGH7.73 | libxml2 2.10.4-1.amzn2023.0.6 fixed in 2.10.4-1.amzn2023.0.12 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | HIGH7.73 | openssl-libs 1:3.0.8-1.amzn2023.0.14 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42584 | HIGH7.73 | io.netty:netty-codec-http 4.1.108.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42584 | HIGH7.73 | io.netty:netty-codec-http 4.1.112.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | glibc 2.34-52.amzn2023.0.11 fixed in 2.34-181.amzn2023.0.1 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | glibc-common 2.34-52.amzn2023.0.11 fixed in 2.34-181.amzn2023.0.1 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | glibc-minimal-langpack 2.34-52.amzn2023.0.11 fixed in 2.34-181.amzn2023.0.1 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-52425 | HIGH7.5 | expat 2.5.0-1.amzn2023.0.4 fixed in 2.6.3-1.amzn2023.0.1 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-45490 | HIGH7.5 | expat 2.5.0-1.amzn2023.0.4 fixed in 2.6.3-1.amzn2023.0.1 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-43396 | HIGH7.5 | glibc 2.34-52.amzn2023.0.11 fixed in 2.34-181.amzn2023.0.1 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-43396 | HIGH7.5 | glibc-common 2.34-52.amzn2023.0.11 fixed in 2.34-181.amzn2023.0.1 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-43396 | HIGH7.5 | glibc-minimal-langpack 2.34-52.amzn2023.0.11 fixed in 2.34-181.amzn2023.0.1 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-61726 | HIGH7.5 | libcap 2.48-2.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.6 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-27113 | HIGH7.5 | libxml2 2.10.4-1.amzn2023.0.6 fixed in 2.10.4-1.amzn2023.0.9 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-6021 | HIGH7.5 | libxml2 2.10.4-1.amzn2023.0.6 fixed in 2.10.4-1.amzn2023.0.11 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28388 | HIGH7.5 | openssl-libs 1:3.0.8-1.amzn2023.0.14 fixed in 1:3.5.5-1.amzn2023.0.4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28389 | HIGH7.5 | openssl-libs 1:3.0.8-1.amzn2023.0.14 fixed in 1:3.5.5-1.amzn2023.0.4 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28390 | HIGH7.5 | openssl-libs 1:3.0.8-1.amzn2023.0.14 fixed in 1:3.5.5-1.amzn2023.0.4 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34183 | HIGH7.5 | openssl-libs 1:3.0.8-1.amzn2023.0.14 fixed in 1:3.5.5-1.amzn2023.0.5 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-7254 | HIGH7.5 | com.google.protobuf:protobuf-java 3.22.1 fixed in 3.25.5, 4.27.5, 4.28.2 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2025-55163 | HIGH7.5 | io.netty:netty-codec-http2 4.1.108.Final fixed in 4.2.4.Final, 4.1.124.Final | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33871 | HIGH7.5 | io.netty:netty-codec-http2 4.1.108.Final fixed in 4.1.132.Final, 4.2.11.Final | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-55163 | HIGH7.5 | io.netty:netty-codec-http2 4.1.112.Final fixed in 4.2.4.Final, 4.1.124.Final | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33871 | HIGH7.5 | io.netty:netty-codec-http2 4.1.112.Final fixed in 4.1.132.Final, 4.2.11.Final | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-24970 | HIGH7.5 | io.netty:netty-handler 4.1.108.Final fixed in 4.1.118.Final | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-24970 | HIGH7.5 | io.netty:netty-handler 4.1.112.Final fixed in 4.1.118.Final | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | glib2 2.74.7-689.amzn2023.0.2 fixed in 2.82.2-770.amzn2023 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | glib2 2.74.7-689.amzn2023.0.2 fixed in 2.82.2-770.amzn2023 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | glib2 2.74.7-689.amzn2023.0.2 fixed in 2.82.2-770.amzn2023 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | glib2 2.74.7-689.amzn2023.0.2 fixed in 2.82.2-770.amzn2023 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | openssl-libs 1:3.0.8-1.amzn2023.0.14 fixed in 1:3.5.5-1.amzn2023.0.4 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-54512 | MEDIUM6.88 | com.fasterxml.jackson.core:jackson-databind 2.14.1 fixed in 2.18.8, 3.1.4, 2.21.4 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-54513 | MEDIUM6.88 | com.fasterxml.jackson.core:jackson-databind 2.14.1 fixed in 2.18.8, 2.21.4, 3.1.4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-54512 | MEDIUM6.88 | com.fasterxml.jackson.core:jackson-databind 2.16.1 fixed in 2.18.8, 3.1.4, 2.21.4 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-54513 | MEDIUM6.88 | com.fasterxml.jackson.core:jackson-databind 2.16.1 fixed in 2.18.8, 2.21.4, 3.1.4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-54512 | MEDIUM6.88 | com.fasterxml.jackson.core:jackson-databind 2.17.1 fixed in 2.18.8, 3.1.4, 2.21.4 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-54513 | MEDIUM6.88 | com.fasterxml.jackson.core:jackson-databind 2.17.1 fixed in 2.18.8, 2.21.4, 3.1.4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-54512 | MEDIUM6.88 | com.fasterxml.jackson.core:jackson-databind 2.17.2 fixed in 2.18.8, 3.1.4, 2.21.4 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-54513 | MEDIUM6.88 | com.fasterxml.jackson.core:jackson-databind 2.17.2 fixed in 2.18.8, 2.21.4, 3.1.4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-44249 | MEDIUM6.88 | io.netty:netty-handler 4.1.108.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44249 | MEDIUM6.88 | io.netty:netty-handler 4.1.112.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1372 | MEDIUM6.63 | elfutils-libelf 0.188-3.amzn2023.0.2 fixed in 0.188-3.amzn2023.0.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1372 | MEDIUM6.63 | elfutils-libs 0.188-3.amzn2023.0.2 fixed in 0.188-3.amzn2023.0.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25210 | MEDIUM6.63 | expat 2.5.0-1.amzn2023.0.4 fixed in 2.6.3-1.amzn2023.0.4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-48957 | MEDIUM6.63 | libarchive 3.7.4-2.amzn2023.0.1 fixed in 3.7.4-2.amzn2023.0.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-48958 | MEDIUM6.63 | libarchive 3.7.4-2.amzn2023.0.1 fixed in 3.7.4-2.amzn2023.0.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-5914 | MEDIUM6.63 | libarchive 3.7.4-2.amzn2023.0.1 fixed in 3.7.4-2.amzn2023.0.3 | 0.3% 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-2022-49043 | MEDIUM6.63 | libxml2 2.10.4-1.amzn2023.0.6 fixed in 2.10.4-1.amzn2023.0.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7425 | MEDIUM6.63 | libxml2 2.10.4-1.amzn2023.0.6 fixed in 2.10.4-1.amzn2023.0.13 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-13601 | MEDIUM6.54 | glib2 2.74.7-689.amzn2023.0.2 fixed in 2.82.2-767.amzn2023 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-24928 | MEDIUM6.54 | libxml2 2.10.4-1.amzn2023.0.6 fixed in 2.10.4-1.amzn2023.0.9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1352 | MEDIUM6.38 | elfutils-libelf 0.188-3.amzn2023.0.2 fixed in 0.188-3.amzn2023.0.3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1352 | MEDIUM6.38 | elfutils-libs 0.188-3.amzn2023.0.2 fixed in 0.188-3.amzn2023.0.3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-6052 | MEDIUM6.38 | glib2 2.74.7-689.amzn2023.0.2 fixed in 2.82.2-766.amzn2023 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | glib2 2.74.7-689.amzn2023.0.2 fixed in 2.82.2-770.amzn2023 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | glib2 2.74.7-689.amzn2023.0.2 fixed in 2.82.2-770.amzn2023 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | krb5-libs 1.21.3-1.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-1.amzn2023.0.1 fixed in 1.21.3-7.amzn2023.0.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-22874 | MEDIUM6.38 | libcap 2.48-2.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-58183 | MEDIUM6.38 | libcap 2.48-2.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61728 | MEDIUM6.38 | libcap 2.48-2.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61729 | MEDIUM6.38 | libcap 2.48-2.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33811 | MEDIUM6.38 | libcap 2.48-2.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM6.38 | libcap 2.48-2.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39820 | MEDIUM6.38 | libcap 2.48-2.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42499 | MEDIUM6.38 | libcap 2.48-2.amzn2023.0.3 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.1 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-2025-49795 | MEDIUM6.38 | libxml2 2.10.4-1.amzn2023.0.6 fixed in 2.10.4-1.amzn2023.0.12 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-32414 | MEDIUM6.38 | libxml2 2.10.4-1.amzn2023.0.6 fixed in 2.10.4-1.amzn2023.0.10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-32415 | MEDIUM6.38 | libxml2 2.10.4-1.amzn2023.0.6 fixed in 2.10.4-1.amzn2023.0.10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | openssl-libs 1:3.0.8-1.amzn2023.0.14 fixed in 1:3.2.2-1.amzn2023.0.5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42583 | MEDIUM6.38 | io.netty:netty-codec 4.1.108.Final fixed in 4.1.133.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59901 | MEDIUM6.38 | io.netty:netty-codec 4.1.108.Final fixed in 4.1.136.Final | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-58057 | MEDIUM6.38 | io.netty:netty-codec 4.1.108.Final fixed in 4.1.125.Final | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42583 | MEDIUM6.38 | io.netty:netty-codec 4.1.112.Final fixed in 4.1.133.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59901 | MEDIUM6.38 | io.netty:netty-codec 4.1.112.Final fixed in 4.1.136.Final | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-58057 | MEDIUM6.38 | io.netty:netty-codec 4.1.112.Final fixed in 4.1.125.Final | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33870 | MEDIUM6.38 | io.netty:netty-codec-http 4.1.108.Final fixed in 4.1.132.Final, 4.2.10.Final | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42587 | MEDIUM6.38 | io.netty:netty-codec-http 4.1.108.Final fixed in 4.2.13.Final, 4.1.133.Final | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-55831 | MEDIUM6.38 | io.netty:netty-codec-http 4.1.108.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-55833 | MEDIUM6.38 | io.netty:netty-codec-http 4.1.108.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56745 | MEDIUM6.38 | io.netty:netty-codec-http 4.1.108.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42585 | MEDIUM6.38 | io.netty:netty-codec-http 4.1.108.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56746 | MEDIUM6.38 | io.netty:netty-codec-http 4.1.108.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59899 | MEDIUM6.38 | io.netty:netty-codec-http 4.1.108.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-58056 | MEDIUM6.38 | io.netty:netty-codec-http 4.1.108.Final fixed in 4.1.125.Final, 4.2.5.Final | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33870 | MEDIUM6.38 | io.netty:netty-codec-http 4.1.112.Final fixed in 4.1.132.Final, 4.2.10.Final | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42587 | MEDIUM6.38 | io.netty:netty-codec-http 4.1.112.Final fixed in 4.2.13.Final, 4.1.133.Final | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-55831 | MEDIUM6.38 | io.netty:netty-codec-http 4.1.112.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-55833 | MEDIUM6.38 | io.netty:netty-codec-http 4.1.112.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56745 | MEDIUM6.38 | io.netty:netty-codec-http 4.1.112.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42585 | MEDIUM6.38 | io.netty:netty-codec-http 4.1.112.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56746 | MEDIUM6.38 | io.netty:netty-codec-http 4.1.112.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59899 | MEDIUM6.38 | io.netty:netty-codec-http 4.1.112.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-58056 | MEDIUM6.38 | io.netty:netty-codec-http 4.1.112.Final fixed in 4.1.125.Final, 4.2.5.Final | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42587 | MEDIUM6.38 | io.netty:netty-codec-http2 4.1.108.Final fixed in 4.2.13.Final, 4.1.133.Final | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-48043 | MEDIUM6.38 | io.netty:netty-codec-http2 4.1.108.Final fixed in 4.1.135.Final, 4.2.15.Final | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42587 | MEDIUM6.38 | io.netty:netty-codec-http2 4.1.112.Final fixed in 4.2.13.Final, 4.1.133.Final | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-48043 | MEDIUM6.38 | io.netty:netty-codec-http2 4.1.112.Final fixed in 4.1.135.Final, 4.2.15.Final | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45416 | MEDIUM6.38 | io.netty:netty-handler 4.1.108.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-50010 | MEDIUM6.38 | io.netty:netty-handler 4.1.108.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45416 | MEDIUM6.38 | io.netty:netty-handler 4.1.112.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-50010 | MEDIUM6.38 | io.netty:netty-handler 4.1.112.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42578 | MEDIUM6.38 | io.netty:netty-handler-proxy 4.1.112.Final fixed in 4.1.133.Final, 4.2.13.Final | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-57699 | MEDIUM6.38 | net.minidev:json-smart 2.5.0 fixed in 2.5.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-34478 | MEDIUM6.38 | org.apache.logging.log4j:log4j-core 2.21.0 fixed in 2.25.4 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-34480 | MEDIUM6.38 | org.apache.logging.log4j:log4j-core 2.21.0 fixed in 2.25.4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-5588 | MEDIUM6.38 | org.bouncycastle:bcpkix-jdk15to18 1.78.1 fixed in 1.84 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5588 | MEDIUM6.38 | org.bouncycastle:bcpkix-jdk18on 1.78 fixed in 1.84 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5588 | MEDIUM6.38 | org.bouncycastle:bcpkix-jdk18on 1.78.1 fixed in 1.84 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14813 | MEDIUM6.38 | org.bouncycastle:bcprov-ext-jdk18on 1.75 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-14813 | MEDIUM6.38 | org.bouncycastle:bcprov-jdk15to18 1.78.1 fixed in 1.84 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5598 | MEDIUM6.38 | org.bouncycastle:bcprov-jdk15to18 1.78.1 fixed in 1.80.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-14813 | MEDIUM6.38 | org.bouncycastle:bcprov-jdk18on 1.78 fixed in 1.80.2, 1.81.1, 1.84 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-14813 | MEDIUM6.38 | org.bouncycastle:bcprov-jdk18on 1.78.1 fixed in 1.80.2, 1.81.1, 1.84 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66566 | MEDIUM6.38 | org.lz4:lz4-java 1.8.0 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-9624 | MEDIUM6.38 | org.opensearch:opensearch-common 2.17.0 fixed in 3.3.0, 2.19.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | openssl-libs 1:3.0.8-1.amzn2023.0.14 fixed in 1:3.2.2-1.amzn2023.0.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | openssl-libs 1:3.0.8-1.amzn2023.0.14 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-46908 | MEDIUM6.21 | sqlite-libs 3.40.0-1.amzn2023.0.4 fixed in 3.40.0-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-2025-4802 | MEDIUM5.95 | glibc 2.34-52.amzn2023.0.11 fixed in 2.34-196.amzn2023.0.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | glibc-common 2.34-52.amzn2023.0.11 fixed in 2.34-196.amzn2023.0.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | glibc-minimal-langpack 2.34-52.amzn2023.0.11 fixed in 2.34-196.amzn2023.0.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-50602 | MEDIUM5.9 | expat 2.5.0-1.amzn2023.0.4 fixed in 2.6.3-1.amzn2023.0.2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt 1.10.2-1.amzn2023.0.1 fixed in 1.10.2-1.amzn2023.0.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1 4.19.0-1.amzn2023.0.4 fixed in 4.19.0-1.amzn2023.0.6 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.9 | openssl-libs 1:3.0.8-1.amzn2023.0.14 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.0.8-1.amzn2023.0.14 fixed in 1:3.5.5-1.amzn2023.0.5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-41996 | MEDIUM5.9 | openssl-libs 1:3.0.8-1.amzn2023.0.14 fixed in 1:3.0.8-1.amzn2023.0.16 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9231 | MEDIUM5.9 | openssl-libs 1:3.0.8-1.amzn2023.0.14 fixed in 1:3.2.2-1.amzn2023.0.2 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56132 | MEDIUM5.87 | expat 2.5.0-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.5.0-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.5.0-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.5.0-1.amzn2023.0.4 fixed in 2.6.3-1.amzn2023.0.6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-4673 | MEDIUM5.78 | libcap 2.48-2.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-35554 | MEDIUM5.78 | org.apache.kafka:kafka-clients 3.7.1 fixed in 3.9.2, 4.0.2, 4.1.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5915 | MEDIUM5.61 | libarchive 3.7.4-2.amzn2023.0.1 fixed in 3.7.4-2.amzn2023.0.4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | openssl-libs 1:3.0.8-1.amzn2023.0.14 fixed in 1:3.2.2-1.amzn2023.0.2 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | krb5-libs 1.21.3-1.amzn2023.0.1 fixed in 1.21.3-6.amzn2023.0.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61727 | MEDIUM5.52 | libcap 2.48-2.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.5 | 0.3% 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-2673 | MEDIUM5.52 | openssl-libs 1:3.0.8-1.amzn2023.0.14 fixed in 1:3.5.5-1.amzn2023.0.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59888 | MEDIUM5.52 | com.fasterxml.jackson.core:jackson-databind 2.16.1 fixed in 2.18.8, 2.21.4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59888 | MEDIUM5.52 | com.fasterxml.jackson.core:jackson-databind 2.17.1 fixed in 2.18.8, 2.21.4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59888 | MEDIUM5.52 | com.fasterxml.jackson.core:jackson-databind 2.17.2 fixed in 2.18.8, 2.21.4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-67735 | MEDIUM5.52 | io.netty:netty-codec-http 4.1.108.Final fixed in 4.2.8.Final, 4.1.129.Final | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41417 | MEDIUM5.52 | io.netty:netty-codec-http 4.1.108.Final fixed in 4.1.133.Final, 4.2.13.Final | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42580 | MEDIUM5.52 | io.netty:netty-codec-http 4.1.108.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-67735 | MEDIUM5.52 | io.netty:netty-codec-http 4.1.112.Final fixed in 4.2.8.Final, 4.1.129.Final | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41417 | MEDIUM5.52 | io.netty:netty-codec-http 4.1.112.Final fixed in 4.1.133.Final, 4.2.13.Final | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42580 | MEDIUM5.52 | io.netty:netty-codec-http 4.1.112.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59900 | MEDIUM5.52 | io.netty:netty-codec-http2 4.1.108.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59900 | MEDIUM5.52 | io.netty:netty-codec-http2 4.1.112.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0636 | MEDIUM5.52 | org.bouncycastle:bcprov-jdk15to18 1.78.1 fixed in 1.84 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0636 | MEDIUM5.52 | org.bouncycastle:bcprov-jdk18on 1.78 fixed in 1.84 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0636 | MEDIUM5.52 | org.bouncycastle:bcprov-jdk18on 1.78.1 fixed in 1.84 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-12183 | MEDIUM5.52 | org.lz4:lz4-java 1.8.0 fixed in 1.8.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-34459 | MEDIUM5.5 | libxml2 2.10.4-1.amzn2023.0.6 fixed in 2.10.4-1.amzn2023.0.7 | 2.3% Low-Moderate Risk | 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-libs 1:3.0.8-1.amzn2023.0.14 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.0.8-1.amzn2023.0.14 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-59375 | MEDIUM5.3 | expat 2.5.0-1.amzn2023.0.4 fixed in 2.6.3-1.amzn2023.0.3 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | glibc 2.34-52.amzn2023.0.11 fixed in 2.34-181.amzn2023.0.1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | glibc-common 2.34-52.amzn2023.0.11 fixed in 2.34-181.amzn2023.0.1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | glibc-minimal-langpack 2.34-52.amzn2023.0.11 fixed in 2.34-181.amzn2023.0.1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-12133 | MEDIUM5.3 | libtasn1 4.19.0-1.amzn2023.0.4 fixed in 4.19.0-1.amzn2023.0.5 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-47273 | MEDIUM5.28 | python3-setuptools-wheel 59.6.0-2.amzn2023.0.5 fixed in 59.6.0-2.amzn2023.0.6 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-1757 | MEDIUM5.27 | libxml2 2.10.4-1.amzn2023.0.6 fixed in 2.10.4-1.amzn2023.0.18 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1390 | MEDIUM5.18 | libcap 2.48-2.amzn2023.0.3 fixed in 2.48-2.amzn2023.0.4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | krb5-libs 1.21.3-1.amzn2023.0.1 fixed in 1.21.3-6.amzn2023.0.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0990 | MEDIUM5.02 | libxml2 2.10.4-1.amzn2023.0.6 fixed in 2.10.4-1.amzn2023.0.16 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-15468 | MEDIUM5.02 | openssl-libs 1:3.0.8-1.amzn2023.0.14 fixed in 1:3.2.2-1.amzn2023.0.5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-66199 | MEDIUM5.02 | openssl-libs 1:3.0.8-1.amzn2023.0.14 fixed in 1:3.2.2-1.amzn2023.0.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | openssl-libs 1:3.0.8-1.amzn2023.0.14 fixed in 1:3.2.2-1.amzn2023.0.5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | openssl-libs 1:3.0.8-1.amzn2023.0.14 fixed in 1:3.2.2-1.amzn2023.0.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.02 | openssl-libs 1:3.0.8-1.amzn2023.0.14 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.0.8-1.amzn2023.0.14 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.0.8-1.amzn2023.0.14 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-34477 | MEDIUM5.02 | org.apache.logging.log4j:log4j-core 2.21.0 fixed in 2.25.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | openssl-libs 1:3.0.8-1.amzn2023.0.14 fixed in 1:3.5.5-1.amzn2023.0.5 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-53864 | MEDIUM4.93 | com.nimbusds:nimbus-jose-jwt 9.40 fixed in 10.0.2, 9.37.4 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-59921 | MEDIUM4.84 | io.netty:netty-codec-http 4.1.108.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59921 | MEDIUM4.84 | io.netty:netty-codec-http 4.1.112.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2007-4559 | MEDIUM4.69 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.20-1.amzn2023.0.2 | 27.1% High Exploitation Risk | Post-Exploit |
| CVE-2007-4559 | MEDIUM4.69 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.20-1.amzn2023.0.2 | 27.1% High Exploitation Risk | Post-Exploit |
| CVE-2007-4559 | MEDIUM4.69 | python3-pip-wheel 21.3.1-2.amzn2023.0.7 fixed in 21.3.1-2.amzn2023.0.11 | 27.1% High Exploitation Risk | Post-Exploit |
| CVE-2025-0395 | MEDIUM4.67 | glibc 2.34-52.amzn2023.0.11 fixed in 2.34-181.amzn2023.0.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | glibc-common 2.34-52.amzn2023.0.11 fixed in 2.34-181.amzn2023.0.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | glibc-minimal-langpack 2.34-52.amzn2023.0.11 fixed in 2.34-181.amzn2023.0.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM4.67 | openssl-libs 1:3.0.8-1.amzn2023.0.14 fixed in 1:3.2.2-1.amzn2023.0.5 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | openssl-libs 1:3.0.8-1.amzn2023.0.14 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-47535 | MEDIUM4.67 | io.netty:netty-common 4.1.108.Final fixed in 4.1.115.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-25193 | MEDIUM4.67 | io.netty:netty-common 4.1.108.Final fixed in 4.1.118.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-47535 | MEDIUM4.67 | io.netty:netty-common 4.1.112.Final fixed in 4.1.115.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-25193 | MEDIUM4.67 | io.netty:netty-common 4.1.112.Final fixed in 4.1.118.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27142 | MEDIUM4.59 | libcap 2.48-2.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39823 | MEDIUM4.59 | libcap 2.48-2.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-4517 | MEDIUM4.56 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.23-1.amzn2023.0.1 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-4517 | MEDIUM4.56 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.23-1.amzn2023.0.1 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-6232 | MEDIUM4.5 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.20-1.amzn2023.0.2 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-4138 | MEDIUM4.5 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.23-1.amzn2023.0.1 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-7592 | MEDIUM4.5 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.20-1.amzn2023.0.2 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-6232 | MEDIUM4.5 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.20-1.amzn2023.0.2 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-4138 | MEDIUM4.5 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.23-1.amzn2023.0.1 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-7592 | MEDIUM4.5 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.20-1.amzn2023.0.2 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-21441 | MEDIUM4.5 | python3-pip-wheel 21.3.1-2.amzn2023.0.7 fixed in 21.3.1-2.amzn2023.0.16 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-3651 | MEDIUM4.5 | python3-pip-wheel 21.3.1-2.amzn2023.0.7 fixed in 21.3.1-2.amzn2023.0.9 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4046 | MEDIUM4.5 | glibc 2.34-52.amzn2023.0.11 fixed in 2.34-231.amzn2023.0.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-common 2.34-52.amzn2023.0.11 fixed in 2.34-231.amzn2023.0.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-minimal-langpack 2.34-52.amzn2023.0.11 fixed in 2.34-231.amzn2023.0.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-47912 | MEDIUM4.5 | libcap 2.48-2.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58185 | MEDIUM4.5 | libcap 2.48-2.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58186 | MEDIUM4.5 | libcap 2.48-2.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58187 | MEDIUM4.5 | libcap 2.48-2.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58188 | MEDIUM4.5 | libcap 2.48-2.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58189 | MEDIUM4.5 | libcap 2.48-2.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61723 | MEDIUM4.5 | libcap 2.48-2.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61724 | MEDIUM4.5 | libcap 2.48-2.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61725 | MEDIUM4.5 | libcap 2.48-2.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61730 | MEDIUM4.5 | libcap 2.48-2.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | openssl-libs 1:3.0.8-1.amzn2023.0.14 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.0.8-1.amzn2023.0.14 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-54514 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-databind 2.14.1 fixed in 2.18.8, 2.21.4, 3.1.4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54515 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-databind 2.14.1 fixed in 3.1.4, 2.18.9, 2.21.5, 2.22.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54514 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-databind 2.16.1 fixed in 2.18.8, 2.21.4, 3.1.4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54515 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-databind 2.16.1 fixed in 3.1.4, 2.18.9, 2.21.5, 2.22.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54514 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-databind 2.17.1 fixed in 2.18.8, 2.21.4, 3.1.4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54515 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-databind 2.17.1 fixed in 3.1.4, 2.18.9, 2.21.5, 2.22.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54514 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-databind 2.17.2 fixed in 2.18.8, 2.21.4, 3.1.4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54515 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-databind 2.17.2 fixed in 3.1.4, 2.18.9, 2.21.5, 2.22.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-50020 | MEDIUM4.5 | io.netty:netty-codec-http 4.1.108.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59898 | MEDIUM4.5 | io.netty:netty-codec-http 4.1.108.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-50020 | MEDIUM4.5 | io.netty:netty-codec-http 4.1.112.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59898 | MEDIUM4.5 | io.netty:netty-codec-http 4.1.112.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47244 | MEDIUM4.5 | io.netty:netty-codec-http2 4.1.108.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-50560 | MEDIUM4.5 | io.netty:netty-codec-http2 4.1.108.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47244 | MEDIUM4.5 | io.netty:netty-codec-http2 4.1.112.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-50560 | MEDIUM4.5 | io.netty:netty-codec-http2 4.1.112.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8885 | MEDIUM4.5 | org.bouncycastle:bc-fips 2.0.0 fixed in 1.0.2.6, 2.0.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-8916 | MEDIUM4.5 | org.bouncycastle:bcpkix-jdk15to18 1.78.1 fixed in 1.79 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-8916 | MEDIUM4.5 | org.bouncycastle:bcpkix-jdk18on 1.78 fixed in 1.79 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-8916 | MEDIUM4.5 | org.bouncycastle:bcpkix-jdk18on 1.78.1 fixed in 1.79 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-47554 | MEDIUM4.3 | commons-io:commons-io 2.7 fixed in 2.14.0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-47554 | MEDIUM4.3 | commons-io:commons-io 2.8.0 fixed in 2.14.0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | krb5-libs 1.21.3-1.amzn2023.0.1 fixed in 1.21.3-8.amzn2023.0.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5917 | MEDIUM4.25 | libarchive 3.7.4-2.amzn2023.0.1 fixed in 3.7.4-2.amzn2023.0.4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | MEDIUM4.13 | curl-minimal 8.5.0-1.amzn2023.0.4 fixed in 8.17.0-1.amzn2023.0.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl-minimal 8.5.0-1.amzn2023.0.4 fixed in 8.17.0-1.amzn2023.0.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | MEDIUM4.13 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.5 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | MEDIUM4.13 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.5 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-0938 | MEDIUM4.08 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.21-1.amzn2023.0.2 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0938 | MEDIUM4.08 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.21-1.amzn2023.0.2 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-68161 | MEDIUM4.08 | org.apache.logging.log4j:log4j-core 2.21.0 fixed in 2.25.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4 | openssl-libs 1:3.0.8-1.amzn2023.0.14 fixed in 1:3.2.2-1.amzn2023.0.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | openssl-libs 1:3.0.8-1.amzn2023.0.14 fixed in 1:3.0.8-1.amzn2023.0.19 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | glibc 2.34-52.amzn2023.0.11 fixed in 2.34-181.amzn2023.0.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | glibc-common 2.34-52.amzn2023.0.11 fixed in 2.34-181.amzn2023.0.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | glibc-minimal-langpack 2.34-52.amzn2023.0.11 fixed in 2.34-181.amzn2023.0.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-24882 | LOW3.98 | gnupg2-minimal 2.3.7-1.amzn2023.0.4 fixed in 2.3.7-1.amzn2023.0.7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-9287 | LOW3.98 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.21-1.amzn2023.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-9287 | LOW3.98 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.21-1.amzn2023.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-9681 | LOW3.9 | curl-minimal 8.5.0-1.amzn2023.0.4 fixed in 8.11.1-4.amzn2023.0.1 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2024-9681 | LOW3.9 | libcurl-minimal 8.5.0-1.amzn2023.0.4 fixed in 8.11.1-4.amzn2023.0.1 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2024-37891 | LOW3.9 | python3-pip-wheel 21.3.1-2.amzn2023.0.7 fixed in 21.3.1-2.amzn2023.0.8 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-12718 | LOW3.88 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.23-1.amzn2023.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-12718 | LOW3.88 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.23-1.amzn2023.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-4435 | LOW3.82 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.23-1.amzn2023.0.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8194 | LOW3.82 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.23-1.amzn2023.0.3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3644 | LOW3.82 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW3.82 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW3.82 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.7 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-4435 | LOW3.82 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.23-1.amzn2023.0.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8194 | LOW3.82 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.23-1.amzn2023.0.3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3644 | LOW3.82 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW3.82 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW3.82 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.7 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-66418 | LOW3.82 | python3-pip-wheel 21.3.1-2.amzn2023.0.7 fixed in 21.3.1-2.amzn2023.0.15 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-66471 | LOW3.82 | python3-pip-wheel 21.3.1-2.amzn2023.0.7 fixed in 21.3.1-2.amzn2023.0.15 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-4330 | LOW3.72 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.23-1.amzn2023.0.1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-4330 | LOW3.72 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.23-1.amzn2023.0.1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-48924 | LOW3.7 | org.apache.commons:commons-lang3 3.10 fixed in 3.18.0 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-48924 | LOW3.7 | org.apache.commons:commons-lang3 3.12.0 fixed in 3.18.0 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-48924 | LOW3.7 | org.apache.commons:commons-lang3 3.13.0 fixed in 3.18.0 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-48924 | LOW3.7 | org.apache.commons:commons-lang3 3.14.0 fixed in 3.18.0 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-48924 | LOW3.7 | org.apache.commons:commons-lang3 3.16.0 fixed in 3.18.0 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-1299 | LOW3.62 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-4786 | LOW3.62 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.5 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1299 | LOW3.62 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-4786 | LOW3.62 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.5 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gnupg2-minimal 2.3.7-1.amzn2023.0.4 fixed in 2.3.7-1.amzn2023.0.6 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8058 | LOW3.57 | glibc 2.34-52.amzn2023.0.11 fixed in 2.34-231.amzn2023.0.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | glibc-common 2.34-52.amzn2023.0.11 fixed in 2.34-231.amzn2023.0.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | glibc-minimal-langpack 2.34-52.amzn2023.0.11 fixed in 2.34-231.amzn2023.0.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-11053 | LOW3.54 | curl-minimal 8.5.0-1.amzn2023.0.4 fixed in 8.15.0-4.amzn2023.0.1 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2024-11053 | LOW3.54 | libcurl-minimal 8.5.0-1.amzn2023.0.4 fixed in 8.15.0-4.amzn2023.0.1 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-13034 | LOW3.47 | curl-minimal 8.5.0-1.amzn2023.0.4 fixed in 8.17.0-1.amzn2023.0.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | curl-minimal 8.5.0-1.amzn2023.0.4 fixed in 8.17.0-1.amzn2023.0.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-13034 | LOW3.47 | libcurl-minimal 8.5.0-1.amzn2023.0.4 fixed in 8.17.0-1.amzn2023.0.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | libcurl-minimal 8.5.0-1.amzn2023.0.4 fixed in 8.17.0-1.amzn2023.0.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-6923 | LOW3.47 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.20-1.amzn2023.0.2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2024-6923 | LOW3.47 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.20-1.amzn2023.0.2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2024-33602 | LOW3.4 | glibc 2.34-52.amzn2023.0.11 fixed in 2.34-181.amzn2023.0.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | glibc-common 2.34-52.amzn2023.0.11 fixed in 2.34-181.amzn2023.0.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | glibc-minimal-langpack 2.34-52.amzn2023.0.11 fixed in 2.34-181.amzn2023.0.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW3.4 | openssl-libs 1:3.0.8-1.amzn2023.0.14 fixed in 1:3.2.2-1.amzn2023.0.5 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11563 | LOW3.31 | curl-minimal 8.5.0-1.amzn2023.0.4 fixed in 8.11.1-4.amzn2023.0.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | curl-minimal 8.5.0-1.amzn2023.0.4 fixed in 8.17.0-1.amzn2023.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-11563 | LOW3.31 | libcurl-minimal 8.5.0-1.amzn2023.0.4 fixed in 8.11.1-4.amzn2023.0.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl-minimal 8.5.0-1.amzn2023.0.4 fixed in 8.17.0-1.amzn2023.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW3.31 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW3.31 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3805 | LOW3.21 | curl-minimal 8.5.0-1.amzn2023.0.4 fixed in 8.17.0-1.amzn2023.0.3 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3805 | LOW3.21 | libcurl-minimal 8.5.0-1.amzn2023.0.4 fixed in 8.17.0-1.amzn2023.0.3 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-9086 | LOW3.18 | curl-minimal 8.5.0-1.amzn2023.0.4 fixed in 8.15.0-4.amzn2023.0.1 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-9086 | LOW3.18 | libcurl-minimal 8.5.0-1.amzn2023.0.4 fixed in 8.15.0-4.amzn2023.0.1 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27043 | LOW3.18 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.20-1.amzn2023.0.2 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-8088 | LOW3.18 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.20-1.amzn2023.0.2 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27043 | LOW3.18 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.20-1.amzn2023.0.2 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-8088 | LOW3.18 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.20-1.amzn2023.0.2 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-3360 | LOW3.15 | glib2 2.74.7-689.amzn2023.0.2 fixed in 2.82.2-766.amzn2023 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0989 | LOW3.15 | libxml2 2.10.4-1.amzn2023.0.6 fixed in 2.10.4-1.amzn2023.0.17 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | openssl-libs 1:3.0.8-1.amzn2023.0.14 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | LOW3.11 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.6 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.11 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.6 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-50181 | LOW3.11 | python3-pip-wheel 21.3.1-2.amzn2023.0.7 fixed in 21.3.1-2.amzn2023.0.13 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | curl-minimal 8.5.0-1.amzn2023.0.4 fixed in 8.15.0-4.amzn2023.0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl-minimal 8.5.0-1.amzn2023.0.4 fixed in 8.15.0-4.amzn2023.0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9669 | LOW3.01 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9669 | LOW3.01 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6357 | LOW2.96 | python3-pip-wheel 21.3.1-2.amzn2023.0.7 fixed in 21.3.1-2.amzn2023.0.19 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35195 | LOW2.86 | python3-pip-wheel 21.3.1-2.amzn2023.0.7 fixed in 21.3.1-2.amzn2023.0.10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-0864 | LOW2.8 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.8 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-13837 | LOW2.8 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6075 | LOW2.8 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0864 | LOW2.8 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.8 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-13837 | LOW2.8 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6075 | LOW2.8 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-8643 | LOW2.8 | python3-pip-wheel 21.3.1-2.amzn2023.0.7 fixed in 21.3.1-2.amzn2023.0.20 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-8732 | LOW2.8 | libxml2 2.10.4-1.amzn2023.0.6 fixed in 2.10.4-1.amzn2023.0.15 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | LOW2.7 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.8 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-12084 | LOW2.7 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3446 | LOW2.7 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW2.7 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.8 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-12084 | LOW2.7 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3446 | LOW2.7 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8869 | LOW2.7 | python3-pip-wheel 21.3.1-2.amzn2023.0.7 fixed in 21.3.1-2.amzn2023.0.14 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-4516 | LOW2.6 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.22-1.amzn2023.0.2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-4516 | LOW2.6 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.22-1.amzn2023.0.2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-0992 | LOW2.46 | libxml2 2.10.4-1.amzn2023.0.6 fixed in 2.10.4-1.amzn2023.0.16 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-10148 | LOW2.45 | curl-minimal 8.5.0-1.amzn2023.0.4 fixed in 8.15.0-4.amzn2023.0.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | curl-minimal 8.5.0-1.amzn2023.0.4 fixed in 8.17.0-1.amzn2023.0.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-10148 | LOW2.45 | libcurl-minimal 8.5.0-1.amzn2023.0.4 fixed in 8.15.0-4.amzn2023.0.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl-minimal 8.5.0-1.amzn2023.0.4 fixed in 8.17.0-1.amzn2023.0.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | LOW2.45 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.45 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | LOW2.45 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.45 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl-minimal 8.5.0-1.amzn2023.0.4 fixed in 8.17.0-1.amzn2023.0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gnupg2-minimal 2.3.7-1.amzn2023.0.4 fixed in 2.3.7-1.amzn2023.0.5 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl-minimal 8.5.0-1.amzn2023.0.4 fixed in 8.17.0-1.amzn2023.0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11468 | LOW2.29 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0865 | LOW2.29 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-11468 | LOW2.29 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0865 | LOW2.29 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-4032 | LOW2.22 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.20-1.amzn2023.0.2 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4032 | LOW2.22 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.20-1.amzn2023.0.2 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-6069 | LOW2.19 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.23-1.amzn2023.0.2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8291 | LOW2.19 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.24-1.amzn2023.0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-6069 | LOW2.19 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.23-1.amzn2023.0.2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8291 | LOW2.19 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.24-1.amzn2023.0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-1703 | LOW1.99 | python3-pip-wheel 21.3.1-2.amzn2023.0.7 fixed in 21.3.1-2.amzn2023.0.17 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-11168 | LOW1.89 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.21-1.amzn2023.0.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-11168 | LOW1.89 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.21-1.amzn2023.0.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW1.68 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4519 | LOW1.68 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.68 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW1.68 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4519 | LOW1.68 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.68 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1795 | LOW1.58 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.21-1.amzn2023.0.3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1795 | LOW1.58 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.21-1.amzn2023.0.3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gnupg2-minimal 2.3.7-1.amzn2023.0.4 fixed in 2.3.7-1.amzn2023.0.9 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1372 | NONE0 | elfutils-default-yama-scope 0.188-3.amzn2023.0.2 fixed in 0.188-3.amzn2023.0.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-1352 | NONE0 | elfutils-default-yama-scope 0.188-3.amzn2023.0.2 fixed in 0.188-3.amzn2023.0.3 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-5278 | NONE0 | coreutils-single 8.32-30.amzn2023.0.3 fixed in 8.32-30.amzn2023.0.4 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-48924 | NONE0 | commons-lang:commons-lang 2.6 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-0167 | NONE0 | curl-minimal 8.5.0-1.amzn2023.0.4 fixed in 8.15.0-4.amzn2023.0.1 | 0.7% 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-2025-0167 | NONE0 | libcurl-minimal 8.5.0-1.amzn2023.0.4 fixed in 8.15.0-4.amzn2023.0.1 | 0.7% Theoretical Threat | 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.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.7 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | python3-libs 3.9.16-1.amzn2023.0.9 fixed in 3.9.25-1.amzn2023.0.8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3-libs 3.9.16-1.amzn2023.0.9 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.4 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.4 fixed in 3.40.0-1.amzn2023.0.8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-0851 | NONE0 | ai.djl:api 0.28.0 fixed in 0.31.1 | 23.3% High Exploitation Risk | Not Applicable |
| GHSA-r7wm-3cxj-wff9 | NONE0 | com.fasterxml.jackson.core:jackson-core 2.17.2 fixed in 2.18.8, 2.21.4, 2.22.1 | — | Not Applicable |
| GHSA-72hv-8253-57qq | NONE0 | com.fasterxml.jackson.core:jackson-core 2.17.2 fixed in 2.21.1, 2.18.6 | — | Not Applicable |
| CVE-2026-33558 | NONE0 | org.apache.kafka:kafka-clients 3.7.1 fixed in 3.9.2, 4.0.1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-59949 | NONE0 | org.lz4:lz4-java 1.8.0 No fix yet | — | 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.