Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. The exposure surface is broad, with 216 detected issues and a maximum severity of 8.33; an attacker could remotely exploit the Netty request smuggling flaw (CVE-2026-42581) to bypass HTTP boundaries on the OpenSearch REST API, or trigger denial of service via libexpat parsing issues (CVE-2024-45490). Upgrading Netty and libexpat to patched versions would fully address these specific vulnerabilities. Note that some high-severity issues such as the OpenSSL delta CRL NULL pointer dereference require non-default configuration flags (X509_V_FLAG_USE_DELTAS) to be exploitable.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-42581 | HIGH8.33 | io.netty:netty-codec-http 4.1.91.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2022-23990 | HIGH7.5 | expat 2.1.0-15.amzn2.0.2 fixed in 2.1.0-15.amzn2.0.3 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-45490 | HIGH7.5 | expat 2.1.0-15.amzn2.0.2 fixed in 2.1.0-15.amzn2.0.4 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-35945 | HIGH7.5 | libnghttp2 1.41.0-1.amzn2 fixed in 1.41.0-1.amzn2.0.1 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-27113 | HIGH7.5 | libxml2 2.9.1-6.amzn2.5.8 fixed in 2.9.1-6.amzn2.5.16 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-6021 | HIGH7.5 | libxml2 2.9.1-6.amzn2.5.8 fixed in 2.9.1-6.amzn2.5.18 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28388 | HIGH7.5 | openssl-libs 1:1.0.2k-24.amzn2.0.7 fixed in 1:1.0.2k-24.amzn2.0.20 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28389 | HIGH7.5 | openssl-libs 1:1.0.2k-24.amzn2.0.7 fixed in 1:1.0.2k-24.amzn2.0.20 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28390 | HIGH7.5 | openssl-libs 1:1.0.2k-24.amzn2.0.7 fixed in 1:1.0.2k-24.amzn2.0.20 | 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-2023-3635 | HIGH7.5 | com.squareup.okio:okio 2.8.0 fixed in 3.4.0, 1.17.6 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-55163 | HIGH7.5 | io.netty:netty-codec-http2 4.1.91.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.91.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.91.Final fixed in 4.1.118.Final | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-23184 | HIGH7.5 | org.apache.cxf:cxf-core 3.5.5 fixed in 3.5.10, 3.6.5, 4.0.6 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-32007 | HIGH7.5 | org.apache.cxf:cxf-rt-rs-security-jose 3.5.5 fixed in 4.0.5, 3.6.4, 3.5.9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5072 | HIGH7.5 | org.json:json 20230227 fixed in 20231013 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-34455 | HIGH7.5 | org.xerial.snappy:snappy-java 1.1.8.4 fixed in 1.1.10.1 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-43642 | HIGH7.5 | org.xerial.snappy:snappy-java 1.1.8.4 fixed in 1.1.10.4 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-34453 | HIGH7.5 | org.xerial.snappy:snappy-java 1.1.8.4 fixed in 1.1.10.1 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-34454 | HIGH7.5 | org.xerial.snappy:snappy-java 1.1.8.4 fixed in 1.1.10.1 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-7104 | HIGH7.3 | nss 3.79.0-4.amzn2.0.1 fixed in 3.90.0-2.amzn2.0.2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-7104 | HIGH7.3 | nss-sysinit 3.79.0-4.amzn2.0.1 fixed in 3.90.0-2.amzn2.0.2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28182 | MEDIUM6.89 | libnghttp2 1.41.0-1.amzn2 fixed in 1.41.0-1.amzn2.0.5 | 84.8% Actively Exploited | 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.15.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.15.1 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.91.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-25210 | MEDIUM6.63 | expat 2.1.0-15.amzn2.0.2 fixed in 2.1.0-15.amzn2.0.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2020-35457 | MEDIUM6.63 | glib2 2.56.1-9.amzn2.0.6 fixed in 2.56.1-9.amzn2.0.8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-32643 | MEDIUM6.63 | glib2 2.56.1-9.amzn2.0.6 fixed in 2.56.1-9.amzn2.0.9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-49043 | MEDIUM6.63 | libxml2 2.9.1-6.amzn2.5.8 fixed in 2.9.1-6.amzn2.5.15 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7425 | MEDIUM6.63 | libxml2 2.9.1-6.amzn2.5.8 fixed in 2.9.1-6.amzn2.5.20 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-13601 | MEDIUM6.54 | glib2 2.56.1-9.amzn2.0.6 fixed in 2.56.1-9.amzn2.0.12 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-24928 | MEDIUM6.54 | libxml2 2.9.1-6.amzn2.5.8 fixed in 2.9.1-6.amzn2.5.16 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-25313 | MEDIUM6.5 | expat 2.1.0-15.amzn2.0.2 fixed in 2.1.0-15.amzn2.0.3 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | krb5-libs 1.15.1-55.amzn2.2.5 fixed in 1.15.1-55.amzn2.2.6 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-34462 | MEDIUM6.5 | io.netty:netty-handler 4.1.91.Final fixed in 4.1.94.Final | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-44483 | MEDIUM6.5 | org.apache.santuario:xmlsec 2.2.3 fixed in 2.3.4, 2.2.6, 3.0.3 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-29857 | MEDIUM6.5 | org.bouncycastle:bc-fips 1.0.2.3 fixed in 1.0.2.5 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-29857 | MEDIUM6.5 | org.bouncycastle:bcprov-jdk15on 1.67 fixed in 1.78 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-29857 | MEDIUM6.5 | org.bouncycastle:bcprov-jdk15on 1.70 fixed in 1.78 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-32636 | MEDIUM6.38 | glib2 2.56.1-9.amzn2.0.6 fixed in 2.56.1-9.amzn2.0.9 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-29499 | MEDIUM6.38 | glib2 2.56.1-9.amzn2.0.6 fixed in 2.56.1-9.amzn2.0.9 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | krb5-libs 1.15.1-55.amzn2.2.5 fixed in 1.15.1-55.amzn2.2.8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-27135 | MEDIUM6.38 | libnghttp2 1.41.0-1.amzn2 fixed in 1.41.0-1.amzn2.0.6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-32414 | MEDIUM6.38 | libxml2 2.9.1-6.amzn2.5.8 fixed in 2.9.1-6.amzn2.5.17 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-32415 | MEDIUM6.38 | libxml2 2.9.1-6.amzn2.5.8 fixed in 2.9.1-6.amzn2.5.17 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | openssl-libs 1:1.0.2k-24.amzn2.0.7 fixed in 1:1.0.2k-24.amzn2.0.17 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-1428 | MEDIUM6.38 | io.grpc:grpc-protobuf 1.52.1 fixed in 1.53.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42583 | MEDIUM6.38 | io.netty:netty-codec 4.1.91.Final fixed in 4.1.133.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59901 | MEDIUM6.38 | io.netty:netty-codec 4.1.91.Final fixed in 4.1.136.Final | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-58057 | MEDIUM6.38 | io.netty:netty-codec 4.1.91.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.91.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.91.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.91.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.91.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.91.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.91.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.91.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.91.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.91.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.91.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.91.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.91.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.91.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.91.Final fixed in 4.1.133.Final, 4.2.13.Final | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-34480 | MEDIUM6.38 | org.apache.logging.log4j:log4j-core 2.17.1 fixed in 2.25.4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-5588 | MEDIUM6.38 | org.bouncycastle:bcpkix-jdk15on 1.70 fixed in 1.84 | 0.4% 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.8.0 fixed in 3.3.0, 2.19.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-21634 | MEDIUM6.38 | software.amazon.ion:ion-java 1.0.2 fixed in 1.10.5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-2976 | MEDIUM6.03 | com.google.guava:guava 30.0-jre fixed in 32.0.0-android | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-2976 | MEDIUM6.03 | com.google.guava:guava 31.0.1-jre fixed in 32.0.0-android | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-2976 | MEDIUM6.03 | com.google.guava:guava 31.1-jre fixed in 32.0.0-android | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50602 | MEDIUM5.9 | expat 2.1.0-15.amzn2.0.2 fixed in 2.1.0-15.amzn2.0.5 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | krb5-libs 1.15.1-55.amzn2.2.5 fixed in 1.15.1-55.amzn2.2.7 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1 4.10-1.amzn2.0.3 fixed in 4.10-1.amzn2.0.8 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-5535 | MEDIUM5.9 | openssl-libs 1:1.0.2k-24.amzn2.0.7 fixed in 1:1.0.2k-24.amzn2.0.13 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56132 | MEDIUM5.87 | expat 2.1.0-15.amzn2.0.2 fixed in 2.1.0-15.amzn2.0.7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM5.87 | expat 2.1.0-15.amzn2.0.2 fixed in 2.1.0-15.amzn2.0.8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM5.87 | expat 2.1.0-15.amzn2.0.2 fixed in 2.1.0-15.amzn2.0.8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56407 | MEDIUM5.87 | expat 2.1.0-15.amzn2.0.2 fixed in 2.1.0-15.amzn2.0.8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-35554 | MEDIUM5.78 | org.apache.kafka:kafka-clients 3.4.0 fixed in 3.9.2, 4.0.2, 4.1.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | openssl-libs 1:1.0.2k-24.amzn2.0.7 fixed in 1:1.0.2k-24.amzn2.0.16 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | krb5-libs 1.15.1-55.amzn2.2.5 fixed in 1.15.1-55.amzn2.2.9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-45322 | MEDIUM5.52 | libxml2 2.9.1-6.amzn2.5.8 fixed in 2.9.1-6.amzn2.5.13 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-39615 | MEDIUM5.52 | libxml2 2.9.1-6.amzn2.5.8 fixed in 2.9.1-6.amzn2.5.11 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-5388 | MEDIUM5.52 | nss-softokn 3.79.0-4.amzn2 fixed in 3.90.0-6.amzn2.0.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-5388 | MEDIUM5.52 | nss-softokn-freebl 3.79.0-4.amzn2 fixed in 3.90.0-6.amzn2.0.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-59888 | MEDIUM5.52 | com.fasterxml.jackson.core:jackson-databind 2.15.1 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.91.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.91.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.91.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.91.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.3% 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.9.1-6.amzn2.5.8 fixed in 2.9.1-6.amzn2.5.14 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | openssl-libs 1:1.0.2k-24.amzn2.0.7 fixed in 1:1.0.2k-24.amzn2.0.12 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-28153 | MEDIUM5.3 | glib2 2.56.1-9.amzn2.0.6 fixed in 2.56.1-9.amzn2.0.7 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | glibc 2.26-63.amzn2 fixed in 2.26-64.amzn2.0.3 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | glibc-common 2.26-63.amzn2 fixed in 2.26-64.amzn2.0.3 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | glibc-langpack-en 2.26-63.amzn2 fixed in 2.26-64.amzn2.0.3 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | glibc-minimal-langpack 2.26-63.amzn2 fixed in 2.26-64.amzn2.0.3 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | libcrypt 2.26-63.amzn2 fixed in 2.26-64.amzn2.0.3 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-12133 | MEDIUM5.3 | libtasn1 4.10-1.amzn2.0.3 fixed in 4.10-1.amzn2.0.7 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3446 | MEDIUM5.3 | openssl-libs 1:1.0.2k-24.amzn2.0.7 fixed in 1:1.0.2k-24.amzn2.0.9 | 6.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3817 | MEDIUM5.3 | openssl-libs 1:1.0.2k-24.amzn2.0.7 fixed in 1:1.0.2k-24.amzn2.0.9 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5678 | MEDIUM5.3 | openssl-libs 1:1.0.2k-24.amzn2.0.7 fixed in 1:1.0.2k-24.amzn2.0.11 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-29025 | MEDIUM5.3 | io.netty:netty-codec-http 4.1.91.Final fixed in 4.1.108.Final | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-31141 | MEDIUM5.3 | org.apache.kafka:kafka-clients 3.4.0 fixed in 3.7.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-28170 | MEDIUM5.3 | org.glassfish:javax.el 3.0.0 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-1757 | MEDIUM5.27 | libxml2 2.9.1-6.amzn2.5.8 fixed in 2.9.1-6.amzn2.5.24 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1390 | MEDIUM5.18 | libcap 2.54-1.amzn2.0.1 fixed in 2.54-1.amzn2.0.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6766 | MEDIUM5.18 | nss 3.79.0-4.amzn2.0.1 fixed in 3.90.0-2.amzn2.0.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6767 | MEDIUM5.18 | nss 3.79.0-4.amzn2.0.1 fixed in 3.90.0-2.amzn2.0.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6772 | MEDIUM5.18 | nss 3.79.0-4.amzn2.0.1 fixed in 3.90.0-2.amzn2.0.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6766 | MEDIUM5.18 | nss-sysinit 3.79.0-4.amzn2.0.1 fixed in 3.90.0-2.amzn2.0.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6767 | MEDIUM5.18 | nss-sysinit 3.79.0-4.amzn2.0.1 fixed in 3.90.0-2.amzn2.0.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6772 | MEDIUM5.18 | nss-sysinit 3.79.0-4.amzn2.0.1 fixed in 3.90.0-2.amzn2.0.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | krb5-libs 1.15.1-55.amzn2.2.5 fixed in 1.15.1-55.amzn2.2.7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | krb5-libs 1.15.1-55.amzn2.2.5 fixed in 1.15.1-55.amzn2.2.9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0990 | MEDIUM5.02 | libxml2 2.9.1-6.amzn2.5.8 fixed in 2.9.1-6.amzn2.5.22 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | openssl-libs 1:1.0.2k-24.amzn2.0.7 fixed in 1:1.0.2k-24.amzn2.0.17 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | openssl-libs 1:1.0.2k-24.amzn2.0.7 fixed in 1:1.0.2k-24.amzn2.0.17 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | openssl-libs 1:1.0.2k-24.amzn2.0.7 fixed in 1:1.0.2k-24.amzn2.0.21 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-34477 | MEDIUM5.02 | org.apache.logging.log4j:log4j-core 2.17.1 fixed in 2.25.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-30171 | MEDIUM5.02 | org.bouncycastle:bcprov-jdk15on 1.67 fixed in 1.78 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-30171 | MEDIUM5.02 | org.bouncycastle:bcprov-jdk15on 1.70 fixed in 1.78 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | openssl-libs 1:1.0.2k-24.amzn2.0.7 fixed in 1:1.0.2k-24.amzn2.0.21 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-59921 | MEDIUM4.84 | io.netty:netty-codec-http 4.1.91.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2007-4559 | MEDIUM4.69 | python-libs 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.12 | 27.1% High Exploitation Risk | Post-Exploit |
| CVE-2020-21047 | MEDIUM4.67 | elfutils-libelf 0.176-2.amzn2 fixed in 0.176-2.amzn2.0.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-33294 | MEDIUM4.67 | elfutils-libelf 0.176-2.amzn2 fixed in 0.176-2.amzn2.0.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-32611 | MEDIUM4.67 | glib2 2.56.1-9.amzn2.0.6 fixed in 2.56.1-9.amzn2.0.9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-32665 | MEDIUM4.67 | glib2 2.56.1-9.amzn2.0.6 fixed in 2.56.1-9.amzn2.0.9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | glibc 2.26-63.amzn2 fixed in 2.26-64.amzn2.0.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | glibc-common 2.26-63.amzn2 fixed in 2.26-64.amzn2.0.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | glibc-langpack-en 2.26-63.amzn2 fixed in 2.26-64.amzn2.0.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | glibc-minimal-langpack 2.26-63.amzn2 fixed in 2.26-64.amzn2.0.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libcrypt 2.26-63.amzn2 fixed in 2.26-64.amzn2.0.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | openssl-libs 1:1.0.2k-24.amzn2.0.7 fixed in 1:1.0.2k-24.amzn2.0.21 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-47535 | MEDIUM4.67 | io.netty:netty-common 4.1.91.Final fixed in 4.1.115.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-25193 | MEDIUM4.67 | io.netty:netty-common 4.1.91.Final fixed in 4.1.118.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-25710 | MEDIUM4.67 | org.apache.commons:commons-compress 1.21 fixed in 1.26.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26308 | MEDIUM4.67 | org.apache.commons:commons-compress 1.21 fixed in 1.26.0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-42503 | MEDIUM4.67 | org.apache.commons:commons-compress 1.23.0 fixed in 1.24.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-25710 | MEDIUM4.67 | org.apache.commons:commons-compress 1.23.0 fixed in 1.26.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26308 | MEDIUM4.67 | org.apache.commons:commons-compress 1.23.0 fixed in 1.26.0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-45146 | MEDIUM4.67 | org.bouncycastle:bc-fips 1.0.2.3 fixed in 1.0.2.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-33202 | MEDIUM4.67 | org.bouncycastle:bcprov-ext-jdk15on 1.70 fixed in 1.73 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-33202 | MEDIUM4.67 | org.bouncycastle:bcprov-jdk15on 1.67 fixed in 1.70 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-7598 | MEDIUM4.64 | libssh2 1.4.3-12.amzn2.2.4 fixed in 1.4.3-12.amzn2.2.7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-38545 | MEDIUM4.58 | curl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.4 | 78.5% Actively Exploited | Post-Exploit |
| CVE-2023-38545 | MEDIUM4.58 | libcurl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.4 | 78.5% Actively Exploited | Post-Exploit |
| CVE-2023-28319 | MEDIUM4.5 | curl 8.0.1-1.amzn2.0.1 fixed in 8.2.1-1.amzn2.0.2 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28319 | MEDIUM4.5 | libcurl 8.0.1-1.amzn2.0.1 fixed in 8.2.1-1.amzn2.0.2 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-7592 | MEDIUM4.5 | python 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.11 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-7592 | MEDIUM4.5 | python-libs 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.11 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5344 | MEDIUM4.5 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.1882-1.amzn2.0.2 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5344 | MEDIUM4.5 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.1882-1.amzn2.0.2 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4046 | MEDIUM4.5 | glibc 2.26-63.amzn2 fixed in 2.26-64.amzn2.0.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-common 2.26-63.amzn2 fixed in 2.26-64.amzn2.0.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-langpack-en 2.26-63.amzn2 fixed in 2.26-64.amzn2.0.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-minimal-langpack 2.26-63.amzn2 fixed in 2.26-64.amzn2.0.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libcrypt 2.26-63.amzn2 fixed in 2.26-64.amzn2.0.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | openssl-libs 1:1.0.2k-24.amzn2.0.7 fixed in 1:1.0.2k-24.amzn2.0.21 | 1.0% 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.15.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.15.1 fixed in 3.1.4, 2.18.9, 2.21.5, 2.22.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-51074 | MEDIUM4.5 | com.jayway.jsonpath:json-path 2.4.0 fixed in 2.9.0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-50020 | MEDIUM4.5 | io.netty:netty-codec-http 4.1.91.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.91.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.91.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.91.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 1.0.2.3 fixed in 1.0.2.6, 2.0.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-8916 | MEDIUM4.5 | org.bouncycastle:bcpkix-jdk15on 1.70 fixed in 1.79 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-33201 | MEDIUM4.5 | org.bouncycastle:bcprov-ext-jdk15on 1.70 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-33201 | MEDIUM4.5 | org.bouncycastle:bcprov-jdk15on 1.67 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-34447 | MEDIUM4.5 | org.bouncycastle:bcprov-jdk15on 1.67 fixed in 1.78 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-33201 | MEDIUM4.5 | org.bouncycastle:bcprov-jdk15on 1.70 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-34447 | MEDIUM4.5 | org.bouncycastle:bcprov-jdk15on 1.70 fixed in 1.78 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-47162 | MEDIUM4.49 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-47162 | MEDIUM4.49 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-7104 | MEDIUM4.38 | nss-tools 3.79.0-4.amzn2.0.1 fixed in 3.90.0-2.amzn2.0.2 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-47554 | MEDIUM4.3 | commons-io:commons-io 2.11.0 fixed in 2.14.0 | 1.2% Low-Moderate Risk | 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.15.1-55.amzn2.2.5 fixed in 1.15.1-55.amzn2.2.10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34982 | MEDIUM4.18 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.5 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-34982 | MEDIUM4.18 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.5 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | curl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.12 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.12 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | MEDIUM4.13 | python 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.19 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | MEDIUM4.13 | python-libs 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.19 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-2961 | MEDIUM4.12 | glibc 2.26-63.amzn2 fixed in 2.26-64.amzn2.0.1 | 88.3% Actively Exploited | Post-Exploit |
| CVE-2024-2961 | MEDIUM4.12 | glibc-common 2.26-63.amzn2 fixed in 2.26-64.amzn2.0.1 | 88.3% Actively Exploited | Post-Exploit |
| CVE-2024-2961 | MEDIUM4.12 | glibc-langpack-en 2.26-63.amzn2 fixed in 2.26-64.amzn2.0.1 | 88.3% Actively Exploited | Post-Exploit |
| CVE-2024-2961 | MEDIUM4.12 | glibc-minimal-langpack 2.26-63.amzn2 fixed in 2.26-64.amzn2.0.1 | 88.3% Actively Exploited | Post-Exploit |
| CVE-2024-2961 | MEDIUM4.12 | libcrypt 2.26-63.amzn2 fixed in 2.26-64.amzn2.0.1 | 88.3% Actively Exploited | Post-Exploit |
| CVE-2025-0938 | MEDIUM4.08 | python 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.11 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0938 | MEDIUM4.08 | python-libs 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.11 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-4039 | MEDIUM4.08 | libgcc 7.3.1-15.amzn2 fixed in 7.3.1-17.amzn2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libstdc++ 7.3.1-15.amzn2 fixed in 7.3.1-17.amzn2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-48795 | MEDIUM4.08 | org.apache.cxf:cxf-core 3.5.5 fixed in 3.5.11, 3.6.6, 4.0.7, 4.1.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-68161 | MEDIUM4.08 | org.apache.logging.log4j:log4j-core 2.17.1 fixed in 2.25.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4 | openssl-libs 1:1.0.2k-24.amzn2.0.7 fixed in 1:1.0.2k-24.amzn2.0.17 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | openssl-libs 1:1.0.2k-24.amzn2.0.7 fixed in 1:1.0.2k-24.amzn2.0.15 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4733 | LOW3.98 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.1882-1.amzn2.0.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-4734 | LOW3.98 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.1882-1.amzn2.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4735 | LOW3.98 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.1882-1.amzn2.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4738 | LOW3.98 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.1882-1.amzn2.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4750 | LOW3.98 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.1882-1.amzn2.0.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-4751 | LOW3.98 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.1882-1.amzn2.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4752 | LOW3.98 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.1882-1.amzn2.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4781 | LOW3.98 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.1882-1.amzn2.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-52858 | LOW3.98 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-52860 | LOW3.98 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55693 | LOW3.98 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.8 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-55895 | LOW3.98 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-57456 | LOW3.98 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.8 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-22667 | LOW3.98 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1215 | LOW3.98 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-5535 | LOW3.98 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.1882-1.amzn2.0.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-4733 | LOW3.98 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.1882-1.amzn2.0.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-4734 | LOW3.98 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.1882-1.amzn2.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4735 | LOW3.98 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.1882-1.amzn2.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4738 | LOW3.98 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.1882-1.amzn2.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4750 | LOW3.98 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.1882-1.amzn2.0.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-4751 | LOW3.98 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.1882-1.amzn2.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4752 | LOW3.98 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.1882-1.amzn2.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4781 | LOW3.98 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.1882-1.amzn2.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-52858 | LOW3.98 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-52860 | LOW3.98 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55693 | LOW3.98 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.8 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-55895 | LOW3.98 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-57456 | LOW3.98 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.8 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-22667 | LOW3.98 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1215 | LOW3.98 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-5535 | LOW3.98 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.1882-1.amzn2.0.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-46218 | LOW3.9 | curl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.6 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-9681 | LOW3.9 | curl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.8 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-46218 | LOW3.9 | libcurl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.6 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-9681 | LOW3.9 | libcurl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.8 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2020-22218 | LOW3.82 | libssh2 1.4.3-12.amzn2.2.4 fixed in 1.4.3-12.amzn2.2.6 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-58050 | LOW3.82 | libssh2 1.4.3-12.amzn2.2.4 fixed in 1.4.3-12.amzn2.2.8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-8194 | LOW3.82 | python 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.14 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3644 | LOW3.82 | python 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.17 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW3.82 | python 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.17 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-8194 | LOW3.82 | python-libs 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.14 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3644 | LOW3.82 | python-libs 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.17 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW3.82 | python-libs 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.17 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-27817 | LOW3.79 | org.apache.kafka:kafka-clients 3.4.0 fixed in 3.9.1 | 64.7% Actively Exploited | Post-Exploit |
| CVE-2026-41411 | LOW3.72 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.6 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-41411 | LOW3.72 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.6 | 0.5% 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.4 fixed in 3.18.0 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-48924 | LOW3.7 | org.apache.commons:commons-lang3 3.9 fixed in 3.18.0 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6135 | LOW3.65 | nss-softokn 3.79.0-4.amzn2 fixed in 3.90.0-6.amzn2.0.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-6135 | LOW3.65 | nss-softokn-freebl 3.79.0-4.amzn2 fixed in 3.90.0-6.amzn2.0.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4156 | LOW3.62 | gawk 4.0.2-4.amzn2.1.2 fixed in 4.0.2-4.amzn2.1.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4786 | LOW3.62 | python 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.19 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-4786 | LOW3.62 | python-libs 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.19 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-6965 | LOW3.61 | sqlite 3.7.17-8.amzn2.1.2 fixed in 3.7.17-8.amzn2.1.3 | 74.4% Actively Exploited | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gnupg2 2.0.22-5.amzn2.0.5 fixed in 2.0.22-5.amzn2.0.6 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8058 | LOW3.57 | glibc 2.26-63.amzn2 fixed in 2.26-64.amzn2.0.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | glibc-common 2.26-63.amzn2 fixed in 2.26-64.amzn2.0.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | glibc-langpack-en 2.26-63.amzn2 fixed in 2.26-64.amzn2.0.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | glibc-minimal-langpack 2.26-63.amzn2 fixed in 2.26-64.amzn2.0.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | libcrypt 2.26-63.amzn2 fixed in 2.26-64.amzn2.0.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-28321 | LOW3.54 | curl 8.0.1-1.amzn2.0.1 fixed in 8.2.1-1.amzn2.0.2 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28321 | LOW3.54 | libcurl 8.0.1-1.amzn2.0.1 fixed in 8.2.1-1.amzn2.0.2 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-48566 | LOW3.54 | python 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.8 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-48566 | LOW3.54 | python-libs 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.8 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-56171 | LOW3.53 | libxml2 2.9.1-6.amzn2.5.8 fixed in 2.9.1-6.amzn2.5.16 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-48565 | LOW3.53 | python 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.7 | 4.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-48565 | LOW3.53 | python-libs 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.7 | 4.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-45853 | LOW3.53 | zlib 1.2.7-19.amzn2.0.2 fixed in 1.2.7-19.amzn2.0.3 | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-38039 | LOW3.51 | curl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.1 | 62.2% Actively Exploited | Post-Exploit |
| CVE-2023-38039 | LOW3.51 | libcurl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.1 | 62.2% Actively Exploited | Post-Exploit |
| CVE-2023-44487 | LOW3.51 | libnghttp2 1.41.0-1.amzn2 fixed in 1.41.0-1.amzn2.0.4 | 100.0% Actively Exploited | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | curl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.12 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | libcurl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.12 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-6923 | LOW3.47 | python 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.11 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2024-6923 | LOW3.47 | python-libs 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.11 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-11563 | LOW3.31 | curl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | curl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.12 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-11563 | LOW3.31 | libcurl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.12 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-58051 | LOW3.31 | libssh2 1.4.3-12.amzn2.2.4 fixed in 1.4.3-12.amzn2.2.8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW3.31 | python 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.21 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW3.31 | python-libs 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.21 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-37371 | LOW3.28 | krb5-libs 1.15.1-55.amzn2.2.5 fixed in 1.15.1-55.amzn2.2.8 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2025-49796 | LOW3.28 | libxml2 2.9.1-6.amzn2.5.8 fixed in 2.9.1-6.amzn2.5.19 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2004 | LOW3.18 | curl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.7 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2025-9086 | LOW3.18 | curl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.10 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-46219 | LOW3.18 | curl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.5 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2004 | LOW3.18 | libcurl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.7 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2025-9086 | LOW3.18 | libcurl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.10 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-46219 | LOW3.18 | libcurl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.5 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27043 | LOW3.18 | python 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.9 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27043 | LOW3.18 | python-libs 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.9 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-48734 | LOW3.17 | commons-beanutils:commons-beanutils 1.9.4 fixed in 1.11.0 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-0450 | LOW3.16 | python 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-0450 | LOW3.16 | python-libs 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-0989 | LOW3.15 | libxml2 2.9.1-6.amzn2.5.8 fixed in 2.9.1-6.amzn2.5.23 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6766 | LOW3.11 | nss-tools 3.79.0-4.amzn2.0.1 fixed in 3.90.0-2.amzn2.0.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6767 | LOW3.11 | nss-tools 3.79.0-4.amzn2.0.1 fixed in 3.90.0-2.amzn2.0.3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6772 | LOW3.11 | nss-tools 3.79.0-4.amzn2.0.1 fixed in 3.90.0-2.amzn2.0.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.11 | python 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.20 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.11 | python-libs 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.20 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-2398 | LOW3.1 | curl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.7 | 36.1% High Exploitation Risk | Post-Exploit |
| CVE-2024-2398 | LOW3.1 | libcurl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.7 | 36.1% High Exploitation Risk | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | curl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.12 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.12 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14087 | LOW3 | glib2 2.56.1-9.amzn2.0.6 fixed in 2.56.1-9.amzn2.0.13 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-6653 | LOW3 | libxml2 2.9.1-6.amzn2.5.8 fixed in 2.9.1-6.amzn2.5.25 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl-libs 1:1.0.2k-24.amzn2.0.7 fixed in 1:1.0.2k-24.amzn2.0.21 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2007-4559 | LOW2.81 | python 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.12 | 27.1% High Exploitation Risk | Post-Exploit |
| CVE-2025-6075 | LOW2.8 | python 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.16 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-6075 | LOW2.8 | python-libs 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.16 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-4641 | LOW2.8 | shadow-utils 2:4.1.5.1-24.amzn2.0.2 fixed in 2:4.1.5.1-24.amzn2.0.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-3236 | LOW2.8 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.1882-1.amzn2.0.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-46246 | LOW2.8 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2081-1.amzn2.0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-24014 | LOW2.8 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-5441 | LOW2.8 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.1882-1.amzn2.0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-3236 | LOW2.8 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.1882-1.amzn2.0.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-46246 | LOW2.8 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2081-1.amzn2.0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-24014 | LOW2.8 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-5441 | LOW2.8 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.1882-1.amzn2.0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-2602 | LOW2.8 | libcap 2.54-1.amzn2.0.1 fixed in 2.54-1.amzn2.0.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-36084 | LOW2.8 | libsepol 2.5-8.1.amzn2.0.2 fixed in 2.5-10.amzn2.0.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-36085 | LOW2.8 | libsepol 2.5-8.1.amzn2.0.2 fixed in 2.5-10.amzn2.0.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-36086 | LOW2.8 | libsepol 2.5-8.1.amzn2.0.2 fixed in 2.5-10.amzn2.0.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-36087 | LOW2.8 | libsepol 2.5-8.1.amzn2.0.2 fixed in 2.5-10.amzn2.0.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-8732 | LOW2.8 | libxml2 2.9.1-6.amzn2.5.8 fixed in 2.9.1-6.amzn2.5.21 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2020-8908 | LOW2.8 | com.google.guava:guava 30.0-jre fixed in 32.0.0-android | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2020-8908 | LOW2.8 | com.google.guava:guava 31.0.1-jre fixed in 32.0.0-android | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2020-8908 | LOW2.8 | com.google.guava:guava 31.1-jre fixed in 32.0.0-android | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | LOW2.78 | glib2 2.56.1-9.amzn2.0.6 fixed in 2.56.1-9.amzn2.0.14 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-49794 | LOW2.78 | libxml2 2.9.1-6.amzn2.5.8 fixed in 2.9.1-6.amzn2.5.19 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-42584 | LOW2.78 | io.netty:netty-codec-http 4.1.91.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2021-43618 | LOW2.7 | gmp 1:6.0.0-15.amzn2.0.2 fixed in 1:6.0.0-15.amzn2.0.3 | 3.4% Low-Moderate Risk | Post-Exploit |
| CVE-2023-40217 | LOW2.7 | python 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.12 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-12084 | LOW2.7 | python 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.15 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-40217 | LOW2.7 | python-libs 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.12 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-12084 | LOW2.7 | python-libs 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.15 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-47167 | LOW2.7 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-47167 | LOW2.7 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0992 | LOW2.46 | libxml2 2.9.1-6.amzn2.5.8 fixed in 2.9.1-6.amzn2.5.22 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14017 | LOW2.45 | curl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.12 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.12 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | LOW2.45 | python 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.16 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.45 | python 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.16 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | LOW2.45 | python-libs 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.16 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.45 | python-libs 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.16 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.12 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.12 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-48706 | LOW2.4 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-48706 | LOW2.4 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11468 | LOW2.29 | python 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.16 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0865 | LOW2.29 | python 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.16 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-11468 | LOW2.29 | python-libs 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.16 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0865 | LOW2.29 | python-libs 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.16 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-43802 | LOW2.29 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-43802 | LOW2.29 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-29768 | LOW2.24 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-29768 | LOW2.24 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-38546 | LOW2.22 | curl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.4 | 6.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28322 | LOW2.22 | curl 8.0.1-1.amzn2.0.1 fixed in 8.2.1-1.amzn2.0.2 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-38546 | LOW2.22 | libcurl 8.0.1-1.amzn2.0.1 fixed in 8.3.0-1.amzn2.0.4 | 6.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28322 | LOW2.22 | libcurl 8.0.1-1.amzn2.0.1 fixed in 8.2.1-1.amzn2.0.2 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-6069 | LOW2.19 | python 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.13 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-6069 | LOW2.19 | python-libs 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.13 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-48231 | LOW2.19 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2120-1.amzn2.0.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48232 | LOW2.19 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2120-1.amzn2.0.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48233 | LOW2.19 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2120-1.amzn2.0.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48234 | LOW2.19 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2120-1.amzn2.0.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48235 | LOW2.19 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2120-1.amzn2.0.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48236 | LOW2.19 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2120-1.amzn2.0.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48237 | LOW2.19 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2120-1.amzn2.0.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48231 | LOW2.19 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2120-1.amzn2.0.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48232 | LOW2.19 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2120-1.amzn2.0.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48233 | LOW2.19 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2120-1.amzn2.0.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48234 | LOW2.19 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2120-1.amzn2.0.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48235 | LOW2.19 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2120-1.amzn2.0.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48236 | LOW2.19 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2120-1.amzn2.0.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48237 | LOW2.19 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2120-1.amzn2.0.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-26603 | LOW2.14 | vim-data 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-26603 | LOW2.14 | vim-minimal 2:9.0.1592-1.amzn2.0.1 fixed in 2:9.0.2153-1.amzn2.0.4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-11168 | LOW1.89 | python 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.11 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-11168 | LOW1.89 | python-libs 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.11 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2020-19909 | LOW1.68 | curl 8.0.1-1.amzn2.0.1 fixed in 8.2.1-1.amzn2.0.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2020-19909 | LOW1.68 | libcurl 8.0.1-1.amzn2.0.1 fixed in 8.2.1-1.amzn2.0.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW1.68 | python 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.18 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4519 | LOW1.68 | python 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.18 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.18 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW1.68 | python-libs 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.18 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4519 | LOW1.68 | python-libs 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.18 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python-libs 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.18 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-39804 | LOW1.68 | tar 2:1.26-35.amzn2.0.2 fixed in 2:1.26-35.amzn2.0.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-5642 | LOW1.38 | python 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.10 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-5642 | LOW1.38 | python-libs 2.7.18-1.amzn2.0.6 fixed in 2.7.18-1.amzn2.0.10 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2015-1197 | LOW1.14 | cpio 2.12-11.amzn2 fixed in 2.12-11.amzn2.0.1 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2023-37920 | NONE0 | ca-certificates 2021.2.50-72.amzn2.0.7 fixed in 2021.2.50-72.amzn2.0.8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-39689 | NONE0 | ca-certificates 2021.2.50-72.amzn2.0.7 fixed in 2023.2.68-1.amzn2.0.1 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2020-19185 | NONE0 | ncurses 6.0-8.20170212.amzn2.1.5 fixed in 6.0-8.20170212.amzn2.1.6 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19186 | NONE0 | ncurses 6.0-8.20170212.amzn2.1.5 fixed in 6.0-8.20170212.amzn2.1.6 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2020-19187 | NONE0 | ncurses 6.0-8.20170212.amzn2.1.5 fixed in 6.0-8.20170212.amzn2.1.6 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19188 | NONE0 | ncurses 6.0-8.20170212.amzn2.1.5 fixed in 6.0-8.20170212.amzn2.1.6 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19189 | NONE0 | ncurses 6.0-8.20170212.amzn2.1.5 fixed in 6.0-8.20170212.amzn2.1.6 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2020-19190 | NONE0 | ncurses 6.0-8.20170212.amzn2.1.5 fixed in 6.0-8.20170212.amzn2.1.6 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses 6.0-8.20170212.amzn2.1.5 fixed in 6.0-8.20170212.amzn2.1.7 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2020-19185 | NONE0 | ncurses-base 6.0-8.20170212.amzn2.1.5 fixed in 6.0-8.20170212.amzn2.1.6 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19186 | NONE0 | ncurses-base 6.0-8.20170212.amzn2.1.5 fixed in 6.0-8.20170212.amzn2.1.6 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2020-19187 | NONE0 | ncurses-base 6.0-8.20170212.amzn2.1.5 fixed in 6.0-8.20170212.amzn2.1.6 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19188 | NONE0 | ncurses-base 6.0-8.20170212.amzn2.1.5 fixed in 6.0-8.20170212.amzn2.1.6 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19189 | NONE0 | ncurses-base 6.0-8.20170212.amzn2.1.5 fixed in 6.0-8.20170212.amzn2.1.6 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2020-19190 | NONE0 | ncurses-base 6.0-8.20170212.amzn2.1.5 fixed in 6.0-8.20170212.amzn2.1.6 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.0-8.20170212.amzn2.1.5 fixed in 6.0-8.20170212.amzn2.1.7 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2020-19185 | NONE0 | ncurses-libs 6.0-8.20170212.amzn2.1.5 fixed in 6.0-8.20170212.amzn2.1.6 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19186 | NONE0 | ncurses-libs 6.0-8.20170212.amzn2.1.5 fixed in 6.0-8.20170212.amzn2.1.6 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2020-19187 | NONE0 | ncurses-libs 6.0-8.20170212.amzn2.1.5 fixed in 6.0-8.20170212.amzn2.1.6 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19188 | NONE0 | ncurses-libs 6.0-8.20170212.amzn2.1.5 fixed in 6.0-8.20170212.amzn2.1.6 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19189 | NONE0 | ncurses-libs 6.0-8.20170212.amzn2.1.5 fixed in 6.0-8.20170212.amzn2.1.6 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2020-19190 | NONE0 | ncurses-libs 6.0-8.20170212.amzn2.1.5 fixed in 6.0-8.20170212.amzn2.1.6 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-libs 6.0-8.20170212.amzn2.1.5 fixed in 6.0-8.20170212.amzn2.1.7 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2019-17595 | NONE0 | ncurses 6.0-8.20170212.amzn2.1.5 fixed in 6.0-8.20170212.amzn2.1.6 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-17595 | NONE0 | ncurses-base 6.0-8.20170212.amzn2.1.5 fixed in 6.0-8.20170212.amzn2.1.6 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-17595 | NONE0 | ncurses-libs 6.0-8.20170212.amzn2.1.5 fixed in 6.0-8.20170212.amzn2.1.6 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-17594 | NONE0 | ncurses 6.0-8.20170212.amzn2.1.5 fixed in 6.0-8.20170212.amzn2.1.6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-17594 | NONE0 | ncurses-base 6.0-8.20170212.amzn2.1.5 fixed in 6.0-8.20170212.amzn2.1.6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-17594 | NONE0 | ncurses-libs 6.0-8.20170212.amzn2.1.5 fixed in 6.0-8.20170212.amzn2.1.6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-48924 | NONE0 | commons-lang:commons-lang 2.4 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-48924 | NONE0 | commons-lang:commons-lang 2.6 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid 2.30.2-2.amzn2.0.11 fixed in 2.30.2-2.amzn2.0.14 | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount 2.30.2-2.amzn2.0.11 fixed in 2.30.2-2.amzn2.0.14 | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libuuid 2.30.2-2.amzn2.0.11 fixed in 2.30.2-2.amzn2.0.14 | — | Not Applicable |
| CVE-2024-37902 | NONE0 | ai.djl:api 0.19.0 fixed in 0.28.0 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-0851 | NONE0 | ai.djl:api 0.19.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.15.1 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.15.1 fixed in 2.21.1, 2.18.6 | — | Not Applicable |
| GHSA-xpw8-rcwv-8f8p | NONE0 | io.netty:netty-codec-http2 4.1.91.Final fixed in 4.1.100.Final | — | Not Applicable |
| CVE-2026-33558 | NONE0 | org.apache.kafka:kafka-clients 3.4.0 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 |
| GHSA-6g3j-p5g6-992f | NONE0 | org.opensearch:opensearch 2.8.0 fixed in 1.3.14, 2.11.1 | — | 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.