Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker who exploits the top findings could bypass authentication on a protected route or exhaust worker threads on the Kafka Connect REST port, disrupting service availability. CVE-2026-75595 only applies if the Netty TLS server uses per-name SNI settings with client certificate requirements, which Kafka Connect's default listeners do not clearly show. CVE-2026-40984 only applies if Micrometer Jetty instrumentation is enabled on the HTTP server. Many exposed findings remain unresolved, so the risk depends on verifying which of these features are active in your deployment.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-75595 | HIGH7.28 | io.netty:netty-handler 4.1.136.Final fixed in 4.2.17.Final, 4.1.137.Final | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-6019 | MEDIUM6.1 | python3-libs 3.6.8-78.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89407 | MEDIUM6 | com.fasterxml.jackson.core:jackson-core 2.18.9 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.18.9 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.18.9 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.18.9 fixed in 2.18.11, 2.21.7, 2.22.3 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-91777 | MEDIUM6 | com.fasterxml.jackson.core:jackson-databind 2.18.9 fixed in 2.21.7, 2.18.11, 2.22.3 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-40984 | MEDIUM6 | io.micrometer:micrometer-core 1.14.4 fixed in 1.16.6, 1.15.12 | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-75596 | MEDIUM6 | io.netty:netty-handler 4.1.136.Final fixed in 4.2.17.Final, 4.1.137.Final | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-5713 | MEDIUM6 | python3-libs 3.6.8-78.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | glibc 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.43 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | glibc 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | glibc 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | glibc-common 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.43 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | glibc-common 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | glibc-common 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12904 | MEDIUM5.9 | libgcrypt 1.8.5-8.el8_10 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt 1.8.5-8.el8_10 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54872 | MEDIUM5.9 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-77696 | MEDIUM5.9 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-84783 | MEDIUM5.9 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM5.52 | platform-python 3.6.8-78.el8_10 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-3644 | MEDIUM5.52 | python3-libs 3.6.8-78.el8_10 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-6368 | MEDIUM5.5 | glibc 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.43 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | glibc-common 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.43 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM5.5 | python3-libs 3.6.8-78.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM5.5 | python3-libs 3.6.8-78.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42308 | MEDIUM5.5 | python3-libs 3.6.8-78.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-50812 | MEDIUM5.5 | sqlite-libs 3.26.0-21.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77420 | MEDIUM5.5 | org.jline:jline-reader 3.25.1 fixed in 4.3.1, 3.30.15 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-114406 | MEDIUM5.44 | ca-certificates 2025.2.80_v9.0.304-80.2.el8_10 fixed in 2026.2.92_v9.0.319-81.3.el8_10 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-8674 | MEDIUM5.3 | glibc 2.28-251.el8_10.40 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | glibc-common 2.28-251.el8_10.40 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-0466 | MEDIUM5.3 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-75804 | MEDIUM5.3 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM5.3 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-12781 | MEDIUM5.3 | python3-libs 3.6.8-78.el8_10 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-19672 | MEDIUM5.3 | python3-libs 3.6.8-78.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM5.3 | python3-libs 3.6.8-78.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4360 | MEDIUM5.3 | python3-libs 3.6.8-78.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM5.3 | xz-libs 5.2.4-4.el8_6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.2 | glibc 2.28-251.el8_10.40 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-4437 | MEDIUM5.2 | glibc-common 2.28-251.el8_10.40 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-11972 | MEDIUM5.2 | platform-python 3.6.8-78.el8_10 No fix yet | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-7774 | MEDIUM5.2 | platform-python 3.6.8-78.el8_10 No fix yet | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-11972 | MEDIUM5.2 | python3-libs 3.6.8-78.el8_10 No fix yet | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-7774 | MEDIUM5.2 | python3-libs 3.6.8-78.el8_10 No fix yet | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-74860 | MEDIUM5.1 | libxml2 2.9.7-21.el8_10.7 fixed in 2.9.7-21.el8_10.9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-2650 | MEDIUM5.07 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 75.4% Actively Exploited | Directly Exposed |
| CVE-2026-42250 | MEDIUM5 | bzip2-libs 1.0.6-28.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | glibc 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | glibc-common 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-19445 | MEDIUM4.86 | python3-libs 3.6.8-78.el8_10 fixed in 3.6.8-79.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-97687 | MEDIUM4.86 | urllib3 2.7.0 fixed in 2.8.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-2511 | MEDIUM4.81 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 52.4% Actively Exploited | Directly Exposed |
| CVE-2025-15282 | MEDIUM4.8 | python3-libs 3.6.8-78.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.8 | python3-libs 3.6.8-78.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-4598 | MEDIUM4.7 | systemd-libs 239-82.el8_10.19 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-86140 | MEDIUM4.68 | libxml2 2.9.7-21.el8_10.7 fixed in 2.9.7-21.el8_10.9 | 0.2% 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-107227 | MEDIUM4.5 | org.asynchttpclient:async-http-client 2.15.0 fixed in 3.0.14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107231 | MEDIUM4.5 | org.asynchttpclient:async-http-client 2.15.0 fixed in 3.0.13, 2.16.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-85721 | MEDIUM4.5 | org.asynchttpclient:async-http-client 2.15.0 fixed in 3.0.12, 2.16.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-77422 | MEDIUM4.5 | org.jline:jline-builtins 3.25.1 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.25.1 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.25.1 fixed in 4.2.1, 4.0.16, 3.30.14 | 0.6% Theoretical Threat | Directly Exposed |
| GHSA-6v7p-g79w-8964 | MEDIUM4.5 | msgpack 1.1.2 fixed in 1.2.1 | — | Directly Exposed |
| CVE-2026-97689 | MEDIUM4.5 | urllib3 2.7.0 fixed in 2.8.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-6763 | MEDIUM4.5 | org.eclipse.jetty:jetty-http 9.4.63 fixed in 12.0.12 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | MEDIUM4.5 | python3-libs 3.6.8-78.el8_10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | MEDIUM4.5 | python3-libs 3.6.8-78.el8_10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83557 | MEDIUM4.48 | 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 ExposedContext importance: MEDIUM |
| CVE-2026-19553 | MEDIUM4.44 | python3-libs 3.6.8-78.el8_10 fixed in 3.6.8-79.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107230 | MEDIUM4.44 | org.asynchttpclient:async-http-client 2.15.0 fixed in 3.0.14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4516 | MEDIUM4.33 | python3-libs 3.6.8-78.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-20839 | MEDIUM4.3 | systemd-libs 239-82.el8_10.19 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-19032 | MEDIUM4.24 | 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 ExposedContext importance: MEDIUM |
| 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-19542 | MEDIUM4.2 | glibc 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | glibc 2.28-251.el8_10.40 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | glibc-common 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | glibc-common 2.28-251.el8_10.40 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107161 | MEDIUM4.14 | cyrus-sasl-lib 2.1.27-6.el8_5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-16118 | MEDIUM4.14 | glib2 2.56.4-177.el8_10 fixed in 2.56.4-178.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM4.14 | glibc 2.28-251.el8_10.40 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.14 | glibc 2.28-251.el8_10.40 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM4.14 | glibc-common 2.28-251.el8_10.40 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.14 | glibc-common 2.28-251.el8_10.40 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-88647 | MEDIUM4.14 | gnutls 3.6.16-8.el8_10.6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88648 | MEDIUM4.14 | gnutls 3.6.16-8.el8_10.6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.14 | libgcc 8.5.0-28.el8_10 fixed in 8.5.0-30.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.14 | libgcc 8.5.0-28.el8_10 fixed in 8.5.0-30.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0966 | MEDIUM4.14 | libssh 0.9.6-17.el8_10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3731 | MEDIUM4.14 | libssh 0.9.6-17.el8_10 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-0966 | MEDIUM4.14 | libssh-config 0.9.6-17.el8_10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3731 | MEDIUM4.14 | libssh-config 0.9.6-17.el8_10 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.14 | libstdc++ 8.5.0-28.el8_10 fixed in 8.5.0-30.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.14 | libstdc++ 8.5.0-28.el8_10 fixed in 8.5.0-30.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6653 | MEDIUM4.14 | libxml2 2.9.7-21.el8_10.7 fixed in 2.9.7-21.el8_10.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86138 | MEDIUM4.14 | libxml2 2.9.7-21.el8_10.7 fixed in 2.9.7-21.el8_10.9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86142 | MEDIUM4.14 | libxml2 2.9.7-21.el8_10.7 fixed in 2.9.7-21.el8_10.10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86143 | MEDIUM4.14 | libxml2 2.9.7-21.el8_10.7 fixed in 2.9.7-21.el8_10.9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86144 | MEDIUM4.14 | libxml2 2.9.7-21.el8_10.7 fixed in 2.9.7-21.el8_10.9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63072 | MEDIUM4.14 | openssl-libs 1:1.1.1k-17.el8_6 fixed in 1:1.1.1k-18.el8_6 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM4.14 | platform-python 3.6.8-78.el8_10 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM4.14 | platform-python 3.6.8-78.el8_10 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM4.14 | python3-libs 3.6.8-78.el8_10 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM4.14 | python3-libs 3.6.8-78.el8_10 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-107280 | MEDIUM4.14 | org.asynchttpclient:async-http-client 2.15.0 fixed in 3.0.13, 2.16.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-107226 | MEDIUM4.08 | org.asynchttpclient:async-http-client 2.15.0 fixed in 3.0.14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-107228 | MEDIUM4.08 | org.asynchttpclient:async-http-client 2.15.0 fixed in 3.0.14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85717 | MEDIUM4.08 | org.asynchttpclient:async-http-client 2.15.0 fixed in 3.0.12, 2.16.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-85231 | LOW3.9 | libtirpc 1.1.4-12.el8_10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58058 | LOW3.9 | nmap-ncat 2:7.92-2.el8_10 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-72712 | LOW3.9 | nmap-ncat 2:7.92-2.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-13346 | LOW3.9 | platform-python-pip 9.0.3-24.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-13346 | LOW3.9 | python3-pip-wheel 9.0.3-24.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-107282 | LOW3.9 | org.asynchttpclient:async-http-client 2.15.0 fixed in 3.0.13, 2.16.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77421 | LOW3.9 | org.jline:jline-builtins 3.25.1 fixed in 4.3.1, 3.30.15 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.9 | glibc 2.28-251.el8_10.40 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.9 | glibc-common 2.28-251.el8_10.40 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-1000654 | LOW3.9 | libtasn1 4.13-6.el8_10 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0464 | LOW3.9 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0465 | LOW3.9 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0727 | LOW3.9 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-41996 | LOW3.9 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-15468 | LOW3.9 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-15469 | LOW3.9 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | LOW3.9 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW3.9 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | LOW3.9 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | LOW3.9 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | LOW3.9 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | LOW3.9 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | LOW3.9 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | LOW3.9 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | LOW3.9 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | LOW3.9 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | LOW3.9 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42765 | LOW3.9 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | LOW3.9 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42768 | LOW3.9 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | LOW3.9 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42771 | LOW3.9 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54874 | LOW3.9 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | LOW3.9 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | LOW3.9 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2019-9674 | LOW3.9 | python3-libs 3.6.8-78.el8_10 No fix yet | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-7592 | LOW3.9 | python3-libs 3.6.8-78.el8_10 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-6075 | LOW3.9 | python3-libs 3.6.8-78.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-19244 | LOW3.9 | sqlite-libs 3.26.0-21.el8_10 No fix yet | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9936 | LOW3.9 | sqlite-libs 3.26.0-21.el8_10 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9937 | LOW3.9 | sqlite-libs 3.26.0-21.el8_10 No fix yet | 6.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3997 | LOW3.9 | systemd-libs 239-82.el8_10.19 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-27171 | LOW3.9 | zlib 1.2.11-25.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0964 | LOW3.78 | libssh 0.9.6-17.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0964 | LOW3.78 | libssh-config 0.9.6-17.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5958 | LOW3.78 | sed 4.5-5.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-8905 | LOW3.74 | file-libs 5.33-27.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-1757 | LOW3.72 | libxml2 2.9.7-21.el8_10.7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | LOW3.72 | p11-kit 0.23.22-2.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | LOW3.72 | p11-kit-trust 0.23.22-2.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | glibc 2.28-251.el8_10.40 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | glibc-common 2.28-251.el8_10.40 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.7 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | LOW3.66 | platform-python 3.6.8-78.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6069 | LOW3.65 | python3-libs 3.6.8-78.el8_10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-8291 | LOW3.65 | python3-libs 3.6.8-78.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5713 | LOW3.6 | platform-python 3.6.8-78.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-67693 | LOW3.54 | gnutls 3.6.16-8.el8_10.6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0990 | LOW3.54 | libxml2 2.9.7-21.el8_10.7 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-54872 | LOW3.54 | openssl 1:1.1.1k-17.el8_6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-77696 | LOW3.54 | openssl 1:1.1.1k-17.el8_6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-84783 | LOW3.54 | openssl 1:1.1.1k-17.el8_6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-107285 | LOW3.54 | org.asynchttpclient:async-http-client 2.15.0 fixed in 3.0.12, 2.16.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-85720 | LOW3.54 | org.asynchttpclient:async-http-client 2.15.0 fixed in 3.0.12, 2.16.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-81642 | LOW3.53 | python3-unbound 1.16.2-5.14.el8_10 fixed in 1.16.2-5.14.el8_10.4 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-81642 | LOW3.53 | unbound-libs 1.16.2-5.14.el8_10 fixed in 1.16.2-5.14.el8_10.4 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-111497 | LOW3.35 | brotli 1.0.6-4.el8_10 No fix yet | 36.0% High Exploitation Risk | Post-Exploit |
| CVE-2025-5351 | LOW3.31 | libssh 0.9.6-17.el8_10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-5351 | LOW3.31 | libssh-config 0.9.6-17.el8_10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2020-35512 | LOW3.31 | dbus-daemon 1:1.12.8-28.el8_10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-35512 | LOW3.31 | dbus-libs 1:1.12.8-28.el8_10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-25260 | LOW3.31 | elfutils-libelf 0.190-2.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-25260 | LOW3.31 | elfutils-libs 0.190-2.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2019-8906 | LOW3.31 | file-libs 5.33-27.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | LOW3.31 | openssl-libs 1:1.1.1k-17.el8_6 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-0397 | LOW3.31 | python3-libs 3.6.8-78.el8_10 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-0232 | LOW3.31 | sqlite-libs 3.26.0-21.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-76781 | LOW3.3 | libxml2 2.9.7-21.el8_10.7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-25282 | LOW3.3 | nmap-ncat 2:7.92-2.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-13837 | LOW3.3 | platform-python 3.6.8-78.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-0864 | LOW3.3 | platform-python 3.6.8-78.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-42308 | LOW3.3 | platform-python 3.6.8-78.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-25645 | LOW3.3 | platform-python-pip 9.0.3-24.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-25645 | LOW3.3 | python3-pip-wheel 9.0.3-24.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41990 | LOW3.3 | libgcrypt 1.8.5-8.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW3.3 | python3-libs 3.6.8-78.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW3.3 | python3-libs 3.6.8-78.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW3.3 | python3-libs 3.6.8-78.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW3.3 | sqlite-libs 3.26.0-21.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| GHSA-6q48-6c7w-9gw2 | LOW3.28 | certifi 2026.6.17 fixed in 2026.10.18 | — | Post-Exploit |
| GHSA-6q48-6c7w-9gw2 | LOW3.28 | certifi 2026.7.22 fixed in 2026.10.18 | — | Post-Exploit |
| CVE-2026-1489 | LOW3.24 | glib2 2.56.4-177.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-82717 | LOW3.2 | python3-unbound 1.16.2-5.14.el8_10 fixed in 1.16.2-5.14.el8_10.4 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-82717 | LOW3.2 | unbound-libs 1.16.2-5.14.el8_10 fixed in 1.16.2-5.14.el8_10.4 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-86469 | LOW3.18 | glib2 2.56.4-177.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-85977 | LOW3.18 | libtirpc 1.1.4-12.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-0466 | LOW3.18 | openssl 1:1.1.1k-17.el8_6 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-75804 | LOW3.18 | openssl 1:1.1.1k-17.el8_6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-75806 | LOW3.18 | openssl 1:1.1.1k-17.el8_6 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-12781 | LOW3.18 | platform-python 3.6.8-78.el8_10 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-19672 | LOW3.18 | platform-python 3.6.8-78.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW3.18 | platform-python 3.6.8-78.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4360 | LOW3.18 | platform-python 3.6.8-78.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| 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-2026-97688 | LOW3.18 | urllib3 2.7.0 fixed in 2.8.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-47273 | LOW3.17 | setuptools 70.3.0 fixed in 78.1.1 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-0799 | LOW3.13 | libpcap 14:1.9.1-5.el8 fixed in 14:1.9.1-6.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-50181 | LOW3.11 | platform-python-pip 9.0.3-24.el8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-50182 | LOW3.11 | platform-python-pip 9.0.3-24.el8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-50181 | LOW3.11 | python3-pip-wheel 9.0.3-24.el8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-50182 | LOW3.11 | python3-pip-wheel 9.0.3-24.el8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63387 | LOW3.1 | libevent 2.1.8-5.el8 fixed in 2.1.8-11.el8_10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-2650 | LOW3.04 | openssl 1:1.1.1k-17.el8_6 No fix yet | 75.4% Actively Exploited | Post-Exploit |
| CVE-2026-63388 | LOW3.02 | libevent 2.1.8-5.el8 fixed in 2.1.8-11.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-77214 | LOW2.95 | expat 2.5.0-2.el8_10.2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-86145 | LOW2.95 | pcre2 10.32-3.el8_6 fixed in 10.32-4.el8_10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | LOW2.92 | curl 7.61.1-34.el8_10.13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | LOW2.92 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19445 | LOW2.92 | platform-python 3.6.8-78.el8_10 fixed in 3.6.8-79.el8_10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-2511 | LOW2.89 | openssl 1:1.1.1k-17.el8_6 No fix yet | 52.4% Actively Exploited | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | libblkid 2.32.1-48.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | libfdisk 2.32.1-48.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | libmount 2.32.1-48.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | libsmartcols 2.32.1-48.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | libuuid 2.32.1-48.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | util-linux 2.32.1-48.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | LOW2.88 | platform-python 3.6.8-78.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.88 | platform-python 3.6.8-78.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.82 | gnupg2 2.2.20-4.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18503 | LOW2.8 | python3-libs 3.6.8-78.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63382 | LOW2.77 | libevent 2.1.8-5.el8 fixed in 2.1.8-11.el8_10 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-63385 | LOW2.77 | libevent 2.1.8-5.el8 fixed in 2.1.8-11.el8_10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-103111 | LOW2.74 | pcre2 10.32-3.el8_6 fixed in 10.32-4.el8_10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW2.7 | curl 7.61.1-34.el8_10.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-66046 | LOW2.7 | expat 2.5.0-2.el8_10.2 fixed in 2.5.0-4.el8_10 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-76641 | LOW2.7 | expat 2.5.0-2.el8_10.2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-93990 | LOW2.7 | expat 2.5.0-2.el8_10.2 fixed in 2.5.0-4.el8_10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW2.7 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-63383 | LOW2.7 | libevent 2.1.8-5.el8 fixed in 2.1.8-11.el8_10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-63384 | LOW2.7 | libevent 2.1.8-5.el8 fixed in 2.1.8-11.el8_10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6554 | LOW2.7 | libpcap 14:1.9.1-5.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-81634 | LOW2.7 | python3-unbound 1.16.2-5.14.el8_10 fixed in 1.16.2-5.14.el8_10.4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-81634 | LOW2.7 | unbound-libs 1.16.2-5.14.el8_10 fixed in 1.16.2-5.14.el8_10.4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-47081 | LOW2.7 | platform-python-pip 9.0.3-24.el8 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2024-47081 | LOW2.7 | python3-pip-wheel 9.0.3-24.el8 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2025-11468 | LOW2.7 | platform-python 3.6.8-78.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW2.7 | platform-python 3.6.8-78.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-84782 | LOW2.66 | openssl 1:1.1.1k-17.el8_6 fixed in 1:1.1.1k-18.el8_6 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-84782 | LOW2.66 | openssl-libs 1:1.1.1k-17.el8_6 fixed in 1:1.1.1k-18.el8_6 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-19553 | LOW2.66 | platform-python 3.6.8-78.el8_10 fixed in 3.6.8-79.el8_10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-1795 | LOW2.63 | python3-libs 3.6.8-78.el8_10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4516 | LOW2.6 | platform-python 3.6.8-78.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | libblkid 2.32.1-48.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | libfdisk 2.32.1-48.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | libmount 2.32.1-48.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | libsmartcols 2.32.1-48.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | libuuid 2.32.1-48.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | util-linux 2.32.1-48.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-1484 | LOW2.52 | glib2 2.56.4-177.el8_10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-18739 | LOW2.5 | popt 1.18-1.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18743 | LOW2.5 | popt 1.18-1.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5773 | LOW2.48 | curl 7.61.1-34.el8_10.13 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW2.48 | curl 7.61.1-34.el8_10.13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW2.48 | curl 7.61.1-34.el8_10.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW2.48 | curl 7.61.1-34.el8_10.13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9546 | LOW2.48 | curl 7.61.1-34.el8_10.13 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-56403 | LOW2.48 | expat 2.5.0-2.el8_10.2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56404 | LOW2.48 | expat 2.5.0-2.el8_10.2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56405 | LOW2.48 | expat 2.5.0-2.el8_10.2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56406 | LOW2.48 | expat 2.5.0-2.el8_10.2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56407 | LOW2.48 | expat 2.5.0-2.el8_10.2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76957 | LOW2.48 | expat 2.5.0-2.el8_10.2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-40467 | LOW2.48 | gawk 4.2.1-4.el8 fixed in 4.2.1-5.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-40468 | LOW2.48 | gawk 4.2.1-4.el8 fixed in 4.2.1-5.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW2.48 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW2.48 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW2.48 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW2.48 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9546 | LOW2.48 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2022-4899 | LOW2.48 | libzstd 1.4.4-1.el8 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63072 | LOW2.48 | openssl 1:1.1.1k-17.el8_6 fixed in 1:1.1.1k-18.el8_6 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-89157 | LOW2.48 | pcre2 10.32-3.el8_6 fixed in 10.32-4.el8_10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-103242 | LOW2.48 | python3-rpm 4.14.3-32.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-78367 | LOW2.48 | python3-rpm 4.14.3-32.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-84837 | LOW2.48 | python3-rpm 4.14.3-32.el8_10 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-95519 | LOW2.48 | python3-rpm 4.14.3-32.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-95520 | LOW2.48 | python3-rpm 4.14.3-32.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-95521 | LOW2.48 | python3-rpm 4.14.3-32.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42960 | LOW2.48 | python3-unbound 1.16.2-5.14.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-50252 | LOW2.48 | python3-unbound 1.16.2-5.14.el8_10 fixed in 1.16.2-5.14.el8_10.2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-80225 | LOW2.48 | python3-unbound 1.16.2-5.14.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-85501 | LOW2.48 | python3-unbound 1.16.2-5.14.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-103242 | LOW2.48 | rpm 4.14.3-32.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-78367 | LOW2.48 | rpm 4.14.3-32.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-84837 | LOW2.48 | rpm 4.14.3-32.el8_10 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-95519 | LOW2.48 | rpm 4.14.3-32.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-95520 | LOW2.48 | rpm 4.14.3-32.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-95521 | LOW2.48 | rpm 4.14.3-32.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-103242 | LOW2.48 | rpm-build-libs 4.14.3-32.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-78367 | LOW2.48 | rpm-build-libs 4.14.3-32.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-84837 | LOW2.48 | rpm-build-libs 4.14.3-32.el8_10 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-95519 | LOW2.48 | rpm-build-libs 4.14.3-32.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-95520 | LOW2.48 | rpm-build-libs 4.14.3-32.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-95521 | LOW2.48 | rpm-build-libs 4.14.3-32.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-103242 | LOW2.48 | rpm-libs 4.14.3-32.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-78367 | LOW2.48 | rpm-libs 4.14.3-32.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-84837 | LOW2.48 | rpm-libs 4.14.3-32.el8_10 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-95519 | LOW2.48 | rpm-libs 4.14.3-32.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-95520 | LOW2.48 | rpm-libs 4.14.3-32.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-95521 | LOW2.48 | rpm-libs 4.14.3-32.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-29111 | LOW2.48 | systemd-libs 239-82.el8_10.19 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2005-2541 | LOW2.48 | tar 2:1.30-11.el8_10 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42960 | LOW2.48 | unbound-libs 1.16.2-5.14.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-50252 | LOW2.48 | unbound-libs 1.16.2-5.14.el8_10 fixed in 1.16.2-5.14.el8_10.2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-80225 | LOW2.48 | unbound-libs 1.16.2-5.14.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-85501 | LOW2.48 | unbound-libs 1.16.2-5.14.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-13034 | LOW2.45 | curl 7.61.1-34.el8_10.13 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW2.45 | curl 7.61.1-34.el8_10.13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-13034 | LOW2.45 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW2.45 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-22185 | LOW2.45 | openldap 2.4.46-21.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4105 | LOW2.41 | systemd-libs 239-82.el8_10.19 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8114 | LOW2.4 | libssh 0.9.6-17.el8_10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8114 | LOW2.4 | libssh-config 0.9.6-17.el8_10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-55688 | LOW2.4 | org.asynchttpclient:async-http-client 2.15.0 fixed in 3.0.11, 2.16.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63381 | LOW2.38 | libevent 2.1.8-5.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW2.34 | curl 7.61.1-34.el8_10.13 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW2.34 | curl 7.61.1-34.el8_10.13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW2.34 | curl 7.61.1-34.el8_10.13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW2.34 | curl 7.61.1-34.el8_10.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW2.34 | curl 7.61.1-34.el8_10.13 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-92388 | LOW2.34 | curl 7.61.1-34.el8_10.13 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-47268 | LOW2.34 | iputils 20180629-11.el8 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-107778 | LOW2.34 | krb5-libs 1.18.2-34.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-107778 | LOW2.34 | krb5-workstation 1.18.2-34.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4426 | LOW2.34 | libarchive 3.3.3-7.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW2.34 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW2.34 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW2.34 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW2.34 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW2.34 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-92388 | LOW2.34 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63379 | LOW2.34 | libevent 2.1.8-5.el8 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-107778 | LOW2.34 | libkadm5 1.18.2-34.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9149 | LOW2.34 | libsolv 0.7.20-7.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-89158 | LOW2.34 | pcre2 10.32-3.el8_6 fixed in 10.32-4.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-50248 | LOW2.34 | python3-unbound 1.16.2-5.14.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-33056 | LOW2.34 | tar 2:1.30-11.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-50248 | LOW2.34 | unbound-libs 1.16.2-5.14.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-10524 | LOW2.34 | wget 1.19.5-16.el8_10 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-16599 | LOW2.34 | wget 1.19.5-16.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53910 | LOW2.34 | diffutils 3.6-6.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-24883 | LOW2.34 | gnupg2 2.2.20-4.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2021-4209 | LOW2.34 | gnutls 3.6.16-8.el8_10.6 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20657 | LOW2.34 | libgcc 8.5.0-28.el8_10 No fix yet | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-14250 | LOW2.34 | libgcc 8.5.0-28.el8_10 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-0967 | LOW2.34 | libssh 0.9.6-17.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0967 | LOW2.34 | libssh-config 0.9.6-17.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-20657 | LOW2.34 | libstdc++ 8.5.0-28.el8_10 No fix yet | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-14250 | LOW2.34 | libstdc++ 8.5.0-28.el8_10 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-27113 | LOW2.34 | libxml2 2.9.7-21.el8_10.7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-19185 | LOW2.34 | ncurses-base 6.1-10.20180224.el8 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2020-19186 | LOW2.34 | ncurses-base 6.1-10.20180224.el8 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2020-19187 | LOW2.34 | ncurses-base 6.1-10.20180224.el8 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2020-19188 | LOW2.34 | ncurses-base 6.1-10.20180224.el8 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2020-19189 | LOW2.34 | ncurses-base 6.1-10.20180224.el8 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2020-19190 | LOW2.34 | ncurses-base 6.1-10.20180224.el8 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2021-39537 | LOW2.34 | ncurses-base 6.1-10.20180224.el8 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-50495 | LOW2.34 | ncurses-base 6.1-10.20180224.el8 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2020-19185 | LOW2.34 | ncurses-libs 6.1-10.20180224.el8 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2020-19186 | LOW2.34 | ncurses-libs 6.1-10.20180224.el8 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2020-19187 | LOW2.34 | ncurses-libs 6.1-10.20180224.el8 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2020-19188 | LOW2.34 | ncurses-libs 6.1-10.20180224.el8 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2020-19189 | LOW2.34 | ncurses-libs 6.1-10.20180224.el8 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2020-19190 | LOW2.34 | ncurses-libs 6.1-10.20180224.el8 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2021-39537 | LOW2.34 | ncurses-libs 6.1-10.20180224.el8 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-50495 | LOW2.34 | ncurses-libs 6.1-10.20180224.el8 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0464 | LOW2.34 | openssl 1:1.1.1k-17.el8_6 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0465 | LOW2.34 | openssl 1:1.1.1k-17.el8_6 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2024-0727 | LOW2.34 | openssl 1:1.1.1k-17.el8_6 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-41996 | LOW2.34 | openssl 1:1.1.1k-17.el8_6 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-15468 | LOW2.34 | openssl 1:1.1.1k-17.el8_6 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-15469 | LOW2.34 | openssl 1:1.1.1k-17.el8_6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68160 | LOW2.34 | openssl 1:1.1.1k-17.el8_6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69418 | LOW2.34 | openssl 1:1.1.1k-17.el8_6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69420 | LOW2.34 | openssl 1:1.1.1k-17.el8_6 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-69421 | LOW2.34 | openssl 1:1.1.1k-17.el8_6 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-22795 | LOW2.34 | openssl 1:1.1.1k-17.el8_6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-22796 | LOW2.34 | openssl 1:1.1.1k-17.el8_6 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-28387 | LOW2.34 | openssl 1:1.1.1k-17.el8_6 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-28388 | LOW2.34 | openssl 1:1.1.1k-17.el8_6 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-28389 | LOW2.34 | openssl 1:1.1.1k-17.el8_6 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-31789 | LOW2.34 | openssl 1:1.1.1k-17.el8_6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-34180 | LOW2.34 | openssl 1:1.1.1k-17.el8_6 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42765 | LOW2.34 | openssl 1:1.1.1k-17.el8_6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42766 | LOW2.34 | openssl 1:1.1.1k-17.el8_6 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42768 | LOW2.34 | openssl 1:1.1.1k-17.el8_6 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW2.34 | openssl 1:1.1.1k-17.el8_6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42771 | LOW2.34 | openssl 1:1.1.1k-17.el8_6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-54874 | LOW2.34 | openssl 1:1.1.1k-17.el8_6 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW2.34 | openssl 1:1.1.1k-17.el8_6 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW2.34 | openssl 1:1.1.1k-17.el8_6 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2019-9674 | LOW2.34 | platform-python 3.6.8-78.el8_10 No fix yet | 5.6% Low-Moderate Risk | Post-Exploit |
| CVE-2024-7592 | LOW2.34 | platform-python 3.6.8-78.el8_10 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-6075 | LOW2.34 | platform-python 3.6.8-78.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-20225 | LOW2.34 | platform-python-pip 9.0.3-24.el8 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2018-1121 | LOW2.34 | procps-ng 3.3.15-14.el8 No fix yet | 4.1% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20225 | LOW2.34 | python3-pip-wheel 9.0.3-24.el8 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-12345 | LOW2.27 | platform-python 3.6.8-78.el8_10 fixed in 3.6.8-79.el8_10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-12345 | LOW2.27 | python3-libs 3.6.8-78.el8_10 fixed in 3.6.8-79.el8_10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-92822 | LOW2.23 | libmodulemd 2.13.0-1.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-92823 | LOW2.23 | libmodulemd 2.13.0-1.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-92824 | LOW2.23 | libmodulemd 2.13.0-1.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0988 | LOW2.22 | glib2 2.56.4-177.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3832 | LOW2.22 | gnutls 3.6.16-8.el8_10.6 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-5419 | LOW2.22 | gnutls 3.6.16-8.el8_10.6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0989 | LOW2.22 | libxml2 2.9.7-21.el8_10.7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW2.22 | openssl 1:1.1.1k-17.el8_6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| 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-107283 | LOW2.22 | org.asynchttpclient:async-http-client 2.15.0 fixed in 3.0.12, 2.16.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56391 | LOW2.2 | coreutils-single 8.30-20.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31912 | LOW2.2 | libpcap 14:1.9.1-5.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-31879 | LOW2.2 | wget 1.19.5-16.el8_10 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-59890 | LOW2.2 | setuptools 70.3.0 fixed in 83.0.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-18839 | LOW2.2 | popt 1.18-1.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6069 | LOW2.19 | platform-python 3.6.8-78.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-8291 | LOW2.19 | platform-python 3.6.8-78.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW2.16 | gnupg2 2.2.20-4.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-45803 | LOW2.14 | platform-python-pip 9.0.3-24.el8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-45803 | LOW2.14 | python3-pip-wheel 9.0.3-24.el8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-102633 | LOW2.12 | expat 2.5.0-2.el8_10.2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-113351 | LOW2.12 | expat 2.5.0-2.el8_10.2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-56412 | LOW2.12 | expat 2.5.0-2.el8_10.2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-44608 | LOW2.12 | python3-unbound 1.16.2-5.14.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-44621 | LOW2.12 | python3-unbound 1.16.2-5.14.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55717 | LOW2.12 | python3-unbound 1.16.2-5.14.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55990 | LOW2.12 | python3-unbound 1.16.2-5.14.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-44608 | LOW2.12 | unbound-libs 1.16.2-5.14.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-44621 | LOW2.12 | unbound-libs 1.16.2-5.14.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55717 | LOW2.12 | unbound-libs 1.16.2-5.14.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55990 | LOW2.12 | unbound-libs 1.16.2-5.14.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15146 | LOW2.12 | wget 1.19.5-16.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-25724 | LOW2.11 | libarchive 3.3.3-7.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.05 | curl 7.61.1-34.el8_10.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.05 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2020-35512 | LOW1.99 | dbus-tools 1:1.12.8-28.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-29499 | LOW1.99 | glib2 2.56.4-177.el8_10 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-32611 | LOW1.99 | glib2 2.56.4-177.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-32636 | LOW1.99 | glib2 2.56.4-177.el8_10 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-32665 | LOW1.99 | glib2 2.56.4-177.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-30258 | LOW1.99 | gnupg2 2.2.20-4.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW1.99 | libgcc 8.5.0-28.el8_10 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | LOW1.99 | libstdc++ 8.5.0-28.el8_10 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-45322 | LOW1.99 | libxml2 2.9.7-21.el8_10.7 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2018-19211 | LOW1.99 | ncurses-base 6.1-10.20180224.el8 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2018-19211 | LOW1.99 | ncurses-libs 6.1-10.20180224.el8 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2024-13176 | LOW1.99 | openssl 1:1.1.1k-17.el8_6 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-0397 | LOW1.99 | platform-python 3.6.8-78.el8_10 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-32776 | LOW1.98 | expat 2.5.0-2.el8_10.2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-32777 | LOW1.98 | expat 2.5.0-2.el8_10.2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-32778 | LOW1.98 | expat 2.5.0-2.el8_10.2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-60753 | LOW1.98 | libarchive 3.3.3-7.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5745 | LOW1.98 | libarchive 3.3.3-7.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31911 | LOW1.98 | libpcap 14:1.9.1-5.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6244 | LOW1.98 | libpcap 14:1.9.1-5.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-82327 | LOW1.98 | libsolv 0.7.20-7.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53655 | LOW1.98 | tar 2:1.30-11.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW1.98 | tar 2:1.30-11.el8_10 fixed in 2:1.30-13.el8_10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-0965 | LOW1.98 | libssh 0.9.6-17.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0965 | LOW1.98 | libssh-config 0.9.6-17.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW1.98 | platform-python 3.6.8-78.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.98 | platform-python 3.6.8-78.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.98 | platform-python 3.6.8-78.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW1.91 | curl 7.61.1-34.el8_10.13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW1.91 | curl 7.61.1-34.el8_10.13 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW1.91 | curl 7.61.1-34.el8_10.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | libblkid 2.32.1-48.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW1.91 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW1.91 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW1.91 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | libfdisk 2.32.1-48.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | libmount 2.32.1-48.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | libsmartcols 2.32.1-48.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | libuuid 2.32.1-48.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-32792 | LOW1.91 | python3-unbound 1.16.2-5.14.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42923 | LOW1.91 | python3-unbound 1.16.2-5.14.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-50251 | LOW1.91 | python3-unbound 1.16.2-5.14.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-32792 | LOW1.91 | unbound-libs 1.16.2-5.14.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42923 | LOW1.91 | unbound-libs 1.16.2-5.14.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-50251 | LOW1.91 | unbound-libs 1.16.2-5.14.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | util-linux 2.32.1-48.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-58470 | LOW1.91 | wget 1.19.5-16.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-3360 | LOW1.89 | glib2 2.56.4-177.el8_10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-7039 | LOW1.89 | glib2 2.56.4-177.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11411 | LOW1.87 | python3-unbound 1.16.2-5.14.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11411 | LOW1.87 | unbound-libs 1.16.2-5.14.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-0968 | LOW1.86 | libssh 0.9.6-17.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0968 | LOW1.86 | libssh-config 0.9.6-17.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-4878 | LOW1.84 | libssh 0.9.6-17.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4878 | LOW1.84 | libssh-config 0.9.6-17.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56433 | LOW1.84 | shadow-utils 2:4.6-23.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-11850 | LOW1.8 | krb5-libs 1.18.2-34.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-11850 | LOW1.8 | krb5-workstation 1.18.2-34.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-11850 | LOW1.8 | libkadm5 1.18.2-34.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-18238 | LOW1.8 | libpcap 14:1.9.1-5.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-107708 | LOW1.76 | krb5-libs 1.18.2-34.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-107708 | LOW1.76 | krb5-workstation 1.18.2-34.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-107708 | LOW1.76 | libkadm5 1.18.2-34.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.74 | gnupg2 2.2.20-4.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0992 | LOW1.74 | libxml2 2.9.7-21.el8_10.7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-14017 | LOW1.73 | curl 7.61.1-34.el8_10.13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW1.73 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56416 | LOW1.73 | python3-unbound 1.16.2-5.14.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56416 | LOW1.73 | unbound-libs 1.16.2-5.14.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-45582 | LOW1.72 | tar 2:1.30-11.el8_10 fixed in 2:1.30-13.el8_10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | libblkid 2.32.1-48.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63380 | LOW1.69 | libevent 2.1.8-5.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | libfdisk 2.32.1-48.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | libmount 2.32.1-48.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | libsmartcols 2.32.1-48.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | libuuid 2.32.1-48.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-64118 | LOW1.69 | tar 2:1.30-11.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | util-linux 2.32.1-48.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gnupg2 2.2.20-4.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1485 | LOW1.68 | glib2 2.56.4-177.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18503 | LOW1.68 | platform-python 3.6.8-78.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-48964 | LOW1.62 | iputils 20180629-11.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-56131 | LOW1.62 | expat 2.5.0-2.el8_10.2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-7264 | LOW1.61 | curl 7.61.1-34.el8_10.13 No fix yet | 20.2% High Exploitation Risk | Post-Exploit |
| CVE-2024-7264 | LOW1.61 | libcurl 7.61.1-34.el8_10.13 No fix yet | 20.2% High Exploitation Risk | Post-Exploit |
| CVE-2026-77955 | LOW1.58 | python3-unbound 1.16.2-5.14.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18477 | LOW1.58 | tar 2:1.30-11.el8_10 fixed in 2:1.30-13.el8_10 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW1.58 | tar 2:1.30-11.el8_10 fixed in 2:1.30-13.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-77955 | LOW1.58 | unbound-libs 1.16.2-5.14.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8277 | LOW1.58 | libssh 0.9.6-17.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-8277 | LOW1.58 | libssh-config 0.9.6-17.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1795 | LOW1.58 | platform-python 3.6.8-78.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-18313 | LOW1.55 | libpcap 14:1.9.1-5.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-27534 | LOW1.4 | curl 7.61.1-34.el8_10.13 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2024-11053 | LOW1.4 | curl 7.61.1-34.el8_10.13 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-14524 | LOW1.4 | curl 7.61.1-34.el8_10.13 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | LOW1.4 | curl 7.61.1-34.el8_10.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW1.4 | curl 7.61.1-34.el8_10.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW1.4 | curl 7.61.1-34.el8_10.13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-86414 | LOW1.4 | curl 7.61.1-34.el8_10.13 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-92390 | LOW1.4 | curl 7.61.1-34.el8_10.13 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66382 | LOW1.4 | expat 2.5.0-2.el8_10.2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2018-1000879 | LOW1.4 | libarchive 3.3.3-7.el8_10 No fix yet | 3.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-1000880 | LOW1.4 | libarchive 3.3.3-7.el8_10 No fix yet | 4.1% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27534 | LOW1.4 | libcurl 7.61.1-34.el8_10.13 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2024-11053 | LOW1.4 | libcurl 7.61.1-34.el8_10.13 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-14524 | LOW1.4 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | LOW1.4 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW1.4 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW1.4 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-86414 | LOW1.4 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-92390 | LOW1.4 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-41409 | LOW1.4 | pcre2 10.32-3.el8_6 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-44605 | LOW1.4 | python3-rpm 4.14.3-32.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2019-16866 | LOW1.4 | python3-unbound 1.16.2-5.14.el8_10 No fix yet | 3.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-44605 | LOW1.4 | rpm 4.14.3-32.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-44605 | LOW1.4 | rpm-build-libs 4.14.3-32.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-44605 | LOW1.4 | rpm-libs 4.14.3-32.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2019-9923 | LOW1.4 | tar 2:1.30-11.el8_10 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-16866 | LOW1.4 | unbound-libs 1.16.2-5.14.el8_10 No fix yet | 3.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-5278 | LOW1.34 | coreutils-single 8.30-20.el8_10 fixed in 8.30-21.el8_10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW1.33 | curl 7.61.1-34.el8_10.13 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.33 | curl 7.61.1-34.el8_10.13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-87864 | LOW1.33 | curl 7.61.1-34.el8_10.13 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-92389 | LOW1.33 | curl 7.61.1-34.el8_10.13 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-92391 | LOW1.33 | curl 7.61.1-34.el8_10.13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41080 | LOW1.33 | expat 2.5.0-2.el8_10.2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW1.33 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.33 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-87864 | LOW1.33 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-92389 | LOW1.33 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-92391 | LOW1.33 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-33655 | LOW1.33 | python3-unbound 1.16.2-5.14.el8_10 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42955 | LOW1.33 | python3-unbound 1.16.2-5.14.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-44687 | LOW1.33 | python3-unbound 1.16.2-5.14.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46582 | LOW1.33 | python3-unbound 1.16.2-5.14.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-50046 | LOW1.33 | python3-unbound 1.16.2-5.14.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-50243 | LOW1.33 | python3-unbound 1.16.2-5.14.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-33655 | LOW1.33 | unbound-libs 1.16.2-5.14.el8_10 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42955 | LOW1.33 | unbound-libs 1.16.2-5.14.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-44687 | LOW1.33 | unbound-libs 1.16.2-5.14.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46582 | LOW1.33 | unbound-libs 1.16.2-5.14.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-50046 | LOW1.33 | unbound-libs 1.16.2-5.14.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-50243 | LOW1.33 | unbound-libs 1.16.2-5.14.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-17591 | LOW1.3 | libarchive 3.3.3-7.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57970 | LOW1.22 | libarchive 3.3.3-7.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-4156 | LOW1.19 | gawk 4.2.1-4.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-1632 | LOW1.19 | libarchive 3.3.3-7.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5915 | LOW1.19 | libarchive 3.3.3-7.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5916 | LOW1.19 | libarchive 3.3.3-7.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5917 | LOW1.19 | libarchive 3.3.3-7.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5918 | LOW1.19 | libarchive 3.3.3-7.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-24032 | LOW1.19 | libzstd 1.4.4-1.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-43168 | LOW1.19 | python3-unbound 1.16.2-5.14.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-43168 | LOW1.19 | unbound-libs 1.16.2-5.14.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-20193 | LOW1.19 | tar 2:1.30-11.el8_10 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-82209 | LOW1.12 | curl 7.61.1-34.el8_10.13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-82209 | LOW1.12 | libcurl 7.61.1-34.el8_10.13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-55708 | LOW1.12 | python3-unbound 1.16.2-5.14.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55708 | LOW1.12 | unbound-libs 1.16.2-5.14.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-39804 | LOW1.01 | tar 2:1.30-11.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-24515 | LOW0.9 | expat 2.5.0-2.el8_10.2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43167 | LOW0.86 | python3-unbound 1.16.2-5.14.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-43167 | LOW0.86 | unbound-libs 1.16.2-5.14.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11961 | LOW0.68 | libpcap 14:1.9.1-5.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| GHSA-xmj3-9gf7-h52w | LOW0.36 | setuptools 70.3.0 fixed in 84.1.0 | — | Post-Exploit |
| GHSA-xmj3-9gf7-h52w | LOW0.36 | setuptools 84.0.0 fixed in 84.1.0 | — | Post-Exploit |
| CVE-2026-86805 | NONE0 | glibc-minimal-langpack 2.28-251.el8_10.40 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-95818 | NONE0 | glibc-minimal-langpack 2.28-251.el8_10.40 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-29111 | NONE0 | systemd 239-82.el8_10.19 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-29111 | NONE0 | systemd-pam 239-82.el8_10.19 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4105 | NONE0 | systemd 239-82.el8_10.19 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4105 | NONE0 | systemd-pam 239-82.el8_10.19 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4437 | NONE0 | glibc-minimal-langpack 2.28-251.el8_10.40 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-12610 | NONE0 | pam 1.3.1-40.el8_10 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6791 | NONE0 | glibc-minimal-langpack 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.43 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-77117 | NONE0 | glibc-minimal-langpack 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80489 | NONE0 | glibc-minimal-langpack 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-19617 | NONE0 | device-mapper 8:1.02.181-15.el8_10.3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-19617 | NONE0 | device-mapper-libs 8:1.02.181-15.el8_10.3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6368 | NONE0 | glibc-minimal-langpack 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.43 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-8674 | NONE0 | glibc-minimal-langpack 2.28-251.el8_10.40 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-18374 | NONE0 | glibc-minimal-langpack 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-4598 | NONE0 | systemd 239-82.el8_10.19 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-4598 | NONE0 | systemd-pam 239-82.el8_10.19 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2018-20839 | NONE0 | systemd 239-82.el8_10.19 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-20839 | NONE0 | systemd-pam 239-82.el8_10.19 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-19542 | NONE0 | glibc-minimal-langpack 2.28-251.el8_10.40 fixed in 2.28-251.el8_10.48 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89092 | NONE0 | glibc-minimal-langpack 2.28-251.el8_10.40 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-35512 | NONE0 | dbus 1:1.12.8-28.el8_10 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-35512 | NONE0 | dbus-common 1:1.12.8-28.el8_10 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-25260 | NONE0 | elfutils-default-yama-scope 0.190-2.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-4438 | NONE0 | glibc-minimal-langpack 2.28-251.el8_10.40 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-3997 | NONE0 | systemd 239-82.el8_10.19 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-3997 | NONE0 | systemd-pam 239-82.el8_10.19 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2026-97399 | NONE0 | glibc-minimal-langpack 2.28-251.el8_10.40 No fix yet | 0.3% 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.