Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. The most serious exposure is CVE-2026-111497, where a crafted Brotli-compressed stream could crash or corrupt memory in a decoder inside this Kafka Connect container, potentially allowing code execution. Whether this applies depends on whether Brotli compression is actually used on Kafka Connect traffic, so that should be verified first. The remaining findings, including CVE-2026-89425, are mainly denial-of-service flaws that could exhaust memory or threads on the Connect worker, and they apply only under specific parsing paths.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-111497 | HIGH7.45 | libbrotli 1.0.9-9.el9_7 No fix yet | 36.0% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-89407 | MEDIUM6 | com.fasterxml.jackson.core:jackson-core 2.21.5 fixed in 2.18.11, 2.21.7, 2.22.3 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-89425 | MEDIUM6 | 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 ExposedContext importance: MEDIUM |
| CVE-2026-89407 | MEDIUM6 | com.fasterxml.jackson.core:jackson-core 2.22.1 fixed in 2.18.11, 2.21.7, 2.22.3 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-89425 | MEDIUM6 | com.fasterxml.jackson.core:jackson-core 2.22.1 fixed in 2.21.7, 2.22.3, 2.18.11 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-68497 | MEDIUM6 | 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 ExposedContext importance: MEDIUM |
| CVE-2026-91776 | MEDIUM6 | com.fasterxml.jackson.core:jackson-databind 2.21.5 fixed in 2.18.11, 2.21.7, 2.22.3 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-68497 | MEDIUM6 | com.fasterxml.jackson.core:jackson-databind 2.22.1 fixed in 2.18.10, 2.21.6, 2.22.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-91776 | MEDIUM6 | com.fasterxml.jackson.core:jackson-databind 2.22.1 fixed in 2.18.11, 2.21.7, 2.22.3 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-6791 | MEDIUM5.9 | glibc 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | glibc 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | glibc 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | glibc-common 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | glibc-common 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | glibc-common 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | 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.9 | 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.9 | glibc-minimal-langpack 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54872 | MEDIUM5.9 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-72897 | MEDIUM5.9 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75805 | MEDIUM5.9 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-77696 | MEDIUM5.9 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-49844 | MEDIUM5.9 | org.apache.logging.log4j:log4j-api 2.25.4 fixed in 2.25.5, 2.26.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-49919 | MEDIUM5.8 | freetype 2.10.4-10.el9_5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM5.52 | python3 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-3644 | MEDIUM5.52 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-95512 | MEDIUM5.5 | freetype 2.10.4-10.el9_5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | glibc 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | glibc-common 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | glibc-minimal-langpack 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM5.5 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM5.5 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42308 | MEDIUM5.5 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-50812 | MEDIUM5.5 | sqlite-libs 3.34.1-11.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | systemd-libs 252-67.el9_8.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77420 | MEDIUM5.5 | org.jline:jline-reader 3.30.4 fixed in 4.3.1, 3.30.15 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-75595 | MEDIUM5.46 | io.netty:netty-handler 4.1.136.Final fixed in 4.2.17.Final, 4.1.137.Final | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-114406 | MEDIUM5.44 | ca-certificates 2025.2.80_v9.0.305-91.el9 fixed in 2026.2.92_v9.0.319-90.3.el9_8 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-1489 | MEDIUM5.4 | glib2 2.68.4-19.el9_8.10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23865 | MEDIUM5.3 | freetype 2.10.4-10.el9_5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86469 | MEDIUM5.3 | glib2 2.68.4-19.el9_8.10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | glibc 2.34-275.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | glibc-common 2.34-275.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | glibc-minimal-langpack 2.34-275.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22693 | MEDIUM5.3 | harfbuzz 2.7.4-10.el9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42772 | MEDIUM5.3 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54873 | MEDIUM5.3 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-75804 | MEDIUM5.3 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM5.3 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-84784 | MEDIUM5.3 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM5.3 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-19672 | MEDIUM5.3 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM5.3 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4360 | MEDIUM5.3 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM5.3 | xz-libs 5.2.5-8.el9_0 fixed in 5.2.5-8.el9_8.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-74860 | MEDIUM5.1 | libxml2 2.9.13-14.el9_8.4 fixed in 2.9.13-14.el9_8.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM5 | bzip2-libs 1.0.8-11.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-77214 | MEDIUM4.92 | expat 2.5.0-6.el9_8.3 fixed in 2.5.0-6.el9_8.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86145 | MEDIUM4.92 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86145 | MEDIUM4.92 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | glibc 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | glibc-common 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | glibc-minimal-langpack 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM4.88 | python3 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-6019 | MEDIUM4.88 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-19445 | MEDIUM4.86 | python3-libs 3.9.25-7.el9_8.3 fixed in 3.9.25-7.el9_8.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libblkid 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libmount 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libuuid 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | MEDIUM4.8 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.8 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54875 | MEDIUM4.7 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86140 | MEDIUM4.68 | libxml2 2.9.13-14.el9_8.4 fixed in 2.9.13-14.el9_8.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89161 | MEDIUM4.68 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-89161 | MEDIUM4.68 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-103111 | MEDIUM4.56 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-103111 | MEDIUM4.56 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66046 | MEDIUM4.5 | expat 2.5.0-6.el9_8.3 fixed in 2.5.0-6.el9_8.5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-76641 | MEDIUM4.5 | expat 2.5.0-6.el9_8.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-93990 | MEDIUM4.5 | expat 2.5.0-6.el9_8.3 fixed in 2.5.0-6.el9_8.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-14456 | MEDIUM4.5 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-91777 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-databind 2.21.5 fixed in 2.21.7, 2.18.11, 2.22.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-91777 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-databind 2.22.1 fixed in 2.21.7, 2.18.11, 2.22.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-59903 | MEDIUM4.5 | io.netty:netty-codec-http 4.1.136.Final fixed in 4.2.17.Final, 4.1.137.Final | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75596 | MEDIUM4.5 | io.netty:netty-handler 4.1.136.Final fixed in 4.2.17.Final, 4.1.137.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-77422 | MEDIUM4.5 | org.jline:jline-builtins 3.30.4 fixed in 4.3.1, 3.30.15 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56740 | MEDIUM4.5 | org.jline:jline-remote-telnet 3.30.4 fixed in 4.2.1, 4.0.16, 3.30.14 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-56741 | MEDIUM4.5 | org.jline:jline-remote-telnet 3.30.4 fixed in 4.2.1, 4.0.16, 3.30.14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-89425 | MEDIUM4.5 | tools.jackson.core:jackson-core 3.2.2 fixed in 3.1.7, 3.2.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-91776 | MEDIUM4.5 | tools.jackson.core:jackson-databind 3.2.2 fixed in 3.1.7, 3.2.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-91777 | MEDIUM4.5 | tools.jackson.core:jackson-databind 3.2.2 fixed in 3.1.7, 3.2.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | MEDIUM4.5 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | MEDIUM4.5 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83557 | MEDIUM4.48 | 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 ExposedContext importance: MEDIUM |
| CVE-2026-83557 | MEDIUM4.48 | com.fasterxml.jackson.core:jackson-databind 2.22.1 fixed in 2.18.10, 2.21.6, 2.22.2 | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-84782 | MEDIUM4.44 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-2.el9_8 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-19553 | MEDIUM4.44 | python3-libs 3.9.25-7.el9_8.3 fixed in 3.9.25-7.el9_8.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-4516 | MEDIUM4.33 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19032 | MEDIUM4.24 | 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 ExposedContext importance: MEDIUM |
| CVE-2026-19032 | MEDIUM4.24 | com.fasterxml.jackson.core:jackson-databind 2.22.1 fixed in 2.18.10, 2.21.6, 2.22.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-53613 | MEDIUM4.2 | libblkid 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libmount 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libuuid 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-106451 | MEDIUM4.2 | at.yawk.lz4:lz4-java 1.11.1 fixed in 1.11.4 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1484 | MEDIUM4.2 | glib2 2.68.4-19.el9_8.10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | glibc 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | glibc 2.34-275.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | glibc-common 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | glibc-common 2.34-275.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | glibc-minimal-langpack 2.34-275.el9_8 fixed in 2.34-283.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | glibc-minimal-langpack 2.34-275.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM4.14 | expat 2.5.0-6.el9_8.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56404 | MEDIUM4.14 | expat 2.5.0-6.el9_8.3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56405 | MEDIUM4.14 | expat 2.5.0-6.el9_8.3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM4.14 | expat 2.5.0-6.el9_8.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56407 | MEDIUM4.14 | expat 2.5.0-6.el9_8.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76957 | MEDIUM4.14 | expat 2.5.0-6.el9_8.3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.14 | libgcc 11.5.0-14.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.14 | libgcc 11.5.0-14.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.14 | libstdc++ 11.5.0-14.el9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.14 | libstdc++ 11.5.0-14.el9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86138 | MEDIUM4.14 | libxml2 2.9.13-14.el9_8.4 fixed in 2.9.13-14.el9_8.5 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86142 | MEDIUM4.14 | libxml2 2.9.13-14.el9_8.4 fixed in 2.9.13-14.el9_8.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86143 | MEDIUM4.14 | libxml2 2.9.13-14.el9_8.4 fixed in 2.9.13-14.el9_8.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86144 | MEDIUM4.14 | libxml2 2.9.13-14.el9_8.4 fixed in 2.9.13-14.el9_8.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18798 | MEDIUM4.14 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63072 | MEDIUM4.14 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-63076 | MEDIUM4.14 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-89157 | MEDIUM4.14 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-89157 | MEDIUM4.14 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM4.14 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM4.14 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-89158 | LOW3.9 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89158 | LOW3.9 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | LOW3.9 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-7774 | LOW3.9 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-77421 | LOW3.9 | org.jline:jline-builtins 3.30.4 fixed in 4.3.1, 3.30.15 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-41996 | LOW3.9 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14457 | LOW3.9 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28387 | LOW3.9 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | LOW3.9 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | LOW3.9 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | LOW3.9 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42765 | LOW3.9 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54874 | LOW3.9 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63073 | LOW3.9 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63074 | LOW3.9 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | LOW3.9 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | LOW3.9 | zlib 1.2.11-40.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-12345 | LOW3.78 | python3-libs 3.9.25-7.el9_8.3 fixed in 3.9.25-7.el9_8.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5958 | LOW3.78 | sed 4.8-10.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1757 | LOW3.72 | libxml2 2.9.13-14.el9_8.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0988 | LOW3.7 | glib2 2.68.4-19.el9_8.10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | glibc 2.34-275.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | glibc-common 2.34-275.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | glibc-minimal-langpack 2.34-275.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.7 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35191 | LOW3.7 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.7 | openssl-libs 1:3.5.5-6.el9_8 fixed in 1:3.5.8-1.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56392 | LOW3.66 | coreutils 8.32-41.el9_8 fixed in 8.32-41.el9_8.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56391 | LOW3.66 | coreutils-common 8.32-41.el9_8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-64506 | LOW3.66 | libpng 2:1.6.37-15.el9_8.2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5713 | LOW3.6 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-102633 | LOW3.54 | expat 2.5.0-6.el9_8.3 fixed in 2.5.0-6.el9_8.7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-113351 | LOW3.54 | expat 2.5.0-6.el9_8.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56412 | LOW3.54 | expat 2.5.0-6.el9_8.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46675 | LOW3.54 | libpng 2:1.6.37-15.el9_8.2 No fix yet | — | Directly Exposed |
| CVE-2026-0990 | LOW3.54 | libxml2 2.9.13-14.el9_8.4 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-32636 | LOW3.31 | glib2 2.68.4-19.el9_8.10 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | LOW3.31 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-0232 | LOW3.31 | sqlite-libs 3.34.1-11.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32776 | LOW3.3 | expat 2.5.0-6.el9_8.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | LOW3.3 | expat 2.5.0-6.el9_8.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | LOW3.3 | expat 2.5.0-6.el9_8.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | LOW3.3 | python3 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-0864 | LOW3.3 | python3 3.9.25-7.el9_8.3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-42308 | LOW3.3 | python3 3.9.25-7.el9_8.3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-25645 | LOW3.3 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41990 | LOW3.3 | libgcrypt 1.10.0-13.el9_8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW3.3 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW3.3 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW3.3 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW3.3 | sqlite-libs 3.34.1-11.el9_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40930 | LOW3.24 | libpng 2:1.6.37-15.el9_8.2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libblkid 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libmount 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libuuid 2.37.4-25.el9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | LOW3.18 | python3 3.9.25-7.el9_8.3 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-19672 | LOW3.18 | python3 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW3.18 | python3 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4360 | LOW3.18 | python3 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-45409 | LOW3.18 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106450 | LOW3.18 | at.yawk.lz4:lz4-java 1.11.1 fixed in 1.11.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-106452 | LOW3.18 | at.yawk.lz4:lz4-java 1.11.1 fixed in 1.11.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-106453 | LOW3.18 | at.yawk.lz4:lz4-java 1.11.1 fixed in 1.11.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-3360 | LOW3.15 | glib2 2.68.4-19.el9_8.10 No fix yet | 0.6% 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-2025-50181 | LOW3.11 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-50182 | LOW3.11 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-9232 | LOW3.1 | openssl-libs 1:3.5.5-6.el9_8 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-28164 | LOW3 | libpng 2:1.6.37-15.el9_8.2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88807 | LOW2.99 | libXrender 0.9.10-16.el9_8.1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-19445 | LOW2.92 | python3 3.9.25-7.el9_8.3 fixed in 3.9.25-7.el9_8.6 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | LOW2.88 | python3 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.88 | python3 3.9.25-7.el9_8.3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.82 | libblkid 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libmount 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libuuid 2.37.4-25.el9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1485 | LOW2.8 | glib2 2.68.4-19.el9_8.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18503 | LOW2.8 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-88806 | LOW2.7 | libX11 1.8.12-1.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-88806 | LOW2.7 | libX11-common 1.8.12-1.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-114613 | LOW2.7 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-57585 | LOW2.7 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-47081 | LOW2.7 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-56131 | LOW2.7 | expat 2.5.0-6.el9_8.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | LOW2.7 | python3 3.9.25-7.el9_8.3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW2.7 | python3 3.9.25-7.el9_8.3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-19553 | LOW2.66 | python3 3.9.25-7.el9_8.3 fixed in 3.9.25-7.el9_8.6 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-64505 | LOW2.64 | libpng 2:1.6.37-15.el9_8.2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34757 | LOW2.64 | libpng 2:1.6.37-15.el9_8.2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1795 | LOW2.63 | python3-libs 3.9.25-7.el9_8.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4516 | LOW2.6 | python3 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-94286 | LOW2.56 | libXtst 1.2.3-16.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-86805 | LOW2.48 | glibc 2.34-275.el9_8 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-95818 | LOW2.48 | glibc 2.34-275.el9_8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-86805 | LOW2.48 | glibc-common 2.34-275.el9_8 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-95818 | LOW2.48 | glibc-common 2.34-275.el9_8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-86805 | LOW2.48 | glibc-minimal-langpack 2.34-275.el9_8 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-95818 | LOW2.48 | glibc-minimal-langpack 2.34-275.el9_8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-88647 | LOW2.48 | gnutls 3.8.10-8.el9_8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-88648 | LOW2.48 | gnutls 3.8.10-8.el9_8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW2.48 | python3 3.9.25-7.el9_8.3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW2.48 | python3 3.9.25-7.el9_8.3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-32284 | LOW2.48 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-56109 | LOW2.45 | alsa-lib 1.2.15.3-1.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4105 | LOW2.41 | systemd-libs 252-67.el9_8.4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-94283 | LOW2.34 | libX11 1.8.12-1.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-94283 | LOW2.34 | libX11-common 1.8.12-1.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-93541 | LOW2.34 | libXi 1.7.10-8.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-93542 | LOW2.34 | libXi 1.7.10-8.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-93543 | LOW2.34 | libXi 1.7.10-8.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-93544 | LOW2.34 | libXi 1.7.10-8.el9 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-93545 | LOW2.34 | libXi 1.7.10-8.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-94281 | LOW2.34 | libXi 1.7.10-8.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW2.34 | python3 3.9.25-7.el9_8.3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7774 | LOW2.34 | python3 3.9.25-7.el9_8.3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-13346 | LOW2.34 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66382 | LOW2.34 | expat 2.5.0-6.el9_8.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-27113 | LOW2.34 | libxml2 2.9.13-14.el9_8.4 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-50495 | LOW2.34 | ncurses-base 6.2-12.20210508.el9 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-50495 | LOW2.34 | ncurses-libs 6.2-12.20210508.el9 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-41409 | LOW2.34 | pcre2 10.40-6.el9 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-89156 | LOW2.34 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-89160 | LOW2.34 | pcre2 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-41409 | LOW2.34 | pcre2-syntax 10.40-6.el9 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-89156 | LOW2.34 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-89160 | LOW2.34 | pcre2-syntax 10.40-6.el9 fixed in 10.40-7.el9_8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-3572 | LOW2.34 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-12345 | LOW2.27 | python3 3.9.25-7.el9_8.3 fixed in 3.9.25-7.el9_8.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41080 | LOW2.22 | expat 2.5.0-6.el9_8.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0989 | LOW2.22 | libxml2 2.9.13-14.el9_8.4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-106449 | LOW2.22 | at.yawk.lz4:lz4-java 1.11.1 fixed in 1.11.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-90781 | LOW2.2 | alsa-lib 1.2.15.3-1.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56391 | LOW2.2 | coreutils 8.32-41.el9_8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-94282 | LOW2.2 | libXi 1.7.10-8.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5713 | LOW2.16 | python3 3.9.25-7.el9_8.3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-45803 | LOW2.14 | python3-pip-wheel 21.3.1-2.el9_8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-67693 | LOW2.12 | gnutls 3.8.10-8.el9_8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-46195 | LOW1.99 | libgcc 11.5.0-14.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | LOW1.99 | libgcc 11.5.0-14.el9 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | LOW1.99 | libstdc++ 11.5.0-14.el9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | LOW1.99 | libstdc++ 11.5.0-14.el9 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-45322 | LOW1.99 | libxml2 2.9.13-14.el9_8.4 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-96675 | LOW1.98 | alsa-lib 1.2.15.3-1.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-94284 | LOW1.98 | libX11 1.8.12-1.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-94284 | LOW1.98 | libX11-common 1.8.12-1.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW1.98 | python3 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.98 | python3 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.98 | python3 3.9.25-7.el9_8.3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-94285 | LOW1.84 | libX11 1.8.12-1.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-94285 | LOW1.84 | libX11-common 1.8.12-1.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0992 | LOW1.74 | libxml2 2.9.13-14.el9_8.4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18503 | LOW1.68 | python3 3.9.25-7.el9_8.3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-96674 | LOW1.58 | alsa-lib 1.2.15.3-1.el9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1795 | LOW1.58 | python3 3.9.25-7.el9_8.3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-25068 | LOW1.55 | alsa-lib 1.2.15.3-1.el9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-24515 | LOW1.5 | expat 2.5.0-6.el9_8.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78667 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78669 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97031 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78659 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-94440 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-111943 | NONE0 | stdlib v1.27.1 fixed in 1.26.10, 1.27.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56866 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-94439 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-94448 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97030 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97032 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78663 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56857 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.6% 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.