Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. The top findings are denial-of-service issues, including CVE-2026-28389 and CVE-2026-68497, so an attacker who can reach the service with crafted inputs could cause crashes, CPU exhaustion, or memory growth that disrupts Elasticsearch availability. CVE-2026-28389 only applies if untrusted CMS EnvelopedData is processed, and several Jackson issues depend on specific deserialization paths; avoiding those paths would fully eliminate the relevant risk. The official image is trusted and pinned, but the vulnerable bundled components still require strict compensating controls before production use.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-28389 | MEDIUM6.38 | openssl-libs 1:3.5.8-1.el9_8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-89425 | MEDIUM6.38 | com.fasterxml.jackson.core:jackson-core 2.18.9 fixed in 2.21.7, 2.22.3, 2.18.11 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-68494 | MEDIUM6.38 | com.fasterxml.jackson.core:jackson-core 2.19.2 fixed in 2.18.8, 2.21.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-89425 | MEDIUM6.38 | com.fasterxml.jackson.core:jackson-core 2.19.2 fixed in 2.21.7, 2.22.3, 2.18.11 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-89425 | MEDIUM6.38 | com.fasterxml.jackson.core:jackson-core 2.21.5 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.18.9 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.18.9 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.18.9 fixed in 2.21.7, 2.18.11, 2.22.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-68497 | MEDIUM6.38 | com.fasterxml.jackson.core:jackson-databind 2.19.2 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.19.2 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.19.2 fixed in 2.21.7, 2.18.11, 2.22.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-68497 | MEDIUM6.38 | com.fasterxml.jackson.core:jackson-databind 2.21.5 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.21.5 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.21.5 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 4.1.135.Final fixed in 4.1.136.Final | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-73508 | MEDIUM6.38 | io.netty:netty-codec-dns 4.1.135.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.1.135.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.1.135.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.1.135.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.1.135.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.1.135.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.135.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.1.135.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.1.135.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-75596 | MEDIUM6.38 | io.netty:netty-handler 4.1.135.Final fixed in 4.2.17.Final, 4.1.137.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75140 | MEDIUM6.38 | org.jsoup:jsoup 1.21.2 fixed in 1.23.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-88647 | MEDIUM6.29 | gnutls 3.8.10-8.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88648 | MEDIUM6.29 | gnutls 3.8.10-8.el9_8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-84782 | MEDIUM6.29 | openssl-libs 1:3.5.8-1.el9_8 fixed in 1:3.5.8-2.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-89157 | MEDIUM6.29 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75595 | MEDIUM6.18 | io.netty:netty-handler 4.1.135.Final fixed in 4.2.17.Final, 4.1.137.Final | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86805 | MEDIUM5.95 | glibc 2.34-275.el9_8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM5.95 | glibc 2.34-275.el9_8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM5.95 | glibc-common 2.34-275.el9_8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM5.95 | glibc-common 2.34-275.el9_8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM5.95 | glibc-minimal-langpack 2.34-275.el9_8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM5.95 | glibc-minimal-langpack 2.34-275.el9_8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM5.95 | libblkid 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libgcc 11.5.0-14.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM5.95 | libmount 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM5.95 | libsmartcols 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libstdc++ 11.5.0-14.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM5.95 | libuuid 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-106451 | MEDIUM5.95 | at.yawk.lz4:lz4-java 1.11.1 fixed in 1.11.4 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-41996 | MEDIUM5.9 | openssl-libs 1:3.5.8-1.el9_8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | openldap 2.6.8-4.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | systemd-libs 252-67.el9_8.6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5915 | MEDIUM5.61 | libarchive 3.5.3-11.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5918 | MEDIUM5.61 | libarchive 3.5.3-11.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM5.52 | krb5-libs 1.21.1-10.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4426 | MEDIUM5.52 | libarchive 3.5.3-11.el9_8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-9149 | MEDIUM5.52 | libsolv 0.7.24-6.el9_8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-9150 | MEDIUM5.52 | libsolv 0.7.24-6.el9_8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-45322 | MEDIUM5.52 | libxml2 2.9.13-14.el9_8.5 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-89158 | MEDIUM5.52 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89160 | MEDIUM5.52 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59888 | MEDIUM5.52 | com.fasterxml.jackson.core:jackson-databind 2.19.2 fixed in 2.18.8, 2.21.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59921 | MEDIUM5.52 | io.netty:netty-codec-http 4.1.135.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-1757 | MEDIUM5.27 | libxml2 2.9.13-14.el9_8.5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31912 | MEDIUM5.18 | libpcap 14:1.10.0-4.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22227 | MEDIUM5.18 | io.projectreactor.netty:reactor-netty-http 1.0.45 fixed in 1.3.0-M5, 1.2.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | glibc 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.02 | glibc 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.02 | glibc 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | glibc-common 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.02 | glibc-common 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.02 | glibc-common 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | glibc-minimal-langpack 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.02 | glibc-minimal-langpack 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.02 | glibc-minimal-langpack 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-67693 | MEDIUM5.02 | gnutls 3.8.10-8.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0990 | MEDIUM5.02 | libxml2 2.9.13-14.el9_8.5 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-54872 | MEDIUM5.02 | openssl-libs 1:3.5.8-1.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-72897 | MEDIUM5.02 | openssl-libs 1:3.5.8-1.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75805 | MEDIUM5.02 | openssl-libs 1:3.5.8-1.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77696 | MEDIUM5.02 | openssl-libs 1:3.5.8-1.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42765 | MEDIUM5.02 | openssl-libs 1:3.5.8-1.el9_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-89156 | MEDIUM5.02 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-89407 | MEDIUM5.02 | com.fasterxml.jackson.core:jackson-core 2.18.9 fixed in 2.18.11, 2.21.7, 2.22.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-89407 | MEDIUM5.02 | com.fasterxml.jackson.core:jackson-core 2.19.2 fixed in 2.18.11, 2.21.7, 2.22.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-89407 | MEDIUM5.02 | com.fasterxml.jackson.core:jackson-core 2.21.5 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.25.4 fixed in 2.25.5, 2.26.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | MEDIUM5 | openssl-libs 1:3.5.8-1.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54513 | MEDIUM4.86 | com.fasterxml.jackson.core:jackson-databind 2.19.2 fixed in 2.18.8, 2.21.4, 3.1.4 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-5916 | MEDIUM4.76 | libarchive 3.5.3-11.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-83557 | MEDIUM4.76 | com.fasterxml.jackson.core:jackson-databind 2.18.9 fixed in 2.18.10, 2.21.6, 2.22.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-83557 | MEDIUM4.76 | com.fasterxml.jackson.core:jackson-databind 2.19.2 fixed in 2.18.10, 2.21.6, 2.22.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-83557 | MEDIUM4.76 | com.fasterxml.jackson.core:jackson-databind 2.21.5 fixed in 2.18.10, 2.21.6, 2.22.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | glibc 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | glibc-common 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | glibc-minimal-langpack 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-60753 | MEDIUM4.67 | libarchive 3.5.3-11.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5745 | MEDIUM4.67 | libarchive 3.5.3-11.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1632 | MEDIUM4.67 | libarchive 3.5.3-11.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | MEDIUM4.67 | libgcc 11.5.0-14.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc 11.5.0-14.el9 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-31911 | MEDIUM4.67 | libpcap 14:1.10.0-4.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6244 | MEDIUM4.67 | libpcap 14:1.10.0-4.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6554 | MEDIUM4.67 | libpcap 14:1.10.0-4.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-82327 | MEDIUM4.67 | libsolv 0.7.24-6.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | MEDIUM4.67 | libstdc++ 11.5.0-14.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libstdc++ 11.5.0-14.el9 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-50812 | MEDIUM4.67 | sqlite-libs 3.34.1-11.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-0232 | MEDIUM4.67 | sqlite-libs 3.34.1-11.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM4.67 | systemd-libs 252-67.el9_8.6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib 1.2.11-40.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1489 | MEDIUM4.59 | glib2 2.68.4-19.el9_8.10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86469 | MEDIUM4.5 | glib2 2.68.4-19.el9_8.10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM4.5 | glibc 2.34-275.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM4.5 | glibc-common 2.34-275.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM4.5 | glibc-minimal-langpack 2.34-275.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-30571 | MEDIUM4.5 | libarchive 3.5.3-11.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libblkid 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libmount 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libsmartcols 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libuuid 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42772 | MEDIUM4.5 | openssl-libs 1:3.5.8-1.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54873 | MEDIUM4.5 | openssl-libs 1:3.5.8-1.el9_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75804 | MEDIUM4.5 | openssl-libs 1:3.5.8-1.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM4.5 | openssl-libs 1:3.5.8-1.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-84784 | MEDIUM4.5 | openssl-libs 1:3.5.8-1.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | xz-libs 5.2.5-8.el9_0 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-106450 | MEDIUM4.5 | at.yawk.lz4:lz4-java 1.11.1 fixed in 1.11.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106452 | MEDIUM4.5 | at.yawk.lz4:lz4-java 1.11.1 fixed in 1.11.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106453 | MEDIUM4.5 | at.yawk.lz4:lz4-java 1.11.1 fixed in 1.11.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-18401 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-core 2.19.2 fixed in 2.21.1, 2.18.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-19032 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-databind 2.18.9 fixed in 2.18.10, 2.21.6, 2.22.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-19032 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-databind 2.19.2 fixed in 2.18.10, 2.21.6, 2.22.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54514 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-databind 2.19.2 fixed in 2.18.8, 2.21.4, 3.1.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54515 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-databind 2.19.2 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.19.2 fixed in 2.18.9, 2.21.5, 2.22.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19032 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-databind 2.21.5 fixed in 2.18.10, 2.21.6, 2.22.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-59900 | MEDIUM4.5 | io.netty:netty-codec-http2 4.1.135.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM4.25 | bzip2-libs 1.0.8-11.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | krb5-libs 1.21.1-10.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5917 | MEDIUM4.25 | libarchive 3.5.3-11.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18238 | MEDIUM4.25 | libpcap 14:1.10.0-4.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | glibc 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | glibc-common 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | glibc-minimal-langpack 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.17 | krb5-libs 1.21.1-10.el9_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54512 | MEDIUM4.13 | com.fasterxml.jackson.core:jackson-databind 2.19.2 fixed in 2.18.8, 3.1.4, 2.21.4 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libblkid 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54875 | MEDIUM4 | openssl-libs 1:3.5.8-1.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | openssl-libs 1:3.5.8-1.el9_8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-71497 | MEDIUM4 | org.jsoup:jsoup 1.21.2 fixed in 1.23.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-95519 | LOW3.98 | rpm 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-95521 | LOW3.98 | rpm 4.16.1.3-40.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-92388 | LOW3.9 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | — | Post-Exploit |
| CVE-2026-92390 | LOW3.9 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | — | Post-Exploit |
| CVE-2026-92388 | LOW3.9 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | — | Post-Exploit |
| CVE-2026-92390 | LOW3.9 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | — | Post-Exploit |
| CVE-2026-28388 | LOW3.83 | openssl-libs 1:3.5.8-1.el9_8 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-5773 | LOW3.82 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9546 | LOW3.82 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9546 | LOW3.82 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW3.72 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW3.72 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-48924 | LOW3.7 | org.apache.commons:commons-lang3 3.9 fixed in 3.18.0 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-18313 | LOW3.65 | libpcap 14:1.10.0-4.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4156 | LOW3.62 | gawk 5.1.0-6.el9_8.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-103242 | LOW3.62 | rpm 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-95520 | LOW3.62 | rpm 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-78367 | LOW3.57 | rpm 4.16.1.3-40.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-1484 | LOW3.57 | glib2 2.68.4-19.el9_8.10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | LOW3.57 | glibc 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | glibc 2.34-275.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | LOW3.57 | glibc-common 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | glibc-common 2.34-275.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | LOW3.57 | glibc-minimal-langpack 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | glibc-minimal-langpack 2.34-275.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-11053 | LOW3.54 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2024-11053 | LOW3.54 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-13034 | LOW3.47 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-13034 | LOW3.47 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | curl-minimal 7.76.1-40.el9_8.7 fixed in 7.76.1-40.el9_8.8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-19931 | LOW3.31 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl-minimal 7.76.1-40.el9_8.7 fixed in 7.76.1-40.el9_8.8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | libcurl-minimal 7.76.1-40.el9_8.7 fixed in 7.76.1-40.el9_8.8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-19931 | LOW3.31 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl-minimal 7.76.1-40.el9_8.7 fixed in 7.76.1-40.el9_8.8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-72712 | LOW3.31 | nmap-ncat 3:7.92-5.el9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-15028 | LOW3.31 | libarchive 3.5.3-11.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-0529 | LOW3.3 | unzip 6.0-60.el9 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-0530 | LOW3.3 | unzip 6.0-60.el9 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-5958 | LOW3.21 | sed 4.8-10.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-86409 | LOW3.18 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | — | Post-Exploit |
| CVE-2026-86409 | LOW3.18 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | — | Post-Exploit |
| CVE-2025-3360 | LOW3.15 | glib2 2.68.4-19.el9_8.10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-7039 | LOW3.15 | glib2 2.68.4-19.el9_8.10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0988 | LOW3.15 | glib2 2.68.4-19.el9_8.10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.15 | glibc 2.34-275.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.15 | glibc-common 2.34-275.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.15 | glibc-minimal-langpack 2.34-275.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0989 | LOW3.15 | libxml2 2.9.13-14.el9_8.5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.15 | openssl-libs 1:3.5.8-1.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35191 | LOW3.15 | openssl-libs 1:3.5.8-1.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.15 | openssl-libs 1:3.5.8-1.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-106449 | LOW3.15 | at.yawk.lz4:lz4-java 1.11.1 fixed in 1.11.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56391 | LOW3.11 | coreutils-single 8.32-41.el9_8.1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-9232 | LOW3.1 | openssl-libs 1:3.5.8-1.el9_8 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-17591 | LOW3.06 | libarchive 3.5.3-11.el9_8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-84837 | LOW2.81 | rpm 4.16.1.3-40.el9 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-24883 | LOW2.8 | gnupg2 2.3.3-5.el9_7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-44605 | LOW2.8 | rpm 4.16.1.3-40.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41990 | LOW2.8 | libgcrypt 1.10.0-13.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | sqlite-libs 3.34.1-11.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-27113 | LOW2.7 | libxml2 2.9.13-14.el9_8.5 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-41409 | LOW2.7 | pcre2 10.40-6.el9 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-7264 | LOW2.69 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | 20.2% High Exploitation Risk | Post-Exploit |
| CVE-2024-7264 | LOW2.69 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | 20.2% High Exploitation Risk | Post-Exploit |
| CVE-2026-0799 | LOW2.66 | libpcap 14:1.10.0-4.el9 fixed in 14:1.10.0-4.el9_8.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-86145 | LOW2.51 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | LOW2.48 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | LOW2.48 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-28387 | LOW2.48 | openssl-libs 1:3.5.8-1.el9_8 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-0992 | LOW2.46 | libxml2 2.9.13-14.el9_8.5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | LOW2.45 | libblkid 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.45 | libmount 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.45 | libsmartcols 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.45 | libuuid 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gnupg2 2.3.3-5.el9_7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gnupg2 2.3.3-5.el9_7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-89161 | LOW2.39 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-1485 | LOW2.38 | glib2 2.68.4-19.el9_8.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | LOW2.36 | libgcc 11.5.0-14.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW2.36 | libstdc++ 11.5.0-14.el9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-9681 | LOW2.34 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-86414 | LOW2.34 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | — | Post-Exploit |
| CVE-2024-9681 | LOW2.34 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-86414 | LOW2.34 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | — | Post-Exploit |
| CVE-2026-58058 | LOW2.34 | nmap-ncat 3:7.92-5.el9 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-103111 | LOW2.33 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-107161 | LOW2.29 | cyrus-sasl-lib 2.1.27-22.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-32636 | LOW2.29 | glib2 2.68.4-19.el9_8.10 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-87864 | LOW2.22 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | — | Post-Exploit |
| CVE-2026-92389 | LOW2.22 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | — | Post-Exploit |
| CVE-2026-92391 | LOW2.22 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | — | Post-Exploit |
| CVE-2026-87864 | LOW2.22 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | — | Post-Exploit |
| CVE-2026-92389 | LOW2.22 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | — | Post-Exploit |
| CVE-2026-92391 | LOW2.22 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | — | Post-Exploit |
| CVE-2026-94266 | LOW1.98 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | — | Post-Exploit |
| CVE-2026-94266 | LOW1.98 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | — | Post-Exploit |
| CVE-2026-18924 | LOW1.89 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.89 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW1.89 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.89 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW1.84 | gnupg2 2.3.3-5.el9_7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gnupg2 2.3.3-5.el9_7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-4217 | LOW1.68 | unzip 6.0-60.el9 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-11961 | LOW1.61 | libpcap 14:1.10.0-4.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-82209 | LOW1.58 | curl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-82209 | LOW1.58 | libcurl-minimal 7.76.1-40.el9_8.7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gnupg2 2.3.3-5.el9_7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-86145 | NONE0 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89161 | NONE0 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-84837 | NONE0 | rpm-libs 4.16.1.3-40.el9 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-95519 | NONE0 | rpm-libs 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-95521 | NONE0 | rpm-libs 4.16.1.3-40.el9 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-103111 | NONE0 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-41409 | NONE0 | pcre2-syntax 10.40-6.el9 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-89157 | NONE0 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-103242 | NONE0 | rpm-libs 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-95520 | NONE0 | rpm-libs 4.16.1.3-40.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-78367 | NONE0 | rpm-libs 4.16.1.3-40.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.2-12.20210508.el9 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-libs 6.2-12.20210508.el9 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-89158 | NONE0 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89160 | NONE0 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89156 | NONE0 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-44605 | NONE0 | rpm-libs 4.16.1.3-40.el9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-77420 | NONE0 | org.jline:jline-reader 3.21.0 fixed in 4.3.1, 3.30.15 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-18739 | NONE0 | popt 1.18-8.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-18743 | NONE0 | popt 1.18-8.el9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-18839 | NONE0 | popt 1.18-8.el9 No fix yet | 0.1% Theoretical Threat | 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.
Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.
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.