Last scanned:
This image poses a critical security risk and must not be used in production, especially as an internet-facing service. An attacker could smuggle a second HTTP request through the Control Center web UI on port 9021 via CVE-2026-2332, potentially bypassing access rules and reaching management functions and the data behind them. CVE-2026-42581 only matters if a Netty-based HTTP server handles this port behind a trusting proxy, a configuration that is not confirmed here. With 833 exposed findings, 24 of them at severity 7.0 or higher, the image cannot be treated as production-ready regardless of how any single item's reachability is resolved.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-2332 | CRITICAL9.1 | org.eclipse.jetty:jetty-http 9.4.57.v20241219 fixed in 12.1.7, 12.0.33, 11.0.29, 10.0.28, 9.4.60 | 1.3% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2026-42581 | HIGH7.84 | io.netty:netty-codec-http 4.1.115.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42581 | HIGH7.84 | io.netty:netty-codec-http 4.1.118.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54399 | HIGH7.5 | org.apache.httpcomponents.core5:httpcore5 5.2 fixed in 5.4.3, 5.5-beta2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-54428 | HIGH7.5 | org.apache.httpcomponents.core5:httpcore5-h2 5.2 fixed in 5.4.3, 5.5-beta2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-24308 | HIGH7.5 | org.apache.zookeeper:zookeeper 3.8.4 fixed in 3.9.5, 3.8.6 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107227 | HIGH7.5 | org.asynchttpclient:async-http-client 2.12.4 fixed in 3.0.14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107231 | HIGH7.5 | org.asynchttpclient:async-http-client 2.12.4 fixed in 3.0.13, 2.16.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-85721 | HIGH7.5 | org.asynchttpclient:async-http-client 2.12.4 fixed in 3.0.12, 2.16.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-29371 | HIGH7.5 | org.bitbucket.b_c:jose4j 0.9.5 fixed in 0.9.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5115 | HIGH7.5 | org.eclipse.jetty.http2:http2-common 9.4.57.v20241219 fixed in 9.4.58, 10.0.26, 11.0.26 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-66566 | HIGH7.5 | org.lz4:lz4-java 1.8.0 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-111497 | HIGH7.45 | brotli 1.0.6-3.el8 No fix yet | 36.0% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-84782 | HIGH7.4 | openssl-libs 1:1.1.1k-14.el8_6 fixed in 1:1.1.1k-18.el8_6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-24281 | HIGH7.4 | org.apache.zookeeper:zookeeper 3.8.4 fixed in 3.8.6, 3.9.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-107230 | HIGH7.4 | org.asynchttpclient:async-http-client 2.12.4 fixed in 3.0.14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45300 | HIGH7.4 | org.asynchttpclient:async-http-client 2.12.4 fixed in 3.0.10, 2.15.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11940 | HIGH7.3 | python39-setuptools-wheel 50.3.2-6.module+el8.10.0+22183+c898c0c1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42584 | HIGH7.28 | io.netty:netty-codec-http 4.1.115.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42584 | HIGH7.28 | io.netty:netty-codec-http 4.1.118.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-10050 | HIGH7.28 | org.eclipse.jetty:jetty-security 9.4.57.v20241219 fixed in 9.4.63, 10.0.31, 11.0.31, 12.0.36, 12.1.10 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-94286 | HIGH7.1 | libXtst 1.2.3-7.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4878 | HIGH7 | libcap 2.48-6.el8_9 fixed in 2.48-6.el8_10.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-106451 | HIGH7 | org.lz4:lz4-java 1.8.0 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-107161 | MEDIUM6.9 | cyrus-sasl-lib 2.1.27-6.el8_5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM6.9 | glibc 2.28-251.el8_10.16 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM6.9 | glibc 2.28-251.el8_10.16 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM6.9 | glibc-common 2.28-251.el8_10.16 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM6.9 | glibc-common 2.28-251.el8_10.16 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM6.9 | glibc-langpack-en 2.28-251.el8_10.16 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM6.9 | glibc-langpack-en 2.28-251.el8_10.16 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM6.9 | glibc-minimal-langpack 2.28-251.el8_10.16 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM6.9 | glibc-minimal-langpack 2.28-251.el8_10.16 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM6.9 | libgcc 8.5.0-26.el8_10 fixed in 8.5.0-30.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.9 | libgcc 8.5.0-26.el8_10 fixed in 8.5.0-30.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41989 | MEDIUM6.9 | libgcrypt 1.8.5-7.el8_6 fixed in 1.8.5-8.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48864 | MEDIUM6.9 | libsolv 0.7.20-6.el8 fixed in 0.7.20-7.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5318 | MEDIUM6.9 | libssh 0.9.6-14.el8 fixed in 0.9.6-15.el8_10 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-0966 | MEDIUM6.9 | libssh 0.9.6-14.el8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3731 | MEDIUM6.9 | libssh 0.9.6-14.el8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-59847 | MEDIUM6.9 | libssh 0.9.6-14.el8 fixed in 0.9.6-17.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59850 | MEDIUM6.9 | libssh 0.9.6-14.el8 fixed in 0.9.6-17.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5318 | MEDIUM6.9 | libssh-config 0.9.6-14.el8 fixed in 0.9.6-15.el8_10 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-0966 | MEDIUM6.9 | libssh-config 0.9.6-14.el8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3731 | MEDIUM6.9 | libssh-config 0.9.6-14.el8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-59847 | MEDIUM6.9 | libssh-config 0.9.6-14.el8 fixed in 0.9.6-17.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59850 | MEDIUM6.9 | libssh-config 0.9.6-14.el8 fixed in 0.9.6-17.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM6.9 | libstdc++ 8.5.0-26.el8_10 fixed in 8.5.0-30.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.9 | libstdc++ 8.5.0-26.el8_10 fixed in 8.5.0-30.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-4899 | MEDIUM6.9 | libzstd 1.4.4-1.el8 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.9 | openssl-libs 1:1.1.1k-14.el8_6 fixed in 1:1.1.1k-15.el8_6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.9 | openssl-libs 1:1.1.1k-14.el8_6 fixed in 1:1.1.1k-17.el8_6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-63072 | MEDIUM6.9 | openssl-libs 1:1.1.1k-14.el8_6 fixed in 1:1.1.1k-18.el8_6 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-47273 | MEDIUM6.9 | python3-setuptools-wheel 39.2.0-8.el8_10 fixed in 39.2.0-9.el8_10 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0391 | MEDIUM6.9 | python39-setuptools-wheel 50.3.2-6.module+el8.10.0+22183+c898c0c1 No fix yet | 8.5% Low-Moderate Risk | Directly Exposed |
| CVE-2025-47273 | MEDIUM6.9 | python39-setuptools-wheel 50.3.2-6.module+el8.10.0+22183+c898c0c1 fixed in 50.3.2-7.module+el8.10.0+23406+03055bfb | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.9 | systemd-libs 239-82.el8_10.5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-107280 | MEDIUM6.9 | org.asynchttpclient:async-http-client 2.12.4 fixed in 3.0.13, 2.16.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56109 | MEDIUM6.8 | alsa-lib 1.2.10-2.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-114406 | MEDIUM6.8 | ca-certificates 2024.2.69_v8.0.303-80.0.el8_10 fixed in 2026.2.92_v9.0.319-81.3.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22185 | MEDIUM6.8 | openldap 2.4.46-21.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-0938 | MEDIUM6.8 | python39-setuptools-wheel 50.3.2-6.module+el8.10.0+22183+c898c0c1 fixed in 50.3.2-7.module+el8.10.0+23406+03055bfb | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107226 | MEDIUM6.8 | org.asynchttpclient:async-http-client 2.12.4 fixed in 3.0.14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-107228 | MEDIUM6.8 | org.asynchttpclient:async-http-client 2.12.4 fixed in 3.0.14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-40490 | MEDIUM6.8 | org.asynchttpclient:async-http-client 2.12.4 fixed in 3.0.9, 2.14.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM6.7 | systemd-libs 239-82.el8_10.5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28684 | MEDIUM6.6 | python-dotenv 0.21.1 fixed in 1.2.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86145 | MEDIUM6.56 | pcre2 10.32-3.el8_6 fixed in 10.32-4.el8_10 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-4437 | MEDIUM6.5 | glibc 2.28-251.el8_10.16 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM6.5 | glibc 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM6.5 | glibc-common 2.28-251.el8_10.16 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM6.5 | glibc-common 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM6.5 | glibc-langpack-en 2.28-251.el8_10.16 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM6.5 | glibc-langpack-en 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM6.5 | glibc-minimal-langpack 2.28-251.el8_10.16 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM6.5 | glibc-minimal-langpack 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-93541 | MEDIUM6.5 | libXi 1.7.10-1.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93542 | MEDIUM6.5 | libXi 1.7.10-1.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93543 | MEDIUM6.5 | libXi 1.7.10-1.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93544 | MEDIUM6.5 | libXi 1.7.10-1.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93545 | MEDIUM6.5 | libXi 1.7.10-1.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94281 | MEDIUM6.5 | libXi 1.7.10-1.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-9149 | MEDIUM6.5 | libsolv 0.7.20-6.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59843 | MEDIUM6.5 | libssh 0.9.6-14.el8 fixed in 0.9.6-17.el8_10 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-59844 | MEDIUM6.5 | libssh 0.9.6-14.el8 fixed in 0.9.6-17.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-59843 | MEDIUM6.5 | libssh-config 0.9.6-14.el8 fixed in 0.9.6-17.el8_10 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-59844 | MEDIUM6.5 | libssh-config 0.9.6-14.el8 fixed in 0.9.6-17.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-85231 | MEDIUM6.5 | libtirpc 1.1.4-12.el8_10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM6.5 | python3-libs 3.6.8-69.el8_10 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-7774 | MEDIUM6.5 | python3-libs 3.6.8-69.el8_10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-13346 | MEDIUM6.5 | python3-pip-wheel 9.0.3-24.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-48924 | MEDIUM6.5 | org.apache.commons:commons-lang3 3.12.0 fixed in 3.18.0 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-48924 | MEDIUM6.5 | org.apache.commons:commons-lang3 3.13.0 fixed in 3.18.0 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107282 | MEDIUM6.5 | org.asynchttpclient:async-http-client 2.12.4 fixed in 3.0.13, 2.16.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11143 | MEDIUM6.5 | org.eclipse.jetty:jetty-http 9.4.57.v20241219 fixed in 12.0.31, 12.1.5 | 0.2% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2025-12183 | MEDIUM6.5 | org.lz4:lz4-java 1.8.0 fixed in 1.8.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-59949 | MEDIUM6.5 | org.lz4:lz4-java 1.8.0 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54512 | MEDIUM6.48 | com.fasterxml.jackson.core:jackson-databind 2.16.0 fixed in 2.18.8, 3.1.4, 2.21.4 | 0.9% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54513 | MEDIUM6.48 | com.fasterxml.jackson.core:jackson-databind 2.16.0 fixed in 2.18.8, 2.21.4, 3.1.4 | 1.2% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2024-12718 | MEDIUM6.46 | python3-libs 3.6.8-69.el8_10 fixed in 3.6.8-70.el8_10 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | MEDIUM6.3 | libattr 2.4.48-3.el8 fixed in 2.6.0-1.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0964 | MEDIUM6.3 | libssh 0.9.6-14.el8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0964 | MEDIUM6.3 | libssh-config 0.9.6-14.el8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-12345 | MEDIUM6.3 | python3-libs 3.6.8-69.el8_10 fixed in 3.6.8-79.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92822 | MEDIUM6.2 | libmodulemd 2.13.0-1.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-92823 | MEDIUM6.2 | libmodulemd 2.13.0-1.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-92824 | MEDIUM6.2 | libmodulemd 2.13.0-1.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | MEDIUM6.2 | p11-kit 0.23.22-2.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | MEDIUM6.2 | p11-kit-trust 0.23.22-2.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90781 | MEDIUM6.1 | alsa-lib 1.2.10-2.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94282 | MEDIUM6.1 | libXi 1.7.10-1.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM6.1 | python3-libs 3.6.8-69.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-103111 | MEDIUM6.08 | pcre2 10.32-3.el8_6 fixed in 10.32-4.el8_10 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-45674 | MEDIUM6 | io.netty:netty-resolver-dns 4.1.115.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47691 | MEDIUM6 | io.netty:netty-resolver-dns 4.1.115.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6965 | MEDIUM6 | sqlite-libs 3.26.0-19.el8_9 fixed in 3.26.0-20.el8_10 | 73.5% Actively Exploited | Directly Exposed |
| CVE-2025-6176 | MEDIUM6 | brotli 1.0.6-3.el8 fixed in 1.0.6-4.el8_10 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-68494 | MEDIUM6 | com.fasterxml.jackson.core:jackson-core 2.16.0 fixed in 2.18.8, 2.21.4 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-68497 | MEDIUM6 | com.fasterxml.jackson.core:jackson-databind 2.16.0 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.16.0 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.16.0 fixed in 2.21.7, 2.18.11, 2.22.3 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-55163 | MEDIUM6 | io.grpc:grpc-netty-shaded 1.66.0 fixed in 1.75.0 | 1.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42583 | MEDIUM6 | io.netty:netty-codec 4.1.115.Final fixed in 4.1.133.Final | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-59901 | MEDIUM6 | io.netty:netty-codec 4.1.115.Final fixed in 4.1.136.Final | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42583 | MEDIUM6 | io.netty:netty-codec 4.1.118.Final fixed in 4.1.133.Final | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-59901 | MEDIUM6 | io.netty:netty-codec 4.1.118.Final fixed in 4.1.136.Final | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33870 | MEDIUM6 | io.netty:netty-codec-http 4.1.115.Final fixed in 4.1.132.Final, 4.2.10.Final | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42587 | MEDIUM6 | io.netty:netty-codec-http 4.1.115.Final fixed in 4.2.13.Final, 4.1.133.Final | 1.0% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-55831 | MEDIUM6 | io.netty:netty-codec-http 4.1.115.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-55833 | MEDIUM6 | io.netty:netty-codec-http 4.1.115.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56745 | MEDIUM6 | io.netty:netty-codec-http 4.1.115.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42585 | MEDIUM6 | io.netty:netty-codec-http 4.1.115.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-59898 | MEDIUM6 | io.netty:netty-codec-http 4.1.115.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-59899 | MEDIUM6 | io.netty:netty-codec-http 4.1.115.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-59903 | MEDIUM6 | io.netty:netty-codec-http 4.1.115.Final fixed in 4.2.17.Final, 4.1.137.Final | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33870 | MEDIUM6 | io.netty:netty-codec-http 4.1.118.Final fixed in 4.1.132.Final, 4.2.10.Final | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42587 | MEDIUM6 | io.netty:netty-codec-http 4.1.118.Final fixed in 4.2.13.Final, 4.1.133.Final | 1.0% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-55831 | MEDIUM6 | io.netty:netty-codec-http 4.1.118.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-55833 | MEDIUM6 | io.netty:netty-codec-http 4.1.118.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56745 | MEDIUM6 | io.netty:netty-codec-http 4.1.118.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42585 | MEDIUM6 | io.netty:netty-codec-http 4.1.118.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-59898 | MEDIUM6 | io.netty:netty-codec-http 4.1.118.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-59899 | MEDIUM6 | io.netty:netty-codec-http 4.1.118.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-59903 | MEDIUM6 | io.netty:netty-codec-http 4.1.118.Final fixed in 4.2.17.Final, 4.1.137.Final | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-55163 | MEDIUM6 | io.netty:netty-codec-http2 4.1.115.Final fixed in 4.2.4.Final, 4.1.124.Final | 1.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33871 | MEDIUM6 | io.netty:netty-codec-http2 4.1.115.Final fixed in 4.1.132.Final, 4.2.11.Final | 1.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42587 | MEDIUM6 | io.netty:netty-codec-http2 4.1.115.Final fixed in 4.2.13.Final, 4.1.133.Final | 1.0% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56819 | MEDIUM6 | io.netty:netty-codec-http2 4.1.115.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-48043 | MEDIUM6 | io.netty:netty-codec-http2 4.1.115.Final fixed in 4.1.135.Final, 4.2.15.Final | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-5713 | MEDIUM6 | python3-libs 3.6.8-69.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.9 | glibc 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.40 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | glibc 2.28-251.el8_10.16 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.16 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.16 fixed in 2.28-251.el8_10.48 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.9 | glibc-common 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.40 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | glibc-common 2.28-251.el8_10.16 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.16 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.16 fixed in 2.28-251.el8_10.48 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.9 | glibc-langpack-en 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.40 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | glibc-langpack-en 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.43 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | glibc-langpack-en 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.48 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | glibc-langpack-en 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.48 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.9 | glibc-minimal-langpack 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.40 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | glibc-minimal-langpack 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.43 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | glibc-minimal-langpack 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.48 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | glibc-minimal-langpack 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.48 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12904 | MEDIUM5.9 | libgcrypt 1.8.5-7.el8_6 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt 1.8.5-7.el8_6 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-59845 | MEDIUM5.9 | libssh 0.9.6-14.el8 fixed in 0.9.6-17.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-59845 | MEDIUM5.9 | libssh-config 0.9.6-14.el8 fixed in 0.9.6-17.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54872 | MEDIUM5.9 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-77696 | MEDIUM5.9 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-84783 | MEDIUM5.9 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-107285 | MEDIUM5.9 | org.asynchttpclient:async-http-client 2.12.4 fixed in 3.0.12, 2.16.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-85720 | MEDIUM5.9 | org.asynchttpclient:async-http-client 2.12.4 fixed in 3.0.12, 2.16.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41409 | MEDIUM5.88 | org.apache.mina:mina-core 2.2.4 fixed in 2.0.28, 2.1.11, 2.2.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41635 | MEDIUM5.88 | org.apache.mina:mina-core 2.2.4 fixed in 2.0.28, 2.1.11, 2.2.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42778 | MEDIUM5.88 | org.apache.mina:mina-core 2.2.4 fixed in 2.1.12, 2.2.7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42779 | MEDIUM5.88 | org.apache.mina:mina-core 2.2.4 fixed in 2.1.12, 2.2.7 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-47065 | MEDIUM5.88 | org.apache.mina:mina-core 2.2.4 fixed in 2.2.8, 2.1.13, 2.0.29 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.87 | glibc 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.22 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.87 | glibc-common 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.22 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.87 | glibc-langpack-en 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.22 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.87 | glibc-minimal-langpack 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.22 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-5372 | MEDIUM5.87 | libssh 0.9.6-14.el8 fixed in 0.9.6-16.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-5372 | MEDIUM5.87 | libssh-config 0.9.6-14.el8 fixed in 0.9.6-16.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-4330 | MEDIUM5.87 | python3-libs 3.6.8-69.el8_10 fixed in 3.6.8-70.el8_10 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-4435 | MEDIUM5.87 | python3-libs 3.6.8-69.el8_10 fixed in 3.6.8-70.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-8194 | MEDIUM5.87 | python3-libs 3.6.8-69.el8_10 fixed in 3.6.8-71.el8_10 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-9287 | MEDIUM5.87 | python39-libs 3.9.20-1.module+el8.10.0+22342+478c159e fixed in 3.9.25-2.module+el8.10.0+23718+1842ae33 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4330 | MEDIUM5.87 | python39-libs 3.9.20-1.module+el8.10.0+22342+478c159e fixed in 3.9.25-2.module+el8.10.0+23718+1842ae33 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-4435 | MEDIUM5.87 | python39-libs 3.9.20-1.module+el8.10.0+22342+478c159e fixed in 3.9.25-2.module+el8.10.0+23718+1842ae33 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-8194 | MEDIUM5.87 | python39-libs 3.9.20-1.module+el8.10.0+22342+478c159e fixed in 3.9.20-2.module+el8.10.0+23441+1124c1da | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-9287 | MEDIUM5.87 | python39-setuptools-wheel 50.3.2-6.module+el8.10.0+22183+c898c0c1 fixed in 50.3.2-7.module+el8.10.0+23406+03055bfb | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4330 | MEDIUM5.87 | python39-setuptools-wheel 50.3.2-6.module+el8.10.0+22183+c898c0c1 fixed in 50.3.2-7.module+el8.10.0+23406+03055bfb | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-4435 | MEDIUM5.87 | python39-setuptools-wheel 50.3.2-6.module+el8.10.0+22183+c898c0c1 fixed in 50.3.2-7.module+el8.10.0+23406+03055bfb | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-8194 | MEDIUM5.87 | python39-setuptools-wheel 50.3.2-6.module+el8.10.0+22183+c898c0c1 fixed in 50.3.2-7.module+el8.10.0+23406+03055bfb | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-49919 | MEDIUM5.8 | freetype 2.9.1-10.el8_10 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | openssl-libs 1:1.1.1k-14.el8_6 fixed in 1:1.1.1k-14.el8_10 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-89157 | MEDIUM5.52 | pcre2 10.32-3.el8_6 fixed in 10.32-4.el8_10 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-3644 | MEDIUM5.52 | platform-python 3.6.8-69.el8_10 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-3644 | MEDIUM5.52 | python3-libs 3.6.8-69.el8_10 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-5351 | MEDIUM5.52 | libssh 0.9.6-14.el8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-5351 | MEDIUM5.52 | libssh-config 0.9.6-14.el8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-96675 | MEDIUM5.5 | alsa-lib 1.2.10-2.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-19617 | MEDIUM5.5 | device-mapper-libs 8:1.02.181-15.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95512 | MEDIUM5.5 | freetype 2.9.1-10.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | glibc 2.28-251.el8_10.16 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.16 fixed in 2.28-251.el8_10.43 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | glibc-langpack-en 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.43 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | glibc-minimal-langpack 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.43 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-82327 | MEDIUM5.5 | libsolv 0.7.20-6.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM5.5 | python3-libs 3.6.8-69.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM5.5 | python3-libs 3.6.8-69.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42308 | MEDIUM5.5 | python3-libs 3.6.8-69.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-25645 | MEDIUM5.5 | python3-pip-wheel 9.0.3-24.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25645 | MEDIUM5.5 | requests 2.32.3 fixed in 2.33.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-24049 | MEDIUM5.5 | wheel 0.43.0 fixed in 0.46.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42579 | MEDIUM5.46 | io.netty:netty-codec-dns 4.1.115.Final fixed in 4.2.13.Final, 4.1.133.Final | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-75595 | MEDIUM5.46 | io.netty:netty-handler 4.1.115.Final fixed in 4.2.17.Final, 4.1.137.Final | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75595 | MEDIUM5.46 | io.netty:netty-handler 4.1.118.Final fixed in 4.2.17.Final, 4.1.137.Final | 0.3% Theoretical Threat | Directly Exposed |
| GHSA-6q48-6c7w-9gw2 | MEDIUM5.46 | certifi 2025.1.31 fixed in 2026.10.18 | — | Directly Exposed |
| CVE-2026-58016 | MEDIUM5.34 | glib2 2.56.4-165.el8_10 fixed in 2.56.4-170.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33845 | MEDIUM5.34 | gnutls 3.6.16-8.el8_10.3 fixed in 3.6.16-8.el8_10.6 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42010 | MEDIUM5.34 | gnutls 3.6.16-8.el8_10.3 fixed in 3.6.16-8.el8_10.6 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-49796 | MEDIUM5.34 | libxml2 2.9.7-19.el8_10 fixed in 2.9.7-21.el8_10.1 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-23865 | MEDIUM5.3 | freetype 2.9.1-10.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM5.3 | glibc 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.31 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM5.3 | glibc 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.37 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | glibc 2.28-251.el8_10.16 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM5.3 | glibc-common 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.31 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM5.3 | glibc-common 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.37 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | glibc-common 2.28-251.el8_10.16 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM5.3 | glibc-langpack-en 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.31 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM5.3 | glibc-langpack-en 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.37 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | glibc-langpack-en 2.28-251.el8_10.16 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM5.3 | glibc-minimal-langpack 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.31 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM5.3 | glibc-minimal-langpack 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.37 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | glibc-minimal-langpack 2.28-251.el8_10.16 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59848 | MEDIUM5.3 | libssh 0.9.6-14.el8 fixed in 0.9.6-17.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59848 | MEDIUM5.3 | libssh-config 0.9.6-14.el8 fixed in 0.9.6-17.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85977 | MEDIUM5.3 | libtirpc 1.1.4-12.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-0466 | MEDIUM5.3 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-75804 | MEDIUM5.3 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM5.3 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-12084 | MEDIUM5.3 | python3-libs 3.6.8-69.el8_10 fixed in 3.6.8-72.el8_10 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM5.3 | python3-libs 3.6.8-69.el8_10 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-19672 | MEDIUM5.3 | python3-libs 3.6.8-69.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM5.3 | python3-libs 3.6.8-69.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4360 | MEDIUM5.3 | python3-libs 3.6.8-69.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-45292 | MEDIUM5.3 | io.opentelemetry:opentelemetry-api 1.39.0 fixed in 1.62.0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-64607 | MEDIUM5.3 | org.apache.httpcomponents.client5:httpclient5 5.2.1 fixed in 5.6.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6790 | MEDIUM5.3 | org.eclipse.jetty:jetty-server 9.4.57.v20241219 fixed in 12.0.35, 12.1.9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-106450 | MEDIUM5.3 | org.lz4:lz4-java 1.8.0 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-106452 | MEDIUM5.3 | org.lz4:lz4-java 1.8.0 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-106453 | MEDIUM5.3 | org.lz4:lz4-java 1.8.0 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45409 | MEDIUM5.3 | idna 3.10 fixed in 3.15 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-48734 | MEDIUM5.28 | commons-beanutils:commons-beanutils 1.9.4 fixed in 1.11.0 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-67030 | MEDIUM5.28 | org.codehaus.plexus:plexus-utils 3.5.1 fixed in 4.0.3, 3.6.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-47273 | MEDIUM5.28 | setuptools 71.1.0 fixed in 78.1.1 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-0799 | MEDIUM5.22 | libpcap 14:1.9.1-5.el8 fixed in 14:1.9.1-6.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-89158 | MEDIUM5.2 | pcre2 10.32-3.el8_6 fixed in 10.32-4.el8_10 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-59888 | MEDIUM5.2 | com.fasterxml.jackson.core:jackson-databind 2.16.0 fixed in 2.18.8, 2.21.4 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-59889 | MEDIUM5.2 | com.fasterxml.jackson.core:jackson-databind 2.16.0 fixed in 2.21.5, 2.18.9, 2.22.1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-67735 | MEDIUM5.2 | io.netty:netty-codec-http 4.1.115.Final fixed in 4.2.8.Final, 4.1.129.Final | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42580 | MEDIUM5.2 | io.netty:netty-codec-http 4.1.115.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56746 | MEDIUM5.2 | io.netty:netty-codec-http 4.1.115.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-59921 | MEDIUM5.2 | io.netty:netty-codec-http 4.1.115.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-67735 | MEDIUM5.2 | io.netty:netty-codec-http 4.1.118.Final fixed in 4.2.8.Final, 4.1.129.Final | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42580 | MEDIUM5.2 | io.netty:netty-codec-http 4.1.118.Final fixed in 4.2.13.Final, 4.1.133.Final | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56746 | MEDIUM5.2 | io.netty:netty-codec-http 4.1.118.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-59921 | MEDIUM5.2 | io.netty:netty-codec-http 4.1.118.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-50181 | MEDIUM5.18 | python3-pip-wheel 9.0.3-24.el8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-50182 | MEDIUM5.18 | python3-pip-wheel 9.0.3-24.el8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-22227 | MEDIUM5.18 | io.projectreactor.netty:reactor-netty-http 1.0.45 fixed in 1.3.0-M5, 1.2.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23949 | MEDIUM5.16 | jaraco.context 5.3.0 fixed in 6.1.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-74860 | MEDIUM5.1 | libxml2 2.9.7-19.el8_10 fixed in 2.9.7-21.el8_10.9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58057 | MEDIUM5.1 | io.netty:netty-codec 4.1.115.Final fixed in 4.1.125.Final | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-58057 | MEDIUM5.1 | io.netty:netty-codec 4.1.118.Final fixed in 4.1.125.Final | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-58056 | MEDIUM5.1 | io.netty:netty-codec-http 4.1.115.Final fixed in 4.1.125.Final, 4.2.5.Final | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-58056 | MEDIUM5.1 | io.netty:netty-codec-http 4.1.118.Final fixed in 4.1.125.Final, 4.2.5.Final | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2023-2650 | MEDIUM5.07 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 75.4% Actively Exploited | Directly Exposed |
| CVE-2024-30171 | MEDIUM5.02 | org.bouncycastle:bctls-fips 1.0.13 fixed in 1.0.19 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-34447 | MEDIUM5.02 | org.bouncycastle:bctls-fips 1.0.13 fixed in 1.0.19 | 0.8% Theoretical Threat | 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-5450 | MEDIUM5 | glibc 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.38 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | glibc 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | glibc-common 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.38 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | glibc-common 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | glibc-langpack-en 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.38 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | glibc-langpack-en 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | glibc-minimal-langpack 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.38 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | glibc-minimal-langpack 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.40 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-88807 | MEDIUM4.98 | libXrender 0.9.10-7.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-53864 | MEDIUM4.93 | com.nimbusds:nimbus-jose-jwt 9.37.2 fixed in 10.0.2, 9.37.4 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-77214 | MEDIUM4.92 | expat 2.2.5-17.el8_10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | glibc 2.28-251.el8_10.16 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.16 fixed in 2.28-251.el8_10.48 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | glibc-langpack-en 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.48 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | glibc-minimal-langpack 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.48 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-8458 | MEDIUM4.86 | curl 7.61.1-34.el8_10.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8458 | MEDIUM4.86 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25646 | MEDIUM4.86 | libpng 2:1.6.34-5.el8 fixed in 2:1.6.34-10.el8_10 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45447 | MEDIUM4.86 | openssl-libs 1:1.1.1k-14.el8_6 fixed in 1:1.1.1k-16.el8_6 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-19445 | MEDIUM4.86 | python3-libs 3.6.8-69.el8_10 fixed in 3.6.8-79.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6100 | MEDIUM4.86 | python3-libs 3.6.8-69.el8_10 fixed in 3.6.8-76.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44249 | MEDIUM4.86 | io.netty:netty-handler 4.1.115.Final fixed in 4.2.15.Final, 4.1.135.Final | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-44249 | MEDIUM4.86 | io.netty:netty-handler 4.1.118.Final fixed in 4.2.15.Final, 4.1.135.Final | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-97687 | MEDIUM4.86 | urllib3 2.4.0 fixed in 2.8.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-2511 | MEDIUM4.81 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 52.4% Actively Exploited | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libblkid 2.32.1-46.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libfdisk 2.32.1-46.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libmount 2.32.1-46.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libsmartcols 2.32.1-46.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libuuid 2.32.1-46.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | MEDIUM4.8 | python3-libs 3.6.8-69.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.8 | python3-libs 3.6.8-69.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-17543 | MEDIUM4.76 | lz4-libs 1.8.3-3.el8_4 fixed in 1.8.3-5.el8_10 | 10.5% High Exploitation Risk | Directly Exposed |
| CVE-2025-4598 | MEDIUM4.7 | systemd-libs 239-82.el8_10.5 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2013-0340 | MEDIUM4.69 | expat 2.2.5-17.el8_10 fixed in 2.5.0-1.el8_10 | 19.4% High Exploitation Risk | Directly Exposed |
| CVE-2026-86140 | MEDIUM4.68 | libxml2 2.9.7-19.el8_10 fixed in 2.9.7-21.el8_10.9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11822 | MEDIUM4.68 | sqlite-libs 3.26.0-19.el8_9 fixed in 3.26.0-21.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11824 | MEDIUM4.68 | sqlite-libs 3.26.0-19.el8_9 fixed in 3.26.0-21.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-25193 | MEDIUM4.67 | io.netty:netty-common 4.1.115.Final fixed in 4.1.118.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-4517 | MEDIUM4.56 | python3-libs 3.6.8-69.el8_10 fixed in 3.6.8-70.el8_10 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-4517 | MEDIUM4.56 | python39-libs 3.9.20-1.module+el8.10.0+22342+478c159e fixed in 3.9.25-2.module+el8.10.0+23718+1842ae33 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-4517 | MEDIUM4.56 | python39-setuptools-wheel 50.3.2-6.module+el8.10.0+22183+c898c0c1 fixed in 50.3.2-7.module+el8.10.0+23406+03055bfb | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-49794 | MEDIUM4.54 | libxml2 2.9.7-19.el8_10 fixed in 2.9.7-21.el8_10.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-8927 | MEDIUM4.5 | curl 7.61.1-34.el8_10.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45186 | MEDIUM4.5 | expat 2.2.5-17.el8_10 fixed in 2.5.0-2.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-66046 | MEDIUM4.5 | expat 2.2.5-17.el8_10 fixed in 2.5.0-4.el8_10 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-76641 | MEDIUM4.5 | expat 2.2.5-17.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-93990 | MEDIUM4.5 | expat 2.2.5-17.el8_10 fixed in 2.5.0-4.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33846 | MEDIUM4.5 | gnutls 3.6.16-8.el8_10.3 fixed in 3.6.16-8.el8_10.6 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42009 | MEDIUM4.5 | gnutls 3.6.16-8.el8_10.3 fixed in 3.6.16-8.el8_10.6 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-88806 | MEDIUM4.5 | libX11 1.6.8-9.el8_10 fixed in 1.6.8-10.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88806 | MEDIUM4.5 | libX11-common 1.6.8-9.el8_10 fixed in 1.6.8-10.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4424 | MEDIUM4.5 | libarchive 3.3.3-5.el8 fixed in 3.3.3-7.el8_10 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-8927 | MEDIUM4.5 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-27135 | MEDIUM4.5 | libnghttp2 1.33.0-6.el8_10.1 fixed in 1.33.0-6.el8_10.2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-6554 | MEDIUM4.5 | libpcap 14:1.9.1-5.el8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-4138 | MEDIUM4.5 | python3-libs 3.6.8-69.el8_10 fixed in 3.6.8-70.el8_10 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-15308 | MEDIUM4.5 | python3-libs 3.6.8-69.el8_10 fixed in 3.6.8-77.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4138 | MEDIUM4.5 | python39-libs 3.9.20-1.module+el8.10.0+22342+478c159e fixed in 3.9.25-2.module+el8.10.0+23718+1842ae33 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-4138 | MEDIUM4.5 | python39-setuptools-wheel 50.3.2-6.module+el8.10.0+22183+c898c0c1 fixed in 50.3.2-7.module+el8.10.0+23406+03055bfb | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-89425 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-core 2.16.0 fixed in 2.21.7, 2.22.3, 2.18.11 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45799 | MEDIUM4.5 | com.squareup.wire:wire-runtime-jvm 5.1.0 fixed in 6.3.0, 7.0.0-alpha03 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-40984 | MEDIUM4.5 | io.micrometer:micrometer-core 1.11.1 fixed in 1.16.6, 1.15.12 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-73508 | MEDIUM4.5 | io.netty:netty-codec-dns 4.1.115.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-24970 | MEDIUM4.5 | io.netty:netty-handler 4.1.115.Final fixed in 4.1.118.Final | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45416 | MEDIUM4.5 | io.netty:netty-handler 4.1.115.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-50010 | MEDIUM4.5 | io.netty:netty-handler 4.1.115.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75596 | MEDIUM4.5 | io.netty:netty-handler 4.1.115.Final fixed in 4.2.17.Final, 4.1.137.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45416 | MEDIUM4.5 | io.netty:netty-handler 4.1.118.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-50010 | MEDIUM4.5 | io.netty:netty-handler 4.1.118.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75596 | MEDIUM4.5 | io.netty:netty-handler 4.1.118.Final fixed in 4.2.17.Final, 4.1.137.Final | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42578 | MEDIUM4.5 | io.netty:netty-handler-proxy 4.1.115.Final fixed in 4.1.133.Final, 4.2.13.Final | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42578 | MEDIUM4.5 | io.netty:netty-handler-proxy 4.1.118.Final fixed in 4.1.133.Final, 4.2.13.Final | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-66418 | MEDIUM4.5 | urllib3 2.4.0 fixed in 2.6.0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-66471 | MEDIUM4.5 | urllib3 2.4.0 fixed in 2.6.0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-21441 | MEDIUM4.5 | urllib3 2.4.0 fixed in 2.6.3 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-97689 | MEDIUM4.5 | urllib3 2.4.0 fixed in 2.8.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47081 | MEDIUM4.5 | python3-pip-wheel 9.0.3-24.el8 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-8916 | MEDIUM4.5 | org.bouncycastle:bcpkix-fips 1.0.7 fixed in 1.0.8, 2.0.8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-6763 | MEDIUM4.5 | org.eclipse.jetty:jetty-http 9.4.57.v20241219 fixed in 12.0.12 | 1.0% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2024-47081 | MEDIUM4.5 | requests 2.32.3 fixed in 2.32.4 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | MEDIUM4.5 | python3-libs 3.6.8-69.el8_10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-0865 | MEDIUM4.5 | python3-libs 3.6.8-69.el8_10 fixed in 3.6.8-73.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | MEDIUM4.5 | python3-libs 3.6.8-69.el8_10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-83557 | MEDIUM4.48 | com.fasterxml.jackson.core:jackson-databind 2.16.0 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-69.el8_10 fixed in 3.6.8-79.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-96674 | MEDIUM4.4 | alsa-lib 1.2.10-2.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-11940 | MEDIUM4.38 | python3-libs 3.6.8-69.el8_10 fixed in 3.6.8-78.el8_10 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-11940 | MEDIUM4.38 | python39-libs 3.9.20-1.module+el8.10.0+22342+478c159e No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-11940 | MEDIUM4.38 | python39-pip-wheel 20.2.4-9.module+el8.10.0+21329+8d76b841 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-4516 | MEDIUM4.33 | python3-libs 3.6.8-69.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4516 | MEDIUM4.33 | python39-libs 3.9.20-1.module+el8.10.0+22342+478c159e fixed in 3.9.25-2.module+el8.10.0+23718+1842ae33 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4516 | MEDIUM4.33 | python39-setuptools-wheel 50.3.2-6.module+el8.10.0+22183+c898c0c1 fixed in 50.3.2-7.module+el8.10.0+23406+03055bfb | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25068 | MEDIUM4.3 | alsa-lib 1.2.10-2.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-20839 | MEDIUM4.3 | systemd-libs 239-82.el8_10.5 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54369 | MEDIUM4.26 | libacl 2.2.53-3.el8 fixed in 2.4.0-1.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-64720 | MEDIUM4.26 | libpng 2:1.6.34-5.el8 fixed in 2:1.6.34-9.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-65018 | MEDIUM4.26 | libpng 2:1.6.34-5.el8 fixed in 2:1.6.34-9.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66293 | MEDIUM4.26 | libpng 2:1.6.34-5.el8 fixed in 2:1.6.34-9.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4786 | MEDIUM4.26 | python3-libs 3.6.8-69.el8_10 fixed in 3.6.8-76.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-18401 | MEDIUM4.24 | com.fasterxml.jackson.core:jackson-core 2.16.0 fixed in 2.21.1, 2.18.6 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-19032 | MEDIUM4.24 | com.fasterxml.jackson.core:jackson-databind 2.16.0 fixed in 2.18.10, 2.21.6, 2.22.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54514 | MEDIUM4.24 | com.fasterxml.jackson.core:jackson-databind 2.16.0 fixed in 2.18.8, 2.21.4, 3.1.4 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54515 | MEDIUM4.24 | com.fasterxml.jackson.core:jackson-databind 2.16.0 fixed in 3.1.4, 2.18.9, 2.21.5, 2.22.1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-77310 | MEDIUM4.24 | com.fasterxml.jackson.core:jackson-databind 2.16.0 fixed in 2.18.9, 2.21.5, 2.22.1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-41417 | MEDIUM4.24 | io.netty:netty-codec-http 4.1.115.Final fixed in 4.1.133.Final, 4.2.13.Final | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-50020 | MEDIUM4.24 | io.netty:netty-codec-http 4.1.115.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-41417 | MEDIUM4.24 | io.netty:netty-codec-http 4.1.118.Final fixed in 4.1.133.Final, 4.2.13.Final | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-50020 | MEDIUM4.24 | io.netty:netty-codec-http 4.1.118.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-47244 | MEDIUM4.24 | io.netty:netty-codec-http2 4.1.115.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-50560 | MEDIUM4.24 | io.netty:netty-codec-http2 4.1.115.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-59900 | MEDIUM4.24 | io.netty:netty-codec-http2 4.1.115.Final fixed in 4.2.16.Final, 4.1.136.Final | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-53613 | MEDIUM4.2 | libblkid 2.32.1-46.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libfdisk 2.32.1-46.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libmount 2.32.1-46.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libsmartcols 2.32.1-46.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libuuid 2.32.1-46.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | util-linux 2.32.1-46.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | glibc 2.28-251.el8_10.16 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.16 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | glibc-common 2.28-251.el8_10.16 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.16 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | glibc-langpack-en 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.48 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | glibc-langpack-en 2.28-251.el8_10.16 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | glibc-minimal-langpack 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.48 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | glibc-minimal-langpack 2.28-251.el8_10.16 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5773 | MEDIUM4.14 | curl 7.61.1-34.el8_10.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-8932 | MEDIUM4.14 | curl 7.61.1-34.el8_10.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9080 | MEDIUM4.14 | curl 7.61.1-34.el8_10.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9545 | MEDIUM4.14 | curl 7.61.1-34.el8_10.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9546 | MEDIUM4.14 | curl 7.61.1-34.el8_10.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-23990 | MEDIUM4.14 | expat 2.2.5-17.el8_10 fixed in 2.5.0-1.el8_10 | 4.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28757 | MEDIUM4.14 | expat 2.2.5-17.el8_10 fixed in 2.5.0-1.el8_10 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56132 | MEDIUM4.14 | expat 2.2.5-17.el8_10 fixed in 2.5.0-2.el8_10.2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM4.14 | expat 2.2.5-17.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56404 | MEDIUM4.14 | expat 2.2.5-17.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56405 | MEDIUM4.14 | expat 2.2.5-17.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM4.14 | expat 2.2.5-17.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56407 | MEDIUM4.14 | expat 2.2.5-17.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76957 | MEDIUM4.14 | expat 2.2.5-17.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-52533 | MEDIUM4.14 | glib2 2.56.4-165.el8_10 fixed in 2.56.4-166.el8_10 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13601 | MEDIUM4.14 | glib2 2.56.4-165.el8_10 fixed in 2.56.4-168.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-14087 | MEDIUM4.14 | glib2 2.56.4-165.el8_10 fixed in 2.56.4-169.el8_10 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-16118 | MEDIUM4.14 | glib2 2.56.4-165.el8_10 fixed in 2.56.4-178.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM4.14 | glib2 2.56.4-165.el8_10 fixed in 2.56.4-177.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM4.14 | glib2 2.56.4-165.el8_10 fixed in 2.56.4-177.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM4.14 | glib2 2.56.4-165.el8_10 fixed in 2.56.4-177.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM4.14 | glib2 2.56.4-165.el8_10 fixed in 2.56.4-177.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | MEDIUM4.14 | glib2 2.56.4-165.el8_10 fixed in 2.56.4-177.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM4.14 | glib2 2.56.4-165.el8_10 fixed in 2.56.4-177.el8_10 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-32988 | MEDIUM4.14 | gnutls 3.6.16-8.el8_10.3 fixed in 3.6.16-8.el8_10.4 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-3833 | MEDIUM4.14 | gnutls 3.6.16-8.el8_10.3 fixed in 3.6.16-8.el8_10.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM4.14 | gnutls 3.6.16-8.el8_10.3 fixed in 3.6.16-8.el8_10.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM4.14 | gnutls 3.6.16-8.el8_10.3 fixed in 3.6.16-8.el8_10.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42013 | MEDIUM4.14 | gnutls 3.6.16-8.el8_10.3 fixed in 3.6.16-8.el8_10.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM4.14 | gnutls 3.6.16-8.el8_10.3 fixed in 3.6.16-8.el8_10.6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-88647 | MEDIUM4.14 | gnutls 3.6.16-8.el8_10.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88648 | MEDIUM4.14 | gnutls 3.6.16-8.el8_10.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM4.14 | krb5-libs 1.18.2-31.el8_10 fixed in 1.18.2-34.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM4.14 | krb5-libs 1.18.2-31.el8_10 fixed in 1.18.2-34.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM4.14 | krb5-workstation 1.18.2-31.el8_10 fixed in 1.18.2-34.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-5121 | MEDIUM4.14 | libarchive 3.3.3-5.el8 fixed in 3.3.3-7.el8_10 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5773 | MEDIUM4.14 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-8932 | MEDIUM4.14 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9080 | MEDIUM4.14 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9545 | MEDIUM4.14 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9546 | MEDIUM4.14 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM4.14 | libkadm5 1.18.2-31.el8_10 fixed in 1.18.2-34.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM4.14 | libkadm5 1.18.2-31.el8_10 fixed in 1.18.2-34.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-22695 | MEDIUM4.14 | libpng 2:1.6.34-5.el8 fixed in 2:1.6.34-10.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22801 | MEDIUM4.14 | libpng 2:1.6.34-5.el8 fixed in 2:1.6.34-10.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33416 | MEDIUM4.14 | libpng 2:1.6.34-5.el8 fixed in 2:1.6.34-11.el8_10 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-6021 | MEDIUM4.14 | libxml2 2.9.7-19.el8_10 fixed in 2.9.7-21.el8_10.1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11979 | MEDIUM4.14 | libxml2 2.9.7-19.el8_10 fixed in 2.9.7-21.el8_10.7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6653 | MEDIUM4.14 | libxml2 2.9.7-19.el8_10 fixed in 2.9.7-21.el8_10.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86138 | MEDIUM4.14 | libxml2 2.9.7-19.el8_10 fixed in 2.9.7-21.el8_10.9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86142 | MEDIUM4.14 | libxml2 2.9.7-19.el8_10 fixed in 2.9.7-21.el8_10.10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86143 | MEDIUM4.14 | libxml2 2.9.7-19.el8_10 fixed in 2.9.7-21.el8_10.9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86144 | MEDIUM4.14 | libxml2 2.9.7-19.el8_10 fixed in 2.9.7-21.el8_10.9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM4.14 | python3-libs 3.6.8-69.el8_10 fixed in 3.6.8-73.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM4.14 | python3-libs 3.6.8-69.el8_10 fixed in 3.6.8-73.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-1299 | MEDIUM4.14 | python3-libs 3.6.8-69.el8_10 fixed in 3.6.8-73.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM4.14 | python3-libs 3.6.8-69.el8_10 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM4.14 | python3-libs 3.6.8-69.el8_10 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-103242 | MEDIUM4.14 | python3-rpm 4.14.3-32.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78367 | MEDIUM4.14 | python3-rpm 4.14.3-32.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-84837 | MEDIUM4.14 | python3-rpm 4.14.3-32.el8_10 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-95519 | MEDIUM4.14 | python3-rpm 4.14.3-32.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95520 | MEDIUM4.14 | python3-rpm 4.14.3-32.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95521 | MEDIUM4.14 | python3-rpm 4.14.3-32.el8_10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-0391 | MEDIUM4.14 | python39-libs 3.9.20-1.module+el8.10.0+22342+478c159e No fix yet | 8.5% Low-Moderate Risk | Directly Exposed |
| CVE-2025-47273 | MEDIUM4.14 | python39-libs 3.9.20-1.module+el8.10.0+22342+478c159e fixed in 3.9.20-2.module+el8.10.0+23441+1124c1da | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0391 | MEDIUM4.14 | python39-pip-wheel 20.2.4-9.module+el8.10.0+21329+8d76b841 No fix yet | 8.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-78367 | MEDIUM4.14 | rpm 4.14.3-32.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-84837 | MEDIUM4.14 | rpm 4.14.3-32.el8_10 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-95519 | MEDIUM4.14 | rpm 4.14.3-32.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95520 | MEDIUM4.14 | rpm 4.14.3-32.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95521 | MEDIUM4.14 | rpm 4.14.3-32.el8_10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-103242 | MEDIUM4.14 | rpm-build-libs 4.14.3-32.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78367 | MEDIUM4.14 | rpm-build-libs 4.14.3-32.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-84837 | MEDIUM4.14 | rpm-build-libs 4.14.3-32.el8_10 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-95519 | MEDIUM4.14 | rpm-build-libs 4.14.3-32.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95520 | MEDIUM4.14 | rpm-build-libs 4.14.3-32.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95521 | MEDIUM4.14 | rpm-build-libs 4.14.3-32.el8_10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-103242 | MEDIUM4.14 | rpm-libs 4.14.3-32.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78367 | MEDIUM4.14 | rpm-libs 4.14.3-32.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-84837 | MEDIUM4.14 | rpm-libs 4.14.3-32.el8_10 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-95519 | MEDIUM4.14 | rpm-libs 4.14.3-32.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95520 | MEDIUM4.14 | rpm-libs 4.14.3-32.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95521 | MEDIUM4.14 | rpm-libs 4.14.3-32.el8_10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-13034 | MEDIUM4.08 | curl 7.61.1-34.el8_10.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1965 | MEDIUM4.08 | curl 7.61.1-34.el8_10.3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-13034 | MEDIUM4.08 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1965 | MEDIUM4.08 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0938 | MEDIUM4.08 | python3-libs 3.6.8-69.el8_10 fixed in 3.6.8-74.el8_10 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-0938 | MEDIUM4.08 | python39-libs 3.9.20-1.module+el8.10.0+22342+478c159e fixed in 3.9.25-2.module+el8.10.0+23718+1842ae33 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45673 | MEDIUM4.08 | io.netty:netty-resolver-dns 4.1.115.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8114 | MEDIUM4 | libssh 0.9.6-14.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8114 | MEDIUM4 | libssh-config 0.9.6-14.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45536 | MEDIUM4 | io.netty:netty-transport-native-epoll 4.1.115.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45536 | MEDIUM4 | io.netty:netty-transport-native-epoll 4.1.118.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45536 | MEDIUM4 | io.netty:netty-transport-native-kqueue 4.1.115.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45536 | MEDIUM4 | io.netty:netty-transport-native-kqueue 4.1.118.Final fixed in 4.2.15.Final, 4.1.135.Final | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55688 | MEDIUM4 | org.asynchttpclient:async-http-client 2.12.4 fixed in 3.0.11, 2.16.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5914 | LOW3.98 | libarchive 3.3.3-5.el8 fixed in 3.3.3-6.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-7425 | LOW3.98 | libxml2 2.9.7-19.el8_10 fixed in 2.9.7-21.el8_10.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42014 | LOW3.96 | gnutls 3.6.16-8.el8_10.3 fixed in 3.6.16-8.el8_10.6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-11856 | LOW3.9 | curl 7.61.1-34.el8_10.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-3784 | LOW3.9 | curl 7.61.1-34.el8_10.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5545 | LOW3.9 | curl 7.61.1-34.el8_10.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6429 | LOW3.9 | curl 7.61.1-34.el8_10.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-8924 | LOW3.9 | curl 7.61.1-34.el8_10.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92388 | LOW3.9 | curl 7.61.1-34.el8_10.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14512 | LOW3.9 | glib2 2.56.4-165.el8_10 fixed in 2.56.4-169.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-47268 | LOW3.9 | iputils 20180629-11.el8 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-107778 | LOW3.9 | krb5-libs 1.18.2-31.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | krb5-workstation 1.18.2-31.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-94283 | LOW3.9 | libX11 1.6.8-9.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94283 | LOW3.9 | libX11-common 1.6.8-9.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4426 | LOW3.9 | libarchive 3.3.3-5.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11856 | LOW3.9 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-3784 | LOW3.9 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5545 | LOW3.9 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6429 | LOW3.9 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-8924 | LOW3.9 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92388 | LOW3.9 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libkadm5 1.18.2-31.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58058 | LOW3.9 | nmap-ncat 2:7.92-1.el8 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-72712 | LOW3.9 | nmap-ncat 2:7.92-1.el8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW3.9 | platform-python 3.6.8-69.el8_10 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7774 | LOW3.9 | platform-python 3.6.8-69.el8_10 No fix yet | 0.6% 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-33056 | LOW3.9 | tar 2:1.30-9.el8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-10524 | LOW3.9 | wget 1.19.5-12.el8_10 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-16599 | LOW3.9 | wget 1.19.5-12.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58469 | LOW3.9 | wget 1.19.5-12.el8_10 fixed in 1.19.5-16.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | LOW3.9 | glibc 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.31 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.9 | glibc 2.28-251.el8_10.16 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | LOW3.9 | glibc-common 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.31 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.9 | glibc-common 2.28-251.el8_10.16 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | LOW3.9 | glibc-langpack-en 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.31 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.9 | glibc-langpack-en 2.28-251.el8_10.16 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | LOW3.9 | glibc-minimal-langpack 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.31 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.9 | glibc-minimal-langpack 2.28-251.el8_10.16 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-20657 | LOW3.9 | libgcc 8.5.0-26.el8_10 No fix yet | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-14250 | LOW3.9 | libgcc 8.5.0-26.el8_10 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-0967 | LOW3.9 | libssh 0.9.6-14.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59846 | LOW3.9 | libssh 0.9.6-14.el8 fixed in 0.9.6-17.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0967 | LOW3.9 | libssh-config 0.9.6-14.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59846 | LOW3.9 | libssh-config 0.9.6-14.el8 fixed in 0.9.6-17.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-20657 | LOW3.9 | libstdc++ 8.5.0-26.el8_10 No fix yet | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-14250 | LOW3.9 | libstdc++ 8.5.0-26.el8_10 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-1000654 | LOW3.9 | libtasn1 4.13-5.el8_10 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | LOW3.9 | libtasn1 4.13-5.el8_10 fixed in 4.13-6.el8_10 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0464 | LOW3.9 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0465 | LOW3.9 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0727 | LOW3.9 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-41996 | LOW3.9 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4741 | LOW3.9 | openssl-libs 1:1.1.1k-14.el8_6 fixed in 1:1.1.1k-16.el8_6 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-15468 | LOW3.9 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-15469 | LOW3.9 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | LOW3.9 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW3.9 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | LOW3.9 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | LOW3.9 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | LOW3.9 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | LOW3.9 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | LOW3.9 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | LOW3.9 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | LOW3.9 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | LOW3.9 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | LOW3.9 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42765 | LOW3.9 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | LOW3.9 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42768 | LOW3.9 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | LOW3.9 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42771 | LOW3.9 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54874 | LOW3.9 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | LOW3.9 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | LOW3.9 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2019-9674 | LOW3.9 | python3-libs 3.6.8-69.el8_10 No fix yet | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-7592 | LOW3.9 | python3-libs 3.6.8-69.el8_10 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-6075 | LOW3.9 | python3-libs 3.6.8-69.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-20225 | LOW3.9 | python3-pip-wheel 9.0.3-24.el8 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-7592 | LOW3.9 | python39-libs 3.9.20-1.module+el8.10.0+22342+478c159e No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-6075 | LOW3.9 | python39-libs 3.9.20-1.module+el8.10.0+22342+478c159e fixed in 3.9.25-2.module+el8.10.0+23718+1842ae33 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-7592 | LOW3.9 | python39-pip-wheel 20.2.4-9.module+el8.10.0+21329+8d76b841 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-7592 | LOW3.9 | python39-setuptools-wheel 50.3.2-6.module+el8.10.0+22183+c898c0c1 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-6075 | LOW3.9 | python39-setuptools-wheel 50.3.2-6.module+el8.10.0+22183+c898c0c1 fixed in 50.3.2-7.module+el8.10.0+23406+03055bfb | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-3997 | LOW3.9 | systemd-libs 239-82.el8_10.5 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-2024-12718 | LOW3.88 | platform-python 3.6.8-69.el8_10 fixed in 3.6.8-70.el8_10 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-54370 | LOW3.78 | acl 2.2.53-3.el8 fixed in 2.4.0-1.el8_10 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54370 | LOW3.78 | libacl 2.2.53-3.el8 fixed in 2.4.0-1.el8_10 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-12345 | LOW3.78 | platform-python 3.6.8-69.el8_10 fixed in 3.6.8-79.el8_10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5958 | LOW3.78 | sed 4.5-5.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-8905 | LOW3.74 | file-libs 5.33-26.el8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-1757 | LOW3.72 | libxml2 2.9.7-19.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | glibc 2.28-251.el8_10.16 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | glibc-common 2.28-251.el8_10.16 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | glibc-langpack-en 2.28-251.el8_10.16 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | glibc-minimal-langpack 2.28-251.el8_10.16 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.7 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-107283 | LOW3.7 | org.asynchttpclient:async-http-client 2.12.4 fixed in 3.0.12, 2.16.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-106449 | LOW3.7 | org.lz4:lz4-java 1.8.0 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56391 | LOW3.66 | coreutils-single 8.30-15.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW3.66 | coreutils-single 8.30-15.el8 fixed in 8.30-20.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.66 | libblkid 2.32.1-46.el8 fixed in 2.32.1-48.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW3.66 | libfdisk 2.32.1-46.el8 fixed in 2.32.1-48.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW3.66 | libmount 2.32.1-46.el8 fixed in 2.32.1-48.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31912 | LOW3.66 | libpcap 14:1.9.1-5.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-64506 | LOW3.66 | libpng 2:1.6.34-5.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW3.66 | libsmartcols 2.32.1-46.el8 fixed in 2.32.1-48.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW3.66 | libuuid 2.32.1-46.el8 fixed in 2.32.1-48.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | LOW3.66 | platform-python 3.6.8-69.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.66 | util-linux 2.32.1-46.el8 fixed in 2.32.1-48.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-31879 | LOW3.66 | wget 1.19.5-12.el8_10 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-59890 | LOW3.66 | setuptools 71.1.0 fixed in 83.0.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6069 | LOW3.65 | python3-libs 3.6.8-69.el8_10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-8291 | LOW3.65 | python3-libs 3.6.8-69.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-6069 | LOW3.65 | python39-libs 3.9.20-1.module+el8.10.0+22342+478c159e fixed in 3.9.25-2.module+el8.10.0+23718+1842ae33 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-8291 | LOW3.65 | python39-libs 3.9.20-1.module+el8.10.0+22342+478c159e fixed in 3.9.25-2.module+el8.10.0+23718+1842ae33 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-6069 | LOW3.65 | python39-setuptools-wheel 50.3.2-6.module+el8.10.0+22183+c898c0c1 fixed in 50.3.2-7.module+el8.10.0+23406+03055bfb | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-8291 | LOW3.65 | python39-setuptools-wheel 50.3.2-6.module+el8.10.0+22183+c898c0c1 fixed in 50.3.2-7.module+el8.10.0+23406+03055bfb | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5713 | LOW3.6 | platform-python 3.6.8-69.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8058 | LOW3.57 | glibc 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.25 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | glibc-common 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.25 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | glibc-langpack-en 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.25 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | glibc-minimal-langpack 2.28-251.el8_10.16 fixed in 2.28-251.el8_10.25 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-45803 | LOW3.57 | python3-pip-wheel 9.0.3-24.el8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-102633 | LOW3.54 | expat 2.2.5-17.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-113351 | LOW3.54 | expat 2.2.5-17.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | LOW3.54 | expat 2.2.5-17.el8_10 fixed in 2.5.0-2.el8_10.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56412 | LOW3.54 | expat 2.2.5-17.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-67693 | LOW3.54 | gnutls 3.6.16-8.el8_10.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46675 | LOW3.54 | libpng 2:1.6.34-5.el8 No fix yet | — | Directly Exposed |
| CVE-2026-0990 | LOW3.54 | libxml2 2.9.7-19.el8_10 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-15146 | LOW3.54 | wget 1.19.5-12.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-32990 | LOW3.52 | gnutls 3.6.16-8.el8_10.3 fixed in 3.6.16-8.el8_10.4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-25724 | LOW3.52 | libarchive 3.3.3-5.el8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-32414 | LOW3.52 | libxml2 2.9.7-19.el8_10 fixed in 2.9.7-20.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-32415 | LOW3.52 | libxml2 2.9.7-19.el8_10 fixed in 2.9.7-21.el8_10.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4330 | LOW3.52 | platform-python 3.6.8-69.el8_10 fixed in 3.6.8-70.el8_10 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-4435 | LOW3.52 | platform-python 3.6.8-69.el8_10 fixed in 3.6.8-70.el8_10 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-8194 | LOW3.52 | platform-python 3.6.8-69.el8_10 fixed in 3.6.8-71.el8_10 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-9287 | LOW3.52 | python39 3.9.20-1.module+el8.10.0+22342+478c159e fixed in 3.9.25-2.module+el8.10.0+23718+1842ae33 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-4330 | LOW3.52 | python39 3.9.20-1.module+el8.10.0+22342+478c159e fixed in 3.9.25-2.module+el8.10.0+23718+1842ae33 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-4435 | LOW3.52 | python39 3.9.20-1.module+el8.10.0+22342+478c159e fixed in 3.9.25-2.module+el8.10.0+23718+1842ae33 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-8194 | LOW3.52 | python39 3.9.20-1.module+el8.10.0+22342+478c159e fixed in 3.9.20-2.module+el8.10.0+23441+1124c1da | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW3.42 | curl 7.61.1-34.el8_10.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3783 | LOW3.42 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-6395 | LOW3.31 | gnutls 3.6.16-8.el8_10.3 fixed in 3.6.16-8.el8_10.4 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2020-35512 | LOW3.31 | dbus-common 1:1.12.8-26.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-35512 | LOW3.31 | dbus-daemon 1:1.12.8-26.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-35512 | LOW3.31 | dbus-libs 1:1.12.8-26.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-25260 | LOW3.31 | elfutils-default-yama-scope 0.190-2.el8 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-26.el8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | LOW3.31 | libgcc 8.5.0-26.el8_10 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | LOW3.31 | libstdc++ 8.5.0-26.el8_10 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2021-24032 | LOW3.31 | libzstd 1.4.4-1.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | LOW3.31 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-0397 | LOW3.31 | python3-libs 3.6.8-69.el8_10 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-0397 | LOW3.31 | python39-libs 3.9.20-1.module+el8.10.0+22342+478c159e No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-0397 | LOW3.31 | python39-pip-wheel 20.2.4-9.module+el8.10.0+21329+8d76b841 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-0397 | LOW3.31 | python39-setuptools-wheel 50.3.2-6.module+el8.10.0+22183+c898c0c1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-19617 | LOW3.3 | device-mapper 8:1.02.181-15.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-32776 | LOW3.3 | expat 2.2.5-17.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | LOW3.3 | expat 2.2.5-17.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | LOW3.3 | expat 2.2.5-17.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94284 | LOW3.3 | libX11 1.6.8-9.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94284 | LOW3.3 | libX11-common 1.6.8-9.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-60753 | LOW3.3 | libarchive 3.3.3-5.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5745 | LOW3.3 | libarchive 3.3.3-5.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31911 | LOW3.3 | libpcap 14:1.9.1-5.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6244 | LOW3.3 | libpcap 14:1.9.1-5.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76781 | LOW3.3 | libxml2 2.9.7-19.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-25282 | LOW3.3 | nmap-ncat 2:7.92-1.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-13837 | LOW3.3 | platform-python 3.6.8-69.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-0864 | LOW3.3 | platform-python 3.6.8-69.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-42308 | LOW3.3 | platform-python 3.6.8-69.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-50812 | LOW3.3 | sqlite-libs 3.26.0-19.el8_9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53655 | LOW3.3 | tar 2:1.30-9.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5704 | LOW3.3 | tar 2:1.30-9.el8 fixed in 2:1.30-13.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41990 | LOW3.3 | libgcrypt 1.8.5-7.el8_6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0965 | LOW3.3 | libssh 0.9.6-14.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0965 | LOW3.3 | libssh-config 0.9.6-14.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW3.3 | python3-libs 3.6.8-69.el8_10 fixed in 3.6.8-75.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW3.3 | python3-libs 3.6.8-69.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW3.3 | python3-libs 3.6.8-69.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW3.3 | python3-libs 3.6.8-69.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1489 | LOW3.24 | glib2 2.56.4-165.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58055 | LOW3.24 | libnghttp2 1.33.0-6.el8_10.1 fixed in 1.33.0-6.el8_10.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-40930 | LOW3.24 | libpng 2:1.6.34-5.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9086 | LOW3.18 | curl 7.61.1-34.el8_10.3 fixed in 7.61.1-34.el8_10.9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-4873 | LOW3.18 | curl 7.61.1-34.el8_10.3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6253 | LOW3.18 | curl 7.61.1-34.el8_10.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-7168 | LOW3.18 | curl 7.61.1-34.el8_10.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-59375 | LOW3.18 | expat 2.2.5-17.el8_10 fixed in 2.5.0-1.el8_10 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-15588 | LOW3.18 | glib2 2.56.4-165.el8_10 fixed in 2.56.4-177.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86469 | LOW3.18 | glib2 2.56.4-165.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14831 | LOW3.18 | gnutls 3.6.16-8.el8_10.3 fixed in 3.6.16-8.el8_10.5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | LOW3.18 | gnutls 3.6.16-8.el8_10.3 fixed in 3.6.16-8.el8_10.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libblkid 2.32.1-46.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-9086 | LOW3.18 | libcurl 7.61.1-34.el8_10.3 fixed in 7.61.1-34.el8_10.9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-4873 | LOW3.18 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6253 | LOW3.18 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-7168 | LOW3.18 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libfdisk 2.32.1-46.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libmount 2.32.1-46.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libsmartcols 2.32.1-46.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libuuid 2.32.1-46.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12084 | LOW3.18 | platform-python 3.6.8-69.el8_10 fixed in 3.6.8-72.el8_10 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW3.18 | platform-python 3.6.8-69.el8_10 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-19672 | LOW3.18 | platform-python 3.6.8-69.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW3.18 | platform-python 3.6.8-69.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4360 | LOW3.18 | platform-python 3.6.8-69.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW3.18 | util-linux 2.32.1-46.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-58470 | LOW3.18 | wget 1.19.5-12.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44431 | LOW3.18 | urllib3 2.4.0 fixed in 2.7.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-11168 | LOW3.15 | python39-libs 3.9.20-1.module+el8.10.0+22342+478c159e fixed in 3.9.25-2.module+el8.10.0+23718+1842ae33 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-11168 | LOW3.15 | python39-setuptools-wheel 50.3.2-6.module+el8.10.0+22183+c898c0c1 fixed in 50.3.2-7.module+el8.10.0+23406+03055bfb | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-41409 | LOW3.12 | pcre2 10.32-3.el8_6 No fix yet | 1.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| 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 | urllib3 2.4.0 fixed in 2.5.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-50182 | LOW3.11 | urllib3 2.4.0 fixed in 2.5.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-0968 | LOW3.1 | libssh 0.9.6-14.el8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0968 | LOW3.1 | libssh-config 0.9.6-14.el8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-94285 | LOW3.06 | libX11 1.6.8-9.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94285 | LOW3.06 | libX11-common 1.6.8-9.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-4878 | LOW3.06 | libssh 0.9.6-14.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4878 | LOW3.06 | libssh-config 0.9.6-14.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | LOW3.01 | krb5-libs 1.18.2-31.el8_10 fixed in 1.18.2-32.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | LOW3.01 | krb5-workstation 1.18.2-31.el8_10 fixed in 1.18.2-32.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | LOW3.01 | libkadm5 1.18.2-31.el8_10 fixed in 1.18.2-32.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | LOW3 | krb5-libs 1.18.2-31.el8_10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | LOW3 | krb5-workstation 1.18.2-31.el8_10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | LOW3 | libkadm5 1.18.2-31.el8_10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-18238 | LOW3 | libpcap 14:1.9.1-5.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-28164 | LOW3 | libpng 2:1.6.34-5.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | krb5-libs 1.18.2-31.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | krb5-workstation 1.18.2-31.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | libkadm5 1.18.2-31.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-8286 | LOW2.92 | curl 7.61.1-34.el8_10.3 fixed in 7.61.1-34.el8_10.13 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | LOW2.92 | libcurl 7.61.1-34.el8_10.3 fixed in 7.61.1-34.el8_10.13 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-19445 | LOW2.92 | platform-python 3.6.8-69.el8_10 fixed in 3.6.8-79.el8_10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | LOW2.92 | platform-python 3.6.8-69.el8_10 fixed in 3.6.8-76.el8_10 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | util-linux 2.32.1-46.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.88 | curl 7.61.1-34.el8_10.3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14017 | LOW2.88 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | LOW2.88 | platform-python 3.6.8-69.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.88 | platform-python 3.6.8-69.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-45582 | LOW2.86 | tar 2:1.30-9.el8 fixed in 2:1.30-13.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gnupg2 2.2.20-3.el8_6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-41991 | LOW2.82 | gzip 1.9-13.el8_5 fixed in 1.9-15.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.82 | libblkid 2.32.1-46.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libfdisk 2.32.1-46.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libmount 2.32.1-46.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libsmartcols 2.32.1-46.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libuuid 2.32.1-46.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-64118 | LOW2.82 | tar 2:1.30-9.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | util-linux 2.32.1-46.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9714 | LOW2.8 | libxml2 2.9.7-19.el8_10 fixed in 2.9.7-21.el8_10.4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18503 | LOW2.8 | python3-libs 3.6.8-69.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-4517 | LOW2.74 | platform-python 3.6.8-69.el8_10 fixed in 3.6.8-70.el8_10 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-4517 | LOW2.74 | python39 3.9.20-1.module+el8.10.0+22342+478c159e fixed in 3.9.25-2.module+el8.10.0+23718+1842ae33 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-4138 | LOW2.7 | platform-python 3.6.8-69.el8_10 fixed in 3.6.8-70.el8_10 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-15308 | LOW2.7 | platform-python 3.6.8-69.el8_10 fixed in 3.6.8-77.el8_10 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-4138 | LOW2.7 | python39 3.9.20-1.module+el8.10.0+22342+478c159e fixed in 3.9.25-2.module+el8.10.0+23718+1842ae33 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-48964 | LOW2.7 | iputils 20180629-11.el8 No fix yet | 0.4% 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-2026-56131 | LOW2.7 | expat 2.2.5-17.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | LOW2.7 | platform-python 3.6.8-69.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-0865 | LOW2.7 | platform-python 3.6.8-69.el8_10 fixed in 3.6.8-73.el8_10 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW2.7 | platform-python 3.6.8-69.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-7264 | LOW2.69 | curl 7.61.1-34.el8_10.3 No fix yet | 20.2% High Exploitation Risk | Directly Exposed |
| CVE-2024-7264 | LOW2.69 | libcurl 7.61.1-34.el8_10.3 No fix yet | 20.2% High Exploitation Risk | Directly Exposed |
| CVE-2026-19553 | LOW2.66 | platform-python 3.6.8-69.el8_10 fixed in 3.6.8-79.el8_10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-64505 | LOW2.64 | libpng 2:1.6.34-5.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34757 | LOW2.64 | libpng 2:1.6.34-5.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18477 | LOW2.64 | tar 2:1.30-9.el8 fixed in 2:1.30-13.el8_10 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18508 | LOW2.64 | tar 2:1.30-9.el8 fixed in 2:1.30-13.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-11940 | LOW2.63 | platform-python 3.6.8-69.el8_10 fixed in 3.6.8-78.el8_10 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-11940 | LOW2.63 | python39 3.9.20-1.module+el8.10.0+22342+478c159e No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-11940 | LOW2.63 | python39-pip 20.2.4-9.module+el8.10.0+21329+8d76b841 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-8277 | LOW2.63 | libssh 0.9.6-14.el8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-8277 | LOW2.63 | libssh-config 0.9.6-14.el8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1795 | LOW2.63 | python3-libs 3.6.8-69.el8_10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1795 | LOW2.63 | python39-libs 3.9.20-1.module+el8.10.0+22342+478c159e No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1795 | LOW2.63 | python39-pip-wheel 20.2.4-9.module+el8.10.0+21329+8d76b841 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1795 | LOW2.63 | python39-setuptools-wheel 50.3.2-6.module+el8.10.0+22183+c898c0c1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4516 | LOW2.6 | platform-python 3.6.8-69.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-4516 | LOW2.6 | python39 3.9.20-1.module+el8.10.0+22342+478c159e fixed in 3.9.25-2.module+el8.10.0+23718+1842ae33 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18313 | LOW2.58 | libpcap 14:1.9.1-5.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54369 | LOW2.56 | acl 2.2.53-3.el8 fixed in 2.4.0-1.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4786 | LOW2.56 | platform-python 3.6.8-69.el8_10 fixed in 3.6.8-76.el8_10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW2.52 | gnupg2 2.2.20-3.el8_6 fixed in 2.2.20-4.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-1484 | LOW2.52 | glib2 2.56.4-165.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-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-40355 | LOW2.48 | krb5-workstation 1.18.2-31.el8_10 fixed in 1.18.2-34.el8_10 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW2.48 | platform-python 3.6.8-69.el8_10 fixed in 3.6.8-73.el8_10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW2.48 | platform-python 3.6.8-69.el8_10 fixed in 3.6.8-73.el8_10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-1299 | LOW2.48 | platform-python 3.6.8-69.el8_10 fixed in 3.6.8-73.el8_10 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW2.48 | platform-python 3.6.8-69.el8_10 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW2.48 | platform-python 3.6.8-69.el8_10 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2022-0391 | LOW2.48 | python39 3.9.20-1.module+el8.10.0+22342+478c159e No fix yet | 8.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-47273 | LOW2.48 | python39 3.9.20-1.module+el8.10.0+22342+478c159e fixed in 3.9.20-2.module+el8.10.0+23441+1124c1da | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-0391 | LOW2.48 | python39-pip 20.2.4-9.module+el8.10.0+21329+8d76b841 No fix yet | 8.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-103242 | LOW2.48 | rpm 4.14.3-32.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2005-2541 | LOW2.48 | tar 2:1.30-9.el8 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-58471 | LOW2.48 | wget 1.19.5-12.el8_10 fixed in 1.19.5-16.el8_10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58472 | LOW2.48 | wget 1.19.5-12.el8_10 fixed in 1.19.5-16.el8_10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-0938 | LOW2.45 | platform-python 3.6.8-69.el8_10 fixed in 3.6.8-74.el8_10 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0938 | LOW2.45 | python39 3.9.20-1.module+el8.10.0+22342+478c159e fixed in 3.9.25-2.module+el8.10.0+23718+1842ae33 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2025-4373 | LOW2.45 | glib2 2.56.4-165.el8_10 fixed in 2.56.4-166.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-27534 | LOW2.34 | curl 7.61.1-34.el8_10.3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-11053 | LOW2.34 | curl 7.61.1-34.el8_10.3 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14524 | LOW2.34 | curl 7.61.1-34.el8_10.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | LOW2.34 | curl 7.61.1-34.el8_10.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15224 | LOW2.34 | curl 7.61.1-34.el8_10.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6276 | LOW2.34 | curl 7.61.1-34.el8_10.3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86414 | LOW2.34 | curl 7.61.1-34.el8_10.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-92390 | LOW2.34 | curl 7.61.1-34.el8_10.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53910 | LOW2.34 | diffutils 3.6-6.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66382 | LOW2.34 | expat 2.2.5-17.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-24883 | LOW2.34 | gnupg2 2.2.20-3.el8_6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-4209 | LOW2.34 | gnutls 3.6.16-8.el8_10.3 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9820 | LOW2.34 | gnutls 3.6.16-8.el8_10.3 fixed in 3.6.16-8.el8_10.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41992 | LOW2.34 | gzip 1.9-13.el8_5 fixed in 1.9-15.el8_10 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2018-1000879 | LOW2.34 | libarchive 3.3.3-5.el8 No fix yet | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-1000880 | LOW2.34 | libarchive 3.3.3-5.el8 No fix yet | 4.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-27534 | LOW2.34 | libcurl 7.61.1-34.el8_10.3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-11053 | LOW2.34 | libcurl 7.61.1-34.el8_10.3 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14524 | LOW2.34 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | LOW2.34 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15224 | LOW2.34 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6276 | LOW2.34 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86414 | LOW2.34 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-92390 | LOW2.34 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-7317 | LOW2.34 | libpng 2:1.6.34-5.el8 No fix yet | 9.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-34459 | LOW2.34 | libxml2 2.9.7-19.el8_10 fixed in 2.9.7-21.el8_10.5 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2025-27113 | LOW2.34 | libxml2 2.9.7-19.el8_10 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-2019-9674 | LOW2.34 | platform-python 3.6.8-69.el8_10 No fix yet | 5.6% Low-Moderate Risk | Post-Exploit |
| CVE-2024-7592 | LOW2.34 | platform-python 3.6.8-69.el8_10 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-6075 | LOW2.34 | platform-python 3.6.8-69.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-2026-44605 | LOW2.34 | python3-rpm 4.14.3-32.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-7592 | LOW2.34 | python39 3.9.20-1.module+el8.10.0+22342+478c159e No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-6075 | LOW2.34 | python39 3.9.20-1.module+el8.10.0+22342+478c159e fixed in 3.9.25-2.module+el8.10.0+23718+1842ae33 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-7592 | LOW2.34 | python39-pip 20.2.4-9.module+el8.10.0+21329+8d76b841 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-44605 | LOW2.34 | rpm 4.14.3-32.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44605 | LOW2.34 | rpm-build-libs 4.14.3-32.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44605 | LOW2.34 | rpm-libs 4.14.3-32.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-19244 | LOW2.34 | sqlite-libs 3.26.0-19.el8_9 No fix yet | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9936 | LOW2.34 | sqlite-libs 3.26.0-19.el8_9 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9937 | LOW2.34 | sqlite-libs 3.26.0-19.el8_9 No fix yet | 6.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9923 | LOW2.34 | tar 2:1.30-9.el8 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-5642 | LOW2.29 | python39-libs 3.9.20-1.module+el8.10.0+22342+478c159e fixed in 3.9.25-2.module+el8.10.0+23718+1842ae33 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-5642 | LOW2.29 | python39-setuptools-wheel 50.3.2-6.module+el8.10.0+22183+c898c0c1 fixed in 50.3.2-7.module+el8.10.0+23406+03055bfb | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-5278 | LOW2.24 | coreutils-single 8.30-15.el8 fixed in 8.30-21.el8_10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW2.22 | curl 7.61.1-34.el8_10.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80230 | LOW2.22 | curl 7.61.1-34.el8_10.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-87864 | LOW2.22 | curl 7.61.1-34.el8_10.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-92389 | LOW2.22 | curl 7.61.1-34.el8_10.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-92391 | LOW2.22 | curl 7.61.1-34.el8_10.3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41080 | LOW2.22 | expat 2.2.5-17.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0988 | LOW2.22 | glib2 2.56.4-165.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3832 | LOW2.22 | gnutls 3.6.16-8.el8_10.3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-5419 | LOW2.22 | gnutls 3.6.16-8.el8_10.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18924 | LOW2.22 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80230 | LOW2.22 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-87864 | LOW2.22 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-92389 | LOW2.22 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-92391 | LOW2.22 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0989 | LOW2.22 | libxml2 2.9.7-19.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| 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-69.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-8291 | LOW2.19 | platform-python 3.6.8-69.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-6069 | LOW2.19 | python39 3.9.20-1.module+el8.10.0+22342+478c159e fixed in 3.9.25-2.module+el8.10.0+23718+1842ae33 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-8291 | LOW2.19 | python39 3.9.20-1.module+el8.10.0+22342+478c159e fixed in 3.9.25-2.module+el8.10.0+23718+1842ae33 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW2.16 | gnupg2 2.2.20-3.el8_6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-17591 | LOW2.16 | libarchive 3.3.3-5.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-45803 | LOW2.14 | platform-python-pip 9.0.3-24.el8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-57970 | LOW2.04 | libarchive 3.3.3-5.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-35512 | LOW1.99 | dbus-tools 1:1.12.8-26.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-4156 | LOW1.99 | gawk 4.2.1-4.el8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-29499 | LOW1.99 | glib2 2.56.4-165.el8_10 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-32611 | LOW1.99 | glib2 2.56.4-165.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-32636 | LOW1.99 | glib2 2.56.4-165.el8_10 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-32665 | LOW1.99 | glib2 2.56.4-165.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-30258 | LOW1.99 | gnupg2 2.2.20-3.el8_6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1632 | LOW1.99 | libarchive 3.3.3-5.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5915 | LOW1.99 | libarchive 3.3.3-5.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5916 | LOW1.99 | libarchive 3.3.3-5.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5917 | LOW1.99 | libarchive 3.3.3-5.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5918 | LOW1.99 | libarchive 3.3.3-5.el8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-45322 | LOW1.99 | libxml2 2.9.7-19.el8_10 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-0397 | LOW1.99 | platform-python 3.6.8-69.el8_10 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2024-0397 | LOW1.99 | python39 3.9.20-1.module+el8.10.0+22342+478c159e No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2024-0397 | LOW1.99 | python39-pip 20.2.4-9.module+el8.10.0+21329+8d76b841 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2024-0232 | LOW1.99 | sqlite-libs 3.26.0-19.el8_9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW1.98 | platform-python 3.6.8-69.el8_10 fixed in 3.6.8-75.el8_10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW1.98 | platform-python 3.6.8-69.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.98 | platform-python 3.6.8-69.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.98 | platform-python 3.6.8-69.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-70873 | LOW1.98 | sqlite-libs 3.26.0-19.el8_9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-20193 | LOW1.98 | tar 2:1.30-9.el8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-34397 | LOW1.94 | glib2 2.56.4-165.el8_10 fixed in 2.56.4-166.el8_10 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-3360 | LOW1.89 | glib2 2.56.4-165.el8_10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-7039 | LOW1.89 | glib2 2.56.4-165.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-11168 | LOW1.89 | python39 3.9.20-1.module+el8.10.0+22342+478c159e fixed in 3.9.25-2.module+el8.10.0+23718+1842ae33 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-82209 | LOW1.86 | curl 7.61.1-34.el8_10.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-82209 | LOW1.86 | libcurl 7.61.1-34.el8_10.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-56433 | LOW1.84 | shadow-utils 2:4.6-22.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.74 | gnupg2 2.2.20-3.el8_6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0992 | LOW1.74 | libxml2 2.9.7-19.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-3219 | LOW1.68 | gnupg2 2.2.20-3.el8_6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-39804 | LOW1.68 | tar 2:1.30-9.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1485 | LOW1.68 | glib2 2.56.4-165.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18503 | LOW1.68 | platform-python 3.6.8-69.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1795 | LOW1.58 | platform-python 3.6.8-69.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1795 | LOW1.58 | python39 3.9.20-1.module+el8.10.0+22342+478c159e No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1795 | LOW1.58 | python39-pip 20.2.4-9.module+el8.10.0+21329+8d76b841 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-24515 | LOW1.5 | expat 2.2.5-17.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-5642 | LOW1.38 | python39 3.9.20-1.module+el8.10.0+22342+478c159e fixed in 3.9.25-2.module+el8.10.0+23718+1842ae33 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-6170 | LOW1.27 | libxml2 2.9.7-19.el8_10 fixed in 2.9.7-21.el8_10.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11961 | LOW1.14 | libpcap 14:1.9.1-5.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| GHSA-xmj3-9gf7-h52w | LOW0.6 | setuptools 71.1.0 fixed in 84.1.0 | — | Directly Exposed |
| CVE-2025-6020 | NONE0 | pam 1.3.1-36.el8_10 fixed in 1.3.1-38.el8_10 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-8941 | NONE0 | pam 1.3.1-36.el8_10 fixed in 1.3.1-38.el8_10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-47273 | NONE0 | platform-python-setuptools 39.2.0-8.el8_10 fixed in 39.2.0-9.el8_10 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-29111 | NONE0 | systemd 239-82.el8_10.5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-29111 | NONE0 | systemd-pam 239-82.el8_10.5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4105 | NONE0 | systemd 239-82.el8_10.5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4105 | NONE0 | systemd-pam 239-82.el8_10.5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-12610 | NONE0 | pam 1.3.1-36.el8_10 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | pam 1.3.1-36.el8_10 fixed in 1.3.1-40.el8_10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-4598 | NONE0 | systemd 239-82.el8_10.5 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-4598 | NONE0 | systemd-pam 239-82.el8_10.5 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2018-20839 | NONE0 | systemd 239-82.el8_10.5 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-20839 | NONE0 | systemd-pam 239-82.el8_10.5 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2020-35512 | NONE0 | dbus 1:1.12.8-26.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-3997 | NONE0 | systemd 239-82.el8_10.5 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-3997 | NONE0 | systemd-pam 239-82.el8_10.5 No fix yet | 1.7% Low-Moderate Risk | 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.