Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker could exploit CVE-2026-42581 to smuggle HTTP requests through the OpenSearch REST API, potentially bypassing request validation or poisoning downstream proxies. CVE-2026-34183 could allow a remote peer to exhaust memory via QUIC PATH_CHALLENGE frames, leading to denial of service. Post-exploit-only findings are low-severity (max 4.06), so the primary risk is from the exposed surface. Upgrading to patched versions of Netty and OpenSSL is strongly advised before any production use.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-42581 | HIGH8.33 | io.netty:netty-codec-http 4.1.124.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-42581 | HIGH8.33 | io.netty:netty-codec-http 4.1.125.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-34183 | HIGH7.5 | openssl-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.5 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34183 | HIGH7.5 | openssl-libs 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.5 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | glib2 2.82.2-766.amzn2023 fixed in 2.82.2-770.amzn2023 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | glib2 2.82.2-766.amzn2023 fixed in 2.82.2-770.amzn2023 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | glib2 2.82.2-766.amzn2023 fixed in 2.82.2-770.amzn2023 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | glib2 2.82.2-766.amzn2023 fixed in 2.82.2-770.amzn2023 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | openssl-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.4 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | openssl-libs 1:3.2.2-1.amzn2023.0.2 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.16.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.16.2 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.18.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.18.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.124.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.125.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-54920 | MEDIUM6.7 | org.apache.spark:spark-core_2.13 3.5.4 fixed in 4.0.1, 3.5.7 | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-25210 | MEDIUM6.63 | expat 2.6.3-1.amzn2023.0.3 fixed in 2.6.3-1.amzn2023.0.4 | 0.2% 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-2025-13601 | MEDIUM6.54 | glib2 2.82.2-766.amzn2023 fixed in 2.82.2-767.amzn2023 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | glib2 2.82.2-766.amzn2023 fixed in 2.82.2-770.amzn2023 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | glib2 2.82.2-766.amzn2023 fixed in 2.82.2-770.amzn2023 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | krb5-libs 1.21.3-6.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-6.amzn2023.0.1 fixed in 1.21.3-7.amzn2023.0.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-58183 | MEDIUM6.38 | libcap 2.73-1.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61728 | MEDIUM6.38 | libcap 2.73-1.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61729 | MEDIUM6.38 | libcap 2.73-1.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33811 | MEDIUM6.38 | libcap 2.73-1.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM6.38 | libcap 2.73-1.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39820 | MEDIUM6.38 | libcap 2.73-1.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42499 | MEDIUM6.38 | libcap 2.73-1.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.2 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-69421 | MEDIUM6.38 | openssl-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.2.2-1.amzn2023.0.5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | openssl-libs 1:3.2.2-1.amzn2023.0.2 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.124.Final fixed in 4.1.133.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59901 | MEDIUM6.38 | io.netty:netty-codec 4.1.124.Final fixed in 4.1.136.Final | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-58057 | MEDIUM6.38 | io.netty:netty-codec 4.1.124.Final fixed in 4.1.125.Final | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42583 | MEDIUM6.38 | io.netty:netty-codec 4.1.125.Final fixed in 4.1.133.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59901 | MEDIUM6.38 | io.netty:netty-codec 4.1.125.Final fixed in 4.1.136.Final | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-33870 | MEDIUM6.38 | io.netty:netty-codec-http 4.1.124.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.124.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.124.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.124.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.124.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.124.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.124.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.124.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.124.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.125.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.125.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.125.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.125.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.125.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.125.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.125.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.125.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42587 | MEDIUM6.38 | io.netty:netty-codec-http2 4.1.124.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.124.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.125.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.125.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.124.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.124.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.125.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.125.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.125.Final fixed in 4.1.133.Final, 4.2.13.Final | 1.0% 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-2025-66566 | MEDIUM6.38 | org.lz4:lz4-java 1.8.0 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | openssl-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.2.2-1.amzn2023.0.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | openssl-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | openssl-libs 1:3.2.2-1.amzn2023.0.2 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.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-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-2026-28388 | MEDIUM6 | openssl-libs 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.4 | 1.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33871 | MEDIUM6 | io.netty:netty-codec-http2 4.1.124.Final fixed in 4.1.132.Final, 4.2.11.Final | 1.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33871 | MEDIUM6 | io.netty:netty-codec-http2 4.1.125.Final fixed in 4.1.132.Final, 4.2.11.Final | 1.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1 4.19.0-1.amzn2023.0.5 fixed in 4.19.0-1.amzn2023.0.6 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.9 | openssl-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.4 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.9 | openssl-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.9 | openssl-libs 1:3.2.2-1.amzn2023.0.2 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.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56132 | MEDIUM5.87 | expat 2.6.3-1.amzn2023.0.3 fixed in 2.6.3-1.amzn2023.0.5 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM5.87 | expat 2.6.3-1.amzn2023.0.3 fixed in 2.6.3-1.amzn2023.0.6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM5.87 | expat 2.6.3-1.amzn2023.0.3 fixed in 2.6.3-1.amzn2023.0.6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56407 | MEDIUM5.87 | expat 2.6.3-1.amzn2023.0.3 fixed in 2.6.3-1.amzn2023.0.6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-35554 | MEDIUM5.78 | org.apache.kafka:kafka-clients 4.0.0 fixed in 3.9.2, 4.0.2, 4.1.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-61727 | MEDIUM5.52 | libcap 2.73-1.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-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2673 | MEDIUM5.52 | openssl-libs 1:3.2.2-1.amzn2023.0.2 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.2 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.18.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.124.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.124.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.124.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.125.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.125.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.125.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.124.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.125.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-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-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | openssl-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM5.35 | openssl-libs 1:3.2.2-1.amzn2023.0.2 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.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1757 | MEDIUM5.27 | libxml2 2.10.4-1.amzn2023.0.13 fixed in 2.10.4-1.amzn2023.0.18 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0990 | MEDIUM5.02 | libxml2 2.10.4-1.amzn2023.0.13 fixed in 2.10.4-1.amzn2023.0.16 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-15468 | MEDIUM5.02 | openssl-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.2.2-1.amzn2023.0.5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-66199 | MEDIUM5.02 | openssl-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.2.2-1.amzn2023.0.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | openssl-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.2.2-1.amzn2023.0.5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | openssl-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.2.2-1.amzn2023.0.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.02 | openssl-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | openssl-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | openssl-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-15468 | MEDIUM5.02 | openssl-libs 1:3.2.2-1.amzn2023.0.2 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.2.2-1.amzn2023.0.2 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.2.2-1.amzn2023.0.2 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.2.2-1.amzn2023.0.2 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.2.2-1.amzn2023.0.2 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.2.2-1.amzn2023.0.2 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.2.2-1.amzn2023.0.2 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-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.5 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | openssl-libs 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.5 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-59921 | MEDIUM4.84 | io.netty:netty-codec-http 4.1.124.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.125.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM4.67 | openssl-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.2.2-1.amzn2023.0.5 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | openssl-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM4.67 | openssl-libs 1:3.2.2-1.amzn2023.0.2 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.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-27142 | MEDIUM4.59 | libcap 2.73-1.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39823 | MEDIUM4.59 | libcap 2.73-1.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc 2.34-231.amzn2023.0.1 fixed in 2.34-231.amzn2023.0.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-common 2.34-231.amzn2023.0.1 fixed in 2.34-231.amzn2023.0.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-minimal-langpack 2.34-231.amzn2023.0.1 fixed in 2.34-231.amzn2023.0.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-47912 | MEDIUM4.5 | libcap 2.73-1.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58185 | MEDIUM4.5 | libcap 2.73-1.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58186 | MEDIUM4.5 | libcap 2.73-1.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58187 | MEDIUM4.5 | libcap 2.73-1.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58188 | MEDIUM4.5 | libcap 2.73-1.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58189 | MEDIUM4.5 | libcap 2.73-1.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61723 | MEDIUM4.5 | libcap 2.73-1.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61724 | MEDIUM4.5 | libcap 2.73-1.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61725 | MEDIUM4.5 | libcap 2.73-1.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61730 | MEDIUM4.5 | libcap 2.73-1.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | openssl-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.5 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | openssl-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | openssl-libs 1:3.2.2-1.amzn2023.0.2 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.2.2-1.amzn2023.0.2 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.16.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.16.2 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.18.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.18.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.124.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.124.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.125.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.125.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.124.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.124.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.125.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.125.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | krb5-libs 1.21.3-6.amzn2023.0.1 fixed in 1.21.3-8.amzn2023.0.1 | 0.3% Theoretical Threat | Directly Exposed |
| 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-15467 | MEDIUM4.06 | openssl-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.2.2-1.amzn2023.0.4 | 47.6% High Exploitation Risk | Post-Exploit |
| CVE-2025-15467 | MEDIUM4.06 | openssl-libs 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.2.2-1.amzn2023.0.4 | 47.6% High Exploitation Risk | Post-Exploit |
| CVE-2025-68160 | MEDIUM4 | openssl-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.2.2-1.amzn2023.0.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4 | openssl-libs 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.2.2-1.amzn2023.0.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-24882 | LOW3.98 | gnupg2-minimal 2.3.7-1.amzn2023.0.5 fixed in 2.3.7-1.amzn2023.0.7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4786 | LOW3.62 | python3 3.9.23-1.amzn2023.0.3 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.5 fixed in 2.3.7-1.amzn2023.0.6 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-11053 | LOW3.54 | curl-minimal 8.11.1-4.amzn2023.0.1 fixed in 8.15.0-4.amzn2023.0.1 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2024-11053 | LOW3.54 | libcurl-minimal 8.11.1-4.amzn2023.0.1 fixed in 8.15.0-4.amzn2023.0.1 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-13034 | LOW3.47 | curl-minimal 8.11.1-4.amzn2023.0.1 fixed in 8.17.0-1.amzn2023.0.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | curl-minimal 8.11.1-4.amzn2023.0.1 fixed in 8.17.0-1.amzn2023.0.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-13034 | LOW3.47 | libcurl-minimal 8.11.1-4.amzn2023.0.1 fixed in 8.17.0-1.amzn2023.0.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | libcurl-minimal 8.11.1-4.amzn2023.0.1 fixed in 8.17.0-1.amzn2023.0.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-69418 | LOW3.4 | openssl-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.2.2-1.amzn2023.0.5 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW3.4 | openssl-libs 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.2.2-1.amzn2023.0.5 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12194 | LOW3.4 | org.bouncycastle:bc-fips 2.1.1 fixed in 2.1.2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11563 | LOW3.31 | curl-minimal 8.11.1-4.amzn2023.0.1 fixed in 8.11.1-4.amzn2023.0.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | curl-minimal 8.11.1-4.amzn2023.0.1 fixed in 8.17.0-1.amzn2023.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-11563 | LOW3.31 | libcurl-minimal 8.11.1-4.amzn2023.0.1 fixed in 8.11.1-4.amzn2023.0.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl-minimal 8.11.1-4.amzn2023.0.1 fixed in 8.17.0-1.amzn2023.0.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW3.31 | python3 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3805 | LOW3.21 | curl-minimal 8.11.1-4.amzn2023.0.1 fixed in 8.17.0-1.amzn2023.0.3 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3805 | LOW3.21 | libcurl-minimal 8.11.1-4.amzn2023.0.1 fixed in 8.17.0-1.amzn2023.0.3 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-9086 | LOW3.18 | curl-minimal 8.11.1-4.amzn2023.0.1 fixed in 8.15.0-4.amzn2023.0.1 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-9086 | LOW3.18 | libcurl-minimal 8.11.1-4.amzn2023.0.1 fixed in 8.15.0-4.amzn2023.0.1 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-0989 | LOW3.15 | libxml2 2.10.4-1.amzn2023.0.13 fixed in 2.10.4-1.amzn2023.0.17 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | openssl-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | openssl-libs 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | LOW3.11 | python3 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.6 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68121 | LOW3.06 | libcap 2.73-1.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.6 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | curl-minimal 8.11.1-4.amzn2023.0.1 fixed in 8.15.0-4.amzn2023.0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl-minimal 8.11.1-4.amzn2023.0.1 fixed in 8.15.0-4.amzn2023.0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9669 | LOW3.01 | python3 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14087 | LOW3 | glib2 2.82.2-766.amzn2023 fixed in 2.82.2-769.amzn2023 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-6653 | LOW3 | libxml2 2.10.4-1.amzn2023.0.13 fixed in 2.10.4-1.amzn2023.0.19 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6357 | LOW2.96 | python3-pip-wheel 21.3.1-2.amzn2023.0.14 fixed in 21.3.1-2.amzn2023.0.19 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.5 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl-libs 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.5 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-0864 | LOW2.8 | python3 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.8 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-13837 | LOW2.8 | python3 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6075 | LOW2.8 | python3 3.9.23-1.amzn2023.0.3 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.14 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.13 fixed in 2.10.4-1.amzn2023.0.15 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | LOW2.78 | glib2 2.82.2-766.amzn2023 fixed in 2.82.2-770.amzn2023 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | LOW2.78 | openssl-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | LOW2.78 | openssl-libs 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.5 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42584 | LOW2.78 | io.netty:netty-codec-http 4.1.124.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-42584 | LOW2.78 | io.netty:netty-codec-http 4.1.125.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-61726 | LOW2.7 | libcap 2.73-1.amzn2023.0.3 fixed in 2.73-1.amzn2023.0.6 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28388 | LOW2.7 | openssl-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.4 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28389 | LOW2.7 | openssl-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.4 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28390 | LOW2.7 | openssl-fips-provider-latest 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.4 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28389 | LOW2.7 | openssl-libs 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.4 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28390 | LOW2.7 | openssl-libs 1:3.2.2-1.amzn2023.0.2 fixed in 1:3.5.5-1.amzn2023.0.4 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-21441 | LOW2.7 | python3-pip-wheel 21.3.1-2.amzn2023.0.14 fixed in 21.3.1-2.amzn2023.0.16 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3276 | LOW2.7 | python3 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.8 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-12084 | LOW2.7 | python3 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3446 | LOW2.7 | python3 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | LOW2.48 | curl-minimal 8.11.1-4.amzn2023.0.1 fixed in 8.17.0-1.amzn2023.0.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | LOW2.48 | libcurl-minimal 8.11.1-4.amzn2023.0.1 fixed in 8.17.0-1.amzn2023.0.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | LOW2.48 | python3 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.5 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-0992 | LOW2.46 | libxml2 2.10.4-1.amzn2023.0.13 fixed in 2.10.4-1.amzn2023.0.16 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-10148 | LOW2.45 | curl-minimal 8.11.1-4.amzn2023.0.1 fixed in 8.15.0-4.amzn2023.0.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | curl-minimal 8.11.1-4.amzn2023.0.1 fixed in 8.17.0-1.amzn2023.0.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-10148 | LOW2.45 | libcurl-minimal 8.11.1-4.amzn2023.0.1 fixed in 8.15.0-4.amzn2023.0.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl-minimal 8.11.1-4.amzn2023.0.1 fixed in 8.17.0-1.amzn2023.0.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | LOW2.45 | python3 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.45 | python3 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl-minimal 8.11.1-4.amzn2023.0.1 fixed in 8.17.0-1.amzn2023.0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl-minimal 8.11.1-4.amzn2023.0.1 fixed in 8.17.0-1.amzn2023.0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3644 | LOW2.29 | python3 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW2.29 | python3 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW2.29 | python3 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.7 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-66418 | LOW2.29 | python3-pip-wheel 21.3.1-2.amzn2023.0.14 fixed in 21.3.1-2.amzn2023.0.15 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-66471 | LOW2.29 | python3-pip-wheel 21.3.1-2.amzn2023.0.14 fixed in 21.3.1-2.amzn2023.0.15 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-11468 | LOW2.29 | python3 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0865 | LOW2.29 | python3 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8291 | LOW2.19 | python3 3.9.23-1.amzn2023.0.3 fixed in 3.9.24-1.amzn2023.0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-1299 | LOW2.17 | python3 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-1703 | LOW1.99 | python3-pip-wheel 21.3.1-2.amzn2023.0.14 fixed in 21.3.1-2.amzn2023.0.17 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW1.68 | python3 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4519 | LOW1.68 | python3 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.68 | python3 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gnupg2-minimal 2.3.7-1.amzn2023.0.5 fixed in 2.3.7-1.amzn2023.0.9 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | NONE0 | python3-libs 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.5 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-3644 | NONE0 | python3-libs 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.5 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4224 | NONE0 | python3-libs 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-7210 | NONE0 | python3-libs 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.7 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-1299 | NONE0 | python3-libs 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4786 | NONE0 | python3-libs 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11972 | NONE0 | python3-libs 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6019 | NONE0 | python3-libs 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-9669 | NONE0 | python3-libs 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0864 | NONE0 | python3-libs 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-13837 | NONE0 | python3-libs 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6075 | NONE0 | python3-libs 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3276 | NONE0 | python3-libs 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-12084 | NONE0 | python3-libs 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-3446 | NONE0 | python3-libs 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-15282 | NONE0 | python3-libs 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0672 | NONE0 | python3-libs 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-11468 | NONE0 | python3-libs 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0865 | NONE0 | python3-libs 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-8291 | NONE0 | python3-libs 3.9.23-1.amzn2023.0.3 fixed in 3.9.24-1.amzn2023.0.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-13462 | NONE0 | python3-libs 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4519 | NONE0 | python3-libs 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-2297 | NONE0 | python3-libs 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.4 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3479 | NONE0 | python3-libs 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-0167 | NONE0 | curl-minimal 8.11.1-4.amzn2023.0.1 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.11.1-4.amzn2023.0.1 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.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.7 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | python3-libs 3.9.23-1.amzn2023.0.3 fixed in 3.9.25-1.amzn2023.0.8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3-libs 3.9.23-1.amzn2023.0.3 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.6 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.6 fixed in 3.40.0-1.amzn2023.0.8 | 0.2% Theoretical Threat | Not Applicable |
| GHSA-r7wm-3cxj-wff9 | NONE0 | com.fasterxml.jackson.core:jackson-core 2.16.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.16.2 fixed in 2.21.1, 2.18.6 | — | Not Applicable |
| GHSA-r7wm-3cxj-wff9 | NONE0 | com.fasterxml.jackson.core:jackson-core 2.18.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.18.2 fixed in 2.21.1, 2.18.6 | — | Not Applicable |
| CVE-2026-59889 | NONE0 | com.fasterxml.jackson.core:jackson-databind 2.18.2 fixed in 2.21.5, 2.18.9, 2.22.1 | 0.3% Theoretical Threat | Not Applicable |
| GHSA-mhm7-754m-9p8w | NONE0 | com.fasterxml.jackson.core:jackson-databind 2.18.2 fixed in 2.18.9, 2.21.5 | — | Not Applicable |
| CVE-2026-33558 | NONE0 | org.apache.kafka:kafka-clients 4.0.0 fixed in 3.9.2, 4.0.1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-10050 | NONE0 | org.eclipse.jetty:jetty-security 9.4.56.v20240826 fixed in 9.4.63, 10.0.31, 11.0.31, 12.0.36, 12.1.10 | — | 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.