Last scanned:
··This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker could exploit the OpenSSL and OpenJDK issues to cause denial of service or tamper with data handled by Nexus, with CVE-2026-63072 enabling heap corruption via CMS decryption and CVE-2026-47063 allowing unauthorized data modification through Java APIs. The image has 109 exposed findings, 43 at severity >= 6, and an exposed max severity of 6.38, while there are no exposed findings at severity >= 7; post-exploit-only findings are 80 with a post max severity of 3.82. Several OpenSSL findings are protocol-specific, so assess whether CMS, QUIC, DTLS, or CMP features are enabled in this Nexus deployment, and disable any unused protocols to eliminate those specific denial-of-service paths.
Hardening plan for this image · 4 steps. The first cuts risk from 50 to 0.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-63072 | MEDIUM6.38 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-54874 | MEDIUM6.38 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM6.38 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM6.38 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-63072 | MEDIUM6.38 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-54874 | MEDIUM6.38 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM6.38 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM6.38 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-41254 | MEDIUM6.38 | openjdk21 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-47063 | MEDIUM6.38 | openjdk21 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41254 | MEDIUM6.38 | openjdk21-jdk 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-47063 | MEDIUM6.38 | openjdk21-jdk 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41254 | MEDIUM6.38 | openjdk21-jre 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-47063 | MEDIUM6.38 | openjdk21-jre 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41254 | MEDIUM6.38 | openjdk21-jre-headless 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-47063 | MEDIUM6.38 | openjdk21-jre-headless 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-89425 | MEDIUM6.38 | com.fasterxml.jackson.core:jackson-core 2.22.0 fixed in 2.21.7, 2.22.3, 2.18.11 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-68497 | MEDIUM6.38 | com.fasterxml.jackson.core:jackson-databind 2.22.0 fixed in 2.18.10, 2.21.6, 2.22.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-91776 | MEDIUM6.38 | com.fasterxml.jackson.core:jackson-databind 2.22.0 fixed in 2.18.11, 2.21.7, 2.22.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-91777 | MEDIUM6.38 | com.fasterxml.jackson.core:jackson-databind 2.22.0 fixed in 2.21.7, 2.18.11, 2.22.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59901 | MEDIUM6.38 | io.netty:netty-codec-compression 4.2.15.Final fixed in 4.2.16.Final | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-73508 | MEDIUM6.38 | io.netty:netty-codec-dns 4.2.15.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-55831 | MEDIUM6.38 | io.netty:netty-codec-http 4.2.15.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-55833 | MEDIUM6.38 | io.netty:netty-codec-http 4.2.15.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-56745 | MEDIUM6.38 | io.netty:netty-codec-http 4.2.15.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56746 | MEDIUM6.38 | io.netty:netty-codec-http 4.2.15.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59898 | MEDIUM6.38 | io.netty:netty-codec-http 4.2.15.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.2.15.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-59903 | MEDIUM6.38 | io.netty:netty-codec-http 4.2.15.Final fixed in 4.2.17.Final, 4.1.137.Final | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56819 | MEDIUM6.38 | io.netty:netty-codec-http2 4.2.15.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-56816 | MEDIUM6.38 | io.netty:netty-codec-http3 4.2.15.Final fixed in 4.2.16.Final | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-75596 | MEDIUM6.38 | io.netty:netty-handler 4.2.15.Final fixed in 4.2.17.Final, 4.1.137.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-84939 | MEDIUM6.38 | org.freemarker:freemarker 2.3.32 fixed in 2.3.35 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-75140 | MEDIUM6.38 | org.jsoup:jsoup 1.15.3 fixed in 1.23.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-89425 | MEDIUM6.38 | tools.jackson.core:jackson-core 3.2.0 fixed in 3.1.7, 3.2.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-68497 | MEDIUM6.38 | tools.jackson.core:jackson-databind 3.2.0 fixed in 3.2.2, 3.1.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-91776 | MEDIUM6.38 | tools.jackson.core:jackson-databind 3.2.0 fixed in 3.1.7, 3.2.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-91777 | MEDIUM6.38 | tools.jackson.core:jackson-databind 3.2.0 fixed in 3.1.7, 3.2.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75595 | MEDIUM6.18 | io.netty:netty-handler 4.2.15.Final fixed in 4.2.17.Final, 4.1.137.Final | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-49268 | MEDIUM6.18 | org.apache.shiro:shiro-core 1.13.0 fixed in 2.2.1, 3.0.0-alpha-2 | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-8763 | MEDIUM6.18 | org.bouncycastle:bc-fips 2.1.2 fixed in 1.0.2.7, 2.0.2, 2.1.3 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-8763 | MEDIUM6.18 | org.bouncycastle:bcprov-jdk18on 1.84 fixed in 1.85 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-10050 | MEDIUM6.18 | org.eclipse.jetty.ee8:jetty-ee8-security 12.0.33 fixed in 12.0.36, 12.1.10 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-63073 | MEDIUM5.9 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-46675 | MEDIUM5.9 | libpng 1.6.58-r1 fixed in 1.6.59-r0 | — | Directly Exposed |
| CVE-2026-63073 | MEDIUM5.9 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-60147 | MEDIUM5.52 | openjdk21 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-60147 | MEDIUM5.52 | openjdk21-jdk 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-60147 | MEDIUM5.52 | openjdk21-jre 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-60147 | MEDIUM5.52 | openjdk21-jre-headless 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59889 | MEDIUM5.52 | com.fasterxml.jackson.core:jackson-databind 2.22.0 fixed in 2.21.5, 2.18.9, 2.22.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59921 | MEDIUM5.52 | io.netty:netty-codec-http 4.2.15.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43827 | MEDIUM5.52 | org.apache.shiro:shiro-core 1.13.0 fixed in 2.2.0, 3.0.0-alpha-2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43828 | MEDIUM5.52 | org.apache.shiro:shiro-web 1.13.0 fixed in 2.2.0, 3.0.0-alpha-2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59889 | MEDIUM5.52 | tools.jackson.core:jackson-databind 3.2.0 fixed in 3.1.5, 3.2.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13506 | MEDIUM5.1 | org.bouncycastle:bcprov-jdk18on 1.84 fixed in 1.85 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-46968 | MEDIUM5.02 | openjdk21 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46968 | MEDIUM5.02 | openjdk21-jdk 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46968 | MEDIUM5.02 | openjdk21-jre 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46968 | MEDIUM5.02 | openjdk21-jre-headless 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-89407 | MEDIUM5.02 | com.fasterxml.jackson.core:jackson-core 2.22.0 fixed in 2.18.11, 2.21.7, 2.22.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-49844 | MEDIUM5.02 | org.apache.logging.log4j:log4j-api 2.19.0 fixed in 2.25.5, 2.26.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-54291 | MEDIUM5.02 | org.postgresql:postgresql 42.7.11 fixed in 42.7.12 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89407 | MEDIUM5.02 | tools.jackson.core:jackson-core 3.2.0 fixed in 3.1.7, 3.2.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-83557 | MEDIUM4.76 | com.fasterxml.jackson.core:jackson-databind 2.22.0 fixed in 2.18.10, 2.21.6, 2.22.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-83557 | MEDIUM4.76 | tools.jackson.core:jackson-databind 3.2.0 fixed in 3.1.6, 3.2.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-58055 | MEDIUM4.59 | nghttp2-libs 1.69.0-r0 fixed in 1.70.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46917 | MEDIUM4.5 | openjdk21 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47021 | MEDIUM4.5 | openjdk21 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47027 | MEDIUM4.5 | openjdk21 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46917 | MEDIUM4.5 | openjdk21-jdk 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47021 | MEDIUM4.5 | openjdk21-jdk 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47027 | MEDIUM4.5 | openjdk21-jdk 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46917 | MEDIUM4.5 | openjdk21-jre 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47021 | MEDIUM4.5 | openjdk21-jre 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47027 | MEDIUM4.5 | openjdk21-jre 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46917 | MEDIUM4.5 | openjdk21-jre-headless 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47021 | MEDIUM4.5 | openjdk21-jre-headless 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47027 | MEDIUM4.5 | openjdk21-jre-headless 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19032 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-databind 2.22.0 fixed in 2.18.10, 2.21.6, 2.22.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54515 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-databind 2.22.0 fixed in 3.1.4, 2.18.9, 2.21.5, 2.22.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-77310 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-databind 2.22.0 fixed in 2.18.9, 2.21.5, 2.22.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59900 | MEDIUM4.5 | io.netty:netty-codec-http2 4.2.15.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23903 | MEDIUM4.5 | org.apache.shiro:shiro-spring 1.13.0 fixed in 2.1.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8384 | MEDIUM4.5 | org.eclipse.jetty:jetty-util 12.0.33 fixed in 12.0.35, 12.1.9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19032 | MEDIUM4.5 | tools.jackson.core:jackson-databind 3.2.0 fixed in 3.1.6, 3.2.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-77310 | MEDIUM4.5 | tools.jackson.core:jackson-databind 3.2.0 fixed in 3.1.5, 3.2.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-71497 | MEDIUM4 | org.jsoup:jsoup 1.15.3 fixed in 1.23.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11586 | LOW3.82 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9079 | LOW3.82 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9546 | LOW3.82 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-11352 | LOW3.82 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-11586 | LOW3.82 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9079 | LOW3.82 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9546 | LOW3.82 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-14456 | LOW3.82 | openssl 3.5.7-r0 fixed in 3.5.8-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-63072 | LOW3.82 | openssl 3.5.7-r0 fixed in 3.5.8-r0 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-54874 | LOW3.82 | openssl 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63074 | LOW3.82 | openssl 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63075 | LOW3.82 | openssl 3.5.7-r0 fixed in 3.5.8-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW3.72 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW3.72 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-63073 | LOW3.54 | openssl 3.5.7-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-11564 | LOW3.31 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-19931 | LOW3.31 | curl 8.20.0-r1 fixed in 8.22.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-11564 | LOW3.31 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-19931 | LOW3.31 | libcurl 8.20.0-r1 fixed in 8.22.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-75803 | LOW3.15 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.15 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-47010 | LOW3.15 | openjdk21 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47059 | LOW3.15 | openjdk21 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47010 | LOW3.15 | openjdk21-jdk 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47059 | LOW3.15 | openjdk21-jdk 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47010 | LOW3.15 | openjdk21-jre 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47059 | LOW3.15 | openjdk21-jre 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47010 | LOW3.15 | openjdk21-jre-headless 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47059 | LOW3.15 | openjdk21-jre-headless 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8925 | LOW2.92 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-8925 | LOW2.92 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-26740 | LOW2.7 | giflib 5.2.2-r1 fixed in 5.2.2-r2 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-18798 | LOW2.7 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63076 | LOW2.7 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-14457 | LOW2.7 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-18798 | LOW2.7 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63076 | LOW2.7 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-14457 | LOW2.7 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-18798 | LOW2.7 | openssl 3.5.7-r0 fixed in 3.5.8-r0 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63076 | LOW2.7 | openssl 3.5.7-r0 fixed in 3.5.8-r0 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-14457 | LOW2.7 | openssl 3.5.7-r0 fixed in 3.5.8-r0 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-2100 | LOW2.7 | p11-kit 0.25.5-r2 fixed in 0.26.2-r0 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-2100 | LOW2.7 | p11-kit-trust 0.25.5-r2 fixed in 0.26.2-r0 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-8286 | LOW2.48 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | LOW2.48 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | LOW2.48 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | LOW2.48 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-82208 | LOW2.45 | curl 8.20.0-r1 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-82208 | LOW2.45 | libcurl 8.20.0-r1 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | libcurl 8.20.0-r1 fixed in 8.21.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-33630 | LOW2.29 | c-ares 1.34.6-r0 fixed in 1.34.8-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-11352 | LOW2.29 | curl 8.20.0-r1 fixed in 8.21.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-14456 | LOW2.29 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-14456 | LOW2.29 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-13505 | LOW2.29 | org.bouncycastle:bc-fips 2.1.2 fixed in 1.0.2.7, 2.0.2, 2.1.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-13506 | LOW2.29 | org.bouncycastle:bc-fips 2.1.2 fixed in 1.0.2.7, 2.0.2, 2.1.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-23901 | LOW2.12 | org.apache.shiro:shiro-core 1.13.0 fixed in 2.1.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13608 | LOW1.89 | curl 8.20.0-r1 fixed in 8.22.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW1.89 | curl 8.20.0-r1 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80229 | LOW1.89 | curl 8.20.0-r1 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.89 | curl 8.20.0-r1 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-80231 | LOW1.89 | curl 8.20.0-r1 fixed in 8.22.0-r0 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-80255 | LOW1.89 | curl 8.20.0-r1 fixed in 8.22.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-13608 | LOW1.89 | libcurl 8.20.0-r1 fixed in 8.22.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW1.89 | libcurl 8.20.0-r1 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80229 | LOW1.89 | libcurl 8.20.0-r1 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.89 | libcurl 8.20.0-r1 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-80231 | LOW1.89 | libcurl 8.20.0-r1 fixed in 8.22.0-r0 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-80255 | LOW1.89 | libcurl 8.20.0-r1 fixed in 8.22.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-75803 | LOW1.89 | openssl 3.5.7-r0 fixed in 3.5.8-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-82209 | LOW1.58 | curl 8.20.0-r1 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-82209 | LOW1.58 | libcurl 8.20.0-r1 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-88807 | NONE0 | libxrender 0.9.12-r0 fixed in 0.9.13-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-88806 | NONE0 | libx11 1.8.13-r0 fixed in 1.8.14-r0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-41254 | NONE0 | openjdk21-demos 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-47063 | NONE0 | openjdk21-demos 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-41254 | NONE0 | openjdk21-doc 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-47063 | NONE0 | openjdk21-doc 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-41254 | NONE0 | openjdk21-jmods 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-47063 | NONE0 | openjdk21-jmods 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94286 | NONE0 | libxtst 1.2.5-r0 fixed in 1.2.6-r0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-94283 | NONE0 | libx11 1.8.13-r0 fixed in 1.8.14-r0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93541 | NONE0 | libxi 1.8.3-r0 fixed in 1.8.4-r0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93542 | NONE0 | libxi 1.8.3-r0 fixed in 1.8.4-r0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93543 | NONE0 | libxi 1.8.3-r0 fixed in 1.8.4-r0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93544 | NONE0 | libxi 1.8.3-r0 fixed in 1.8.4-r0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93545 | NONE0 | libxi 1.8.3-r0 fixed in 1.8.4-r0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-94281 | NONE0 | libxi 1.8.3-r0 fixed in 1.8.4-r0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-60147 | NONE0 | openjdk21-demos 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-60147 | NONE0 | openjdk21-doc 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-60147 | NONE0 | openjdk21-jmods 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94282 | NONE0 | libxi 1.8.3-r0 fixed in 1.8.4-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46968 | NONE0 | openjdk21-demos 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46968 | NONE0 | openjdk21-doc 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46968 | NONE0 | openjdk21-jmods 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94284 | NONE0 | libx11 1.8.13-r0 fixed in 1.8.14-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46917 | NONE0 | openjdk21-demos 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-47021 | NONE0 | openjdk21-demos 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-47027 | NONE0 | openjdk21-demos 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46917 | NONE0 | openjdk21-doc 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-47021 | NONE0 | openjdk21-doc 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-47027 | NONE0 | openjdk21-doc 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46917 | NONE0 | openjdk21-jmods 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-47021 | NONE0 | openjdk21-jmods 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-47027 | NONE0 | openjdk21-jmods 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94285 | NONE0 | libx11 1.8.13-r0 fixed in 1.8.14-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47010 | NONE0 | openjdk21-demos 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-47059 | NONE0 | openjdk21-demos 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-47010 | NONE0 | openjdk21-doc 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-47059 | NONE0 | openjdk21-doc 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-47010 | NONE0 | openjdk21-jmods 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-47059 | NONE0 | openjdk21-jmods 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80256 | NONE0 | curl 8.20.0-r1 fixed in 8.22.0-r0 | — | Not Applicable |
| CVE-2026-80256 | NONE0 | libcurl 8.20.0-r1 fixed in 8.22.0-r0 | — | Not Applicable |
| CVE-2026-109089 | NONE0 | libxi 1.8.3-r0 fixed in 1.8.4-r0 | — | Not Applicable |
| CVE-2026-109090 | NONE0 | libxi 1.8.3-r0 fixed in 1.8.4-r0 | — | Not Applicable |
| CVE-2026-109088 | NONE0 | libxtst 1.2.5-r0 fixed in 1.2.6-r0 | — | Not Applicable |
| CVE-2026-107891 | NONE0 | musl 1.2.6-r2 fixed in 1.2.6-r3 | — | Not Applicable |
| CVE-2026-107891 | NONE0 | musl-utils 1.2.6-r2 fixed in 1.2.6-r3 | — | Not Applicable |
| CVE-2026-62574 | NONE0 | openjdk21 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62574 | NONE0 | openjdk21-demos 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62574 | NONE0 | openjdk21-doc 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62574 | NONE0 | openjdk21-jdk 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62574 | NONE0 | openjdk21-jmods 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62574 | NONE0 | openjdk21-jre 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62574 | NONE0 | openjdk21-jre-headless 21.0.11_p10-r0 fixed in 21.0.12_p8-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-85091 | NONE0 | zlib 1.3.2-r0 fixed in 1.3.2-r1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-10532 | NONE0 | ch.qos.logback:logback-core 1.5.32 fixed in 1.5.34 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9828 | NONE0 | ch.qos.logback:logback-core 1.5.32 fixed in 1.5.33 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-113730 | NONE0 | ognl:ognl 3.4.4 fixed in 3.4.13 | — | Not Applicable |
| CVE-2026-8798 | NONE0 | org.bouncycastle:bc-fips 2.1.2 fixed in 2.1.3 | 0.4% Theoretical Threat | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.