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 exploit the exposed glibc and nss vulnerabilities (CVE-2019-9169, CVE-2022-23218) to achieve remote code execution or compromise the integrity of data streams processed by Debezium Connect. These vulnerabilities are in core system libraries and are reachable without any special configuration, so they cannot be avoided by disabling modules. Rebuilding from a patched base image is the only effective mitigation; the current image remains unsafe until then.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2019-9169 | CRITICAL9.8 | glibc 2.17-260.el7 No fix yet | 4.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23218 | CRITICAL9.8 | glibc 2.17-260.el7 No fix yet | 4.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23219 | CRITICAL9.8 | glibc 2.17-260.el7 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33574 | CRITICAL9.8 | glibc 2.17-260.el7 No fix yet | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9169 | CRITICAL9.8 | glibc-common 2.17-260.el7 No fix yet | 4.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23218 | CRITICAL9.8 | glibc-common 2.17-260.el7 No fix yet | 4.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23219 | CRITICAL9.8 | glibc-common 2.17-260.el7 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33574 | CRITICAL9.8 | glibc-common 2.17-260.el7 No fix yet | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2019-17006 | CRITICAL9.8 | nspr 4.19.0-1.el7_5 fixed in 4.25.0-2.el7_9 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-17006 | CRITICAL9.8 | nss 3.36.0-7.el7_5 fixed in 3.53.1-3.el7_9 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-17006 | CRITICAL9.8 | nss-softokn 3.36.0-5.el7_5 fixed in 3.53.1-6.el7_9 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-17006 | CRITICAL9.8 | nss-softokn-freebl 3.36.0-5.el7_5 fixed in 3.53.1-6.el7_9 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-17006 | CRITICAL9.8 | nss-sysinit 3.36.0-7.el7_5 fixed in 3.53.1-3.el7_9 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-17006 | CRITICAL9.8 | nss-util 3.36.0-1.el7_5 fixed in 3.53.1-1.el7_9 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45853 | CRITICAL9.8 | zlib 1.2.7-18.el7 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-16335 | CRITICAL9.8 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10, 2.8.11.5, 2.6.7.3 | 5.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-16942 | CRITICAL9.8 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.1, 2.8.11.5, 2.6.7.3 | 5.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-16943 | CRITICAL9.8 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.1, 2.8.11.5, 2.6.7.3 | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2019-17267 | CRITICAL9.8 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10, 2.8.11.5 | 4.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-17531 | CRITICAL9.8 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.1, 2.8.11.5, 2.6.7.3 | 5.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20330 | CRITICAL9.8 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.6.7.4, 2.7.9.7, 2.8.11.5, 2.9.10.2 | 8.6% Low-Moderate Risk | Directly Exposed |
| CVE-2020-9546 | CRITICAL9.8 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.4 | 4.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-1597 | CRITICAL9.8 | org.postgresql:postgresql 42.2.5 fixed in 42.2.28, 42.3.9, 42.4.4, 42.5.5, 42.6.1, 42.7.2 | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21724 | CRITICAL9.8 | org.postgresql:postgresql 42.2.5 fixed in 42.2.25, 42.3.2 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-26520 | CRITICAL9.8 | org.postgresql:postgresql 42.2.5 fixed in 42.3.3 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-34169 | CRITICAL9.75 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.342.b07-1.el7_9 | 81.0% Actively Exploited | Directly Exposed |
| CVE-2022-34169 | CRITICAL9.75 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.342.b07-1.el7_9 | 81.0% Actively Exploited | Directly Exposed |
| CVE-2022-34169 | CRITICAL9.75 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.342.b07-1.el7_9 | 81.0% Actively Exploited | Directly Exposed |
| CVE-2016-2183 | CRITICAL9.75 | nss 3.36.0-7.el7_5 No fix yet | 95.7% Actively Exploited | Directly Exposed |
| CVE-2016-2183 | CRITICAL9.75 | nss-sysinit 3.36.0-7.el7_5 No fix yet | 95.7% Actively Exploited | Directly Exposed |
| CVE-2022-0778 | CRITICAL9.75 | openssl-libs 1:1.0.2k-16.el7 fixed in 1:1.0.2k-25.el7_9 | 70.6% Actively Exploited | Directly Exposed |
| CVE-2021-23840 | CRITICAL9.75 | openssl-libs 1:1.0.2k-16.el7 fixed in 1:1.0.2k-22.el7_9 | 50.7% Actively Exploited | Directly Exposed |
| CVE-2024-6119 | CRITICAL9.75 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 66.6% Actively Exploited | Directly Exposed |
| CVE-2018-25032 | CRITICAL9.75 | zlib 1.2.7-18.el7 fixed in 1.2.7-20.el7_9 | 52.1% Actively Exploited | Directly Exposed |
| CVE-2021-4104 | CRITICAL9.75 | log4j:log4j 1.2.17 No fix yet | 81.1% Actively Exploited | Directly Exposed |
| CVE-2021-28165 | CRITICAL9.75 | org.eclipse.jetty:jetty-server 9.4.14.v20181114 fixed in 9.4.39, 10.0.2, 11.0.2 | 53.9% Actively Exploited | Directly Exposed |
| CVE-2023-0286 | CRITICAL9.62 | openssl-libs 1:1.0.2k-16.el7 fixed in 1:1.0.2k-26.el7_9 | 59.5% Actively Exploited | Directly Exposed |
| CVE-2021-3712 | CRITICAL9.62 | openssl-libs 1:1.0.2k-16.el7 fixed in 1:1.0.2k-23.el7_9 | 50.4% Actively Exploited | Directly Exposed |
| CVE-2021-42574 | CRITICAL9.54 | libgcc 4.8.5-36.el7 No fix yet | 12.2% High Exploitation Risk | Directly Exposed |
| CVE-2021-42574 | CRITICAL9.54 | libstdc++ 4.8.5-36.el7 No fix yet | 12.2% High Exploitation Risk | Directly Exposed |
| CVE-2022-1292 | CRITICAL9.49 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 82.6% Actively Exploited | Directly Exposed |
| CVE-2022-2068 | CRITICAL9.49 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 95.8% Actively Exploited | Directly Exposed |
| CVE-2020-35728 | CRITICAL9.31 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.8 | 12.5% High Exploitation Risk | Directly Exposed |
| CVE-2020-36179 | CRITICAL9.31 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.8, 2.6.7.5 | 20.9% High Exploitation Risk | Directly Exposed |
| CVE-2020-36184 | CRITICAL9.31 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.8 | 10.4% High Exploitation Risk | Directly Exposed |
| CVE-2020-36188 | CRITICAL9.31 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.8, 2.6.7.5 | 10.9% High Exploitation Risk | Directly Exposed |
| CVE-2021-35942 | CRITICAL9.1 | glibc 2.17-260.el7 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35942 | CRITICAL9.1 | glibc-common 2.17-260.el7 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-12403 | CRITICAL9.1 | nspr 4.19.0-1.el7_5 fixed in 4.25.0-2.el7_9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-12403 | CRITICAL9.1 | nss 3.36.0-7.el7_5 fixed in 3.53.1-3.el7_9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-12403 | CRITICAL9.1 | nss-softokn 3.36.0-5.el7_5 fixed in 3.53.1-6.el7_9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-12403 | CRITICAL9.1 | nss-softokn-freebl 3.36.0-5.el7_5 fixed in 3.53.1-6.el7_9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-12403 | CRITICAL9.1 | nss-sysinit 3.36.0-7.el7_5 fixed in 3.53.1-3.el7_9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-12403 | CRITICAL9.1 | nss-util 3.36.0-1.el7_5 fixed in 3.53.1-1.el7_9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-44981 | CRITICAL9.1 | org.apache.zookeeper:zookeeper 3.4.13 fixed in 3.7.2, 3.8.3, 3.9.1 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-2332 | CRITICAL9.1 | org.eclipse.jetty:jetty-http 9.4.14.v20181114 fixed in 12.1.7, 12.0.33 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-11756 | HIGH8.8 | nspr 4.19.0-1.el7_5 fixed in 4.25.0-2.el7_9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-11745 | HIGH8.8 | nss 3.36.0-7.el7_5 fixed in 3.44.0-7.el7_7 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-11756 | HIGH8.8 | nss 3.36.0-7.el7_5 fixed in 3.53.1-3.el7_9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-11745 | HIGH8.8 | nss-softokn 3.36.0-5.el7_5 fixed in 3.44.0-8.el7_7 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-11756 | HIGH8.8 | nss-softokn 3.36.0-5.el7_5 fixed in 3.53.1-6.el7_9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-11745 | HIGH8.8 | nss-softokn-freebl 3.36.0-5.el7_5 fixed in 3.44.0-8.el7_7 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-11756 | HIGH8.8 | nss-softokn-freebl 3.36.0-5.el7_5 fixed in 3.53.1-6.el7_9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-11745 | HIGH8.8 | nss-sysinit 3.36.0-7.el7_5 fixed in 3.44.0-7.el7_7 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-11756 | HIGH8.8 | nss-sysinit 3.36.0-7.el7_5 fixed in 3.53.1-3.el7_9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-11745 | HIGH8.8 | nss-util 3.36.0-1.el7_5 fixed in 3.44.0-4.el7_7 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-11756 | HIGH8.8 | nss-util 3.36.0-1.el7_5 fixed in 3.53.1-1.el7_9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9840 | HIGH8.8 | zlib 1.2.7-18.el7 fixed in 1.2.7-21.el7_9.1 | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10672 | HIGH8.8 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.4 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10673 | HIGH8.8 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.4, 2.6.7.4 | 8.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10968 | HIGH8.8 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.4 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10969 | HIGH8.8 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.4 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-11111 | HIGH8.8 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.4 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-11112 | HIGH8.8 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.4 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2020-11113 | HIGH8.8 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.4 | 6.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-47561 | HIGH8.8 | org.apache.avro:avro 1.8.2 fixed in 1.11.4 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-10899 | HIGH8.8 | org.jolokia:jolokia-core 1.5.0 fixed in 1.6.1 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-12086 | HIGH8.62 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.9, 2.8.11.4, 2.7.9.6, 2.6.7.3 | 21.9% High Exploitation Risk | Directly Exposed |
| CVE-2019-14439 | HIGH8.62 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.9.2, 2.8.11.4, 2.7.9.6, 2.6.7.3 | 10.8% High Exploitation Risk | Directly Exposed |
| CVE-2020-25649 | HIGH8.62 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.6.7.4, 2.9.10.7, 2.10.5.1 | 17.6% High Exploitation Risk | Directly Exposed |
| CVE-2019-10172 | HIGH8.62 | org.codehaus.jackson:jackson-mapper-asl 1.9.13 No fix yet | 17.0% High Exploitation Risk | Directly Exposed |
| CVE-2017-18640 | HIGH8.62 | org.yaml:snakeyaml 1.16 fixed in 1.26 | 26.7% High Exploitation Risk | Directly Exposed |
| CVE-2016-1951 | HIGH8.6 | nspr 4.19.0-1.el7_5 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2650 | HIGH8.45 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 75.1% Actively Exploited | Directly Exposed |
| CVE-2026-31789 | HIGH8.33 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2020-14583 | HIGH8.3 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.262.b10-0.el7_8 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2803 | HIGH8.3 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.252.b09-2.el7_8 | 6.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2805 | HIGH8.3 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.252.b09-2.el7_8 | 4.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14583 | HIGH8.3 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.262.b10-0.el7_8 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2803 | HIGH8.3 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.252.b09-2.el7_8 | 6.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2805 | HIGH8.3 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.252.b09-2.el7_8 | 4.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14583 | HIGH8.3 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.262.b10-0.el7_8 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2803 | HIGH8.3 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.252.b09-2.el7_8 | 6.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2805 | HIGH8.3 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.252.b09-2.el7_8 | 4.1% Low-Moderate Risk | Directly Exposed |
| CVE-2015-8983 | HIGH8.1 | glibc 2.17-260.el7 No fix yet | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2015-8982 | HIGH8.1 | glibc 2.17-260.el7 No fix yet | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2015-8983 | HIGH8.1 | glibc-common 2.17-260.el7 No fix yet | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2015-8982 | HIGH8.1 | glibc-common 2.17-260.el7 No fix yet | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2604 | HIGH8.1 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.242.b08-0.el7_7 | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-30749 | HIGH8.1 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.462.b08-1.el7_9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2604 | HIGH8.1 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.242.b08-0.el7_7 | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-30749 | HIGH8.1 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.462.b08-1.el7_9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2604 | HIGH8.1 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.242.b08-0.el7_7 | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-30749 | HIGH8.1 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.462.b08-1.el7_9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45447 | HIGH8.1 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10650 | HIGH8.1 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.4 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-11619 | HIGH8.1 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.4 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2020-11620 | HIGH8.1 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.4 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14060 | HIGH8.1 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.5 | 8.6% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14061 | HIGH8.1 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.5 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14062 | HIGH8.1 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.5 | 8.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14195 | HIGH8.1 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.5 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-24616 | HIGH8.1 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.6 | 9.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-24750 | HIGH8.1 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.6.7.5, 2.9.10.6 | 7.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-35490 | HIGH8.1 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.8 | 7.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-35491 | HIGH8.1 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.8 | 9.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-36180 | HIGH8.1 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.8, 2.6.7.5 | 5.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-36181 | HIGH8.1 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.8, 2.6.7.5 | 5.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-36182 | HIGH8.1 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.8, 2.6.7.5 | 5.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-36183 | HIGH8.1 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.8, 2.6.7.5 | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2020-36185 | HIGH8.1 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.8 | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-36186 | HIGH8.1 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.8 | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-36187 | HIGH8.1 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.8 | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-36189 | HIGH8.1 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.8, 2.6.7.5 | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20190 | HIGH8.1 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.7, 2.6.7.5 | 7.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-14540 | HIGH8 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10, 2.8.11.5, 2.6.7.3 | 10.8% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2020-8840 | HIGH8 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.6.7.4, 2.7.9.7, 2.8.11.5, 2.9.10.3 | 26.6% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2020-9547 | HIGH8 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.4, 2.8.11.6, 2.7.9.7 | 17.8% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2020-9548 | HIGH8 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10.4, 2.8.11.6, 2.7.9.7 | 18.3% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-31197 | HIGH8 | org.postgresql:postgresql 42.2.5 fixed in 42.2.26, 42.4.1, 42.3.7 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-11023 | HIGH7.93 | libgcc 4.8.5-36.el7 fixed in 4.8.5-45.el7_9 | 83.8% Actively Exploited | Directly Exposed |
| CVE-2020-11023 | HIGH7.93 | libstdc++ 4.8.5-36.el7 fixed in 4.8.5-45.el7_9 | 83.8% Actively Exploited | Directly Exposed |
| CVE-2021-2471 | HIGH7.9 | mysql:mysql-connector-java 8.0.13 fixed in 8.0.27 | 7.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-14379 | HIGH7.84 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.9.2, 2.8.11.4, 2.7.9.6 | 8.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2019-14892 | HIGH7.84 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.6.7.3, 2.8.11.5, 2.9.10 | 5.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2019-14893 | HIGH7.84 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.10 | 4.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2019-10202 | HIGH7.84 | org.codehaus.jackson:jackson-mapper-asl 1.9.13 No fix yet | 5.2% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2016-2226 | HIGH7.8 | libgcc 4.8.5-36.el7 No fix yet | 7.3% Low-Moderate Risk | Directly Exposed |
| CVE-2016-2226 | HIGH7.8 | libstdc++ 4.8.5-36.el7 No fix yet | 7.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-13692 | HIGH7.7 | org.postgresql:postgresql 42.2.5 fixed in 42.2.13 | 4.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | glibc 2.17-260.el7 fixed in 2.17-326.el7_9.3 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | glibc-common 2.17-260.el7 fixed in 2.17-326.el7_9.3 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2009-5155 | HIGH7.5 | glibc 2.17-260.el7 No fix yet | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2016-1234 | HIGH7.5 | glibc 2.17-260.el7 No fix yet | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2017-8804 | HIGH7.5 | glibc 2.17-260.el7 No fix yet | 7.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-29573 | HIGH7.5 | glibc 2.17-260.el7 fixed in 2.17-322.el7_9 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5156 | HIGH7.5 | glibc 2.17-260.el7 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2014-4043 | HIGH7.5 | glibc 2.17-260.el7 No fix yet | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2009-5155 | HIGH7.5 | glibc-common 2.17-260.el7 No fix yet | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2016-1234 | HIGH7.5 | glibc-common 2.17-260.el7 No fix yet | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2017-8804 | HIGH7.5 | glibc-common 2.17-260.el7 No fix yet | 7.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-29573 | HIGH7.5 | glibc-common 2.17-260.el7 fixed in 2.17-322.el7_9 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5156 | HIGH7.5 | glibc-common 2.17-260.el7 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2014-4043 | HIGH7.5 | glibc-common 2.17-260.el7 No fix yet | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2017-10118 | HIGH7.5 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2017-10176 | HIGH7.5 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 No fix yet | 5.0% Low-Moderate Risk | Directly Exposed |
| CVE-2017-10118 | HIGH7.5 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2017-10176 | HIGH7.5 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 No fix yet | 5.0% Low-Moderate Risk | Directly Exposed |
| CVE-2017-10118 | HIGH7.5 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2017-10176 | HIGH7.5 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 No fix yet | 5.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-16276 | HIGH7.5 | libgcc 4.8.5-36.el7 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-16845 | HIGH7.5 | libgcc 4.8.5-36.el7 No fix yet | 4.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-28362 | HIGH7.5 | libgcc 4.8.5-36.el7 No fix yet | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2020-28366 | HIGH7.5 | libgcc 4.8.5-36.el7 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-28367 | HIGH7.5 | libgcc 4.8.5-36.el7 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-27918 | HIGH7.5 | libgcc 4.8.5-36.el7 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20657 | HIGH7.5 | libgcc 4.8.5-36.el7 No fix yet | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-16276 | HIGH7.5 | libstdc++ 4.8.5-36.el7 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-16845 | HIGH7.5 | libstdc++ 4.8.5-36.el7 No fix yet | 4.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-28362 | HIGH7.5 | libstdc++ 4.8.5-36.el7 No fix yet | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2020-28366 | HIGH7.5 | libstdc++ 4.8.5-36.el7 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-28367 | HIGH7.5 | libstdc++ 4.8.5-36.el7 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-27918 | HIGH7.5 | libstdc++ 4.8.5-36.el7 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20657 | HIGH7.5 | libstdc++ 4.8.5-36.el7 No fix yet | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-11719 | HIGH7.5 | nspr 4.19.0-1.el7_5 fixed in 4.25.0-2.el7_9 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-17007 | HIGH7.5 | nspr 4.19.0-1.el7_5 fixed in 4.21.0-1.el7 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-11719 | HIGH7.5 | nss 3.36.0-7.el7_5 fixed in 3.53.1-3.el7_9 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-11729 | HIGH7.5 | nss 3.36.0-7.el7_5 fixed in 3.44.0-7.el7_7 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-17007 | HIGH7.5 | nss 3.36.0-7.el7_5 fixed in 3.44.0-4.el7 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25648 | HIGH7.5 | nss 3.36.0-7.el7_5 fixed in 3.53.1-7.el7_9 | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2019-11719 | HIGH7.5 | nss-softokn 3.36.0-5.el7_5 fixed in 3.53.1-6.el7_9 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-11729 | HIGH7.5 | nss-softokn 3.36.0-5.el7_5 fixed in 3.44.0-8.el7_7 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-17007 | HIGH7.5 | nss-softokn 3.36.0-5.el7_5 fixed in 3.44.0-5.el7 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-11719 | HIGH7.5 | nss-softokn-freebl 3.36.0-5.el7_5 fixed in 3.53.1-6.el7_9 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-11729 | HIGH7.5 | nss-softokn-freebl 3.36.0-5.el7_5 fixed in 3.44.0-8.el7_7 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-17007 | HIGH7.5 | nss-softokn-freebl 3.36.0-5.el7_5 fixed in 3.44.0-5.el7 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-11719 | HIGH7.5 | nss-sysinit 3.36.0-7.el7_5 fixed in 3.53.1-3.el7_9 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-11729 | HIGH7.5 | nss-sysinit 3.36.0-7.el7_5 fixed in 3.44.0-7.el7_7 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-17007 | HIGH7.5 | nss-sysinit 3.36.0-7.el7_5 fixed in 3.44.0-4.el7 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25648 | HIGH7.5 | nss-sysinit 3.36.0-7.el7_5 fixed in 3.53.1-7.el7_9 | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2019-11719 | HIGH7.5 | nss-util 3.36.0-1.el7_5 fixed in 3.53.1-1.el7_9 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-11729 | HIGH7.5 | nss-util 3.36.0-1.el7_5 fixed in 3.44.0-4.el7_7 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-17007 | HIGH7.5 | nss-util 3.36.0-1.el7_5 fixed in 3.44.0-3.el7 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0215 | HIGH7.5 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28390 | HIGH7.5 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3358 | HIGH7.5 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0464 | HIGH7.5 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28388 | HIGH7.5 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28389 | HIGH7.5 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-29361 | HIGH7.5 | p11-kit 0.23.5-3.el7 No fix yet | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-29361 | HIGH7.5 | p11-kit-trust 0.23.5-3.el7 No fix yet | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-36518 | HIGH7.5 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.13.2.1, 2.12.6.1 | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42003 | HIGH7.5 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.12.7.1, 2.13.4.2 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42004 | HIGH7.5 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.12.7.1, 2.13.4 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-7254 | HIGH7.5 | com.google.protobuf:protobuf-java 2.6.1 fixed in 3.25.5, 4.27.5, 4.28.2 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3171 | HIGH7.5 | com.google.protobuf:protobuf-java 2.6.1 fixed in 3.21.7, 3.20.3, 3.19.6, 3.16.3 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-26464 | HIGH7.5 | log4j:log4j 1.2.17 fixed in 2.0 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-39410 | HIGH7.5 | org.apache.avro:avro 1.8.2 fixed in 1.11.3 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-34455 | HIGH7.5 | org.xerial.snappy:snappy-java 1.1.7.2 fixed in 1.1.10.1 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-43642 | HIGH7.5 | org.xerial.snappy:snappy-java 1.1.7.2 fixed in 1.1.10.4 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-34453 | HIGH7.5 | org.xerial.snappy:snappy-java 1.1.7.2 fixed in 1.1.10.1 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-34454 | HIGH7.5 | org.xerial.snappy:snappy-java 1.1.7.2 fixed in 1.1.10.1 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25857 | HIGH7.5 | org.yaml:snakeyaml 1.16 fixed in 1.31 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0767 | HIGH7.48 | nss 3.36.0-7.el7_5 fixed in 3.79.0-5.el7_9 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-0767 | HIGH7.48 | nss-sysinit 3.36.0-7.el7_5 fixed in 3.79.0-5.el7_9 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-27819 | HIGH7.48 | org.apache.kafka:kafka_2.12 2.2.0 fixed in 3.4.0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-67030 | HIGH7.48 | org.codehaus.plexus:plexus-utils 3.1.0 fixed in 4.0.3, 3.6.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2020-14593 | HIGH7.4 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.262.b10-0.el7_8 | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-21930 | HIGH7.4 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.372.b07-1.el7_9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-21147 | HIGH7.4 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.422.b05-1.el7_9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14593 | HIGH7.4 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.262.b10-0.el7_8 | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-21930 | HIGH7.4 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.372.b07-1.el7_9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-21147 | HIGH7.4 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.422.b05-1.el7_9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14593 | HIGH7.4 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.262.b10-0.el7_8 | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-21930 | HIGH7.4 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.372.b07-1.el7_9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-21147 | HIGH7.4 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.422.b05-1.el7_9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-22102 | HIGH7.06 | mysql:mysql-connector-java 8.0.13 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-27223 | MEDIUM6.89 | org.eclipse.jetty:jetty-server 9.4.14.v20181114 fixed in 9.4.37, 10.0.1, 11.0.1 | 78.0% Actively Exploited | Directly Exposed |
| CVE-2021-28169 | MEDIUM6.89 | org.eclipse.jetty:jetty-servlets 9.4.14.v20181114 fixed in 9.4.41, 10.0.3, 11.0.3 | 78.5% Actively Exploited | Directly Exposed |
| CVE-2025-50106 | MEDIUM6.88 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.462.b08-1.el7_9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-50106 | MEDIUM6.88 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.462.b08-1.el7_9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-50106 | MEDIUM6.88 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.462.b08-1.el7_9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2019-2949 | MEDIUM6.8 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2601 | MEDIUM6.8 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.242.b08-0.el7_7 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35567 | MEDIUM6.8 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2989 | MEDIUM6.8 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2949 | MEDIUM6.8 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2601 | MEDIUM6.8 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.242.b08-0.el7_7 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35567 | MEDIUM6.8 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2989 | MEDIUM6.8 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2949 | MEDIUM6.8 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2601 | MEDIUM6.8 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.242.b08-0.el7_7 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35567 | MEDIUM6.8 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2989 | MEDIUM6.8 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-12404 | MEDIUM6.79 | nspr 4.19.0-1.el7_5 fixed in 4.21.0-1.el7 | 44.4% High Exploitation Risk | Directly Exposed |
| CVE-2018-12404 | MEDIUM6.79 | nss 3.36.0-7.el7_5 fixed in 3.44.0-4.el7 | 44.4% High Exploitation Risk | Directly Exposed |
| CVE-2018-12404 | MEDIUM6.79 | nss-softokn 3.36.0-5.el7_5 fixed in 3.44.0-5.el7 | 44.4% High Exploitation Risk | Directly Exposed |
| CVE-2018-12404 | MEDIUM6.79 | nss-softokn-freebl 3.36.0-5.el7_5 fixed in 3.44.0-5.el7 | 44.4% High Exploitation Risk | Directly Exposed |
| CVE-2018-12404 | MEDIUM6.79 | nss-sysinit 3.36.0-7.el7_5 fixed in 3.44.0-4.el7 | 44.4% High Exploitation Risk | Directly Exposed |
| CVE-2018-12404 | MEDIUM6.79 | nss-util 3.36.0-1.el7_5 fixed in 3.44.0-3.el7 | 44.4% High Exploitation Risk | Directly Exposed |
| CVE-2019-1559 | MEDIUM6.79 | openssl-libs 1:1.0.2k-16.el7 fixed in 1:1.0.2k-19.el7 | 17.1% High Exploitation Risk | Directly Exposed |
| CVE-2022-4304 | MEDIUM6.79 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 16.2% High Exploitation Risk | Directly Exposed |
| CVE-2018-0734 | MEDIUM6.79 | openssl-libs 1:1.0.2k-16.el7 fixed in 1:1.0.2k-19.el7 | 12.2% High Exploitation Risk | Directly Exposed |
| CVE-2019-12384 | MEDIUM6.79 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.9.1, 2.8.11.4, 2.7.9.6, 2.6.7.3 | 45.2% High Exploitation Risk | Directly Exposed |
| CVE-2019-12814 | MEDIUM6.79 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.9.9.1, 2.8.11.4, 2.7.9.6, 2.6.7.3 | 11.0% High Exploitation Risk | Directly Exposed |
| CVE-2021-3999 | MEDIUM6.63 | glibc 2.17-260.el7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-3999 | MEDIUM6.63 | glibc-common 2.17-260.el7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-3826 | MEDIUM6.5 | libgcc 4.8.5-36.el7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3826 | MEDIUM6.5 | libstdc++ 4.8.5-36.el7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-17023 | MEDIUM6.5 | nspr 4.19.0-1.el7_5 fixed in 4.25.0-2.el7_9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18508 | MEDIUM6.5 | nss 3.36.0-7.el7_5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-17023 | MEDIUM6.5 | nss 3.36.0-7.el7_5 fixed in 3.53.1-3.el7_9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2016-1938 | MEDIUM6.5 | nss-softokn 3.36.0-5.el7_5 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-17023 | MEDIUM6.5 | nss-softokn 3.36.0-5.el7_5 fixed in 3.53.1-6.el7_9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2016-1938 | MEDIUM6.5 | nss-softokn-freebl 3.36.0-5.el7_5 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-17023 | MEDIUM6.5 | nss-softokn-freebl 3.36.0-5.el7_5 fixed in 3.53.1-6.el7_9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18508 | MEDIUM6.5 | nss-sysinit 3.36.0-7.el7_5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-17023 | MEDIUM6.5 | nss-sysinit 3.36.0-7.el7_5 fixed in 3.53.1-3.el7_9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-17023 | MEDIUM6.5 | nss-util 3.36.0-1.el7_5 fixed in 3.53.1-1.el7_9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6129 | MEDIUM6.5 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-8184 | MEDIUM6.5 | org.eclipse.jetty:jetty-server 9.4.14.v20181114 fixed in 12.0.9, 10.0.24, 11.0.24, 9.4.56 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-38749 | MEDIUM6.5 | org.yaml:snakeyaml 1.16 fixed in 1.31 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-38751 | MEDIUM6.5 | org.yaml:snakeyaml 1.16 fixed in 1.31 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-38752 | MEDIUM6.5 | org.yaml:snakeyaml 1.16 fixed in 1.32 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41854 | MEDIUM6.5 | org.yaml:snakeyaml 1.16 fixed in 1.32 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2015-2808 | MEDIUM6.5 | nss 3.36.0-7.el7_5 No fix yet | 73.9% Actively Exploited | Directly Exposed |
| CVE-2015-2808 | MEDIUM6.5 | nss-sysinit 3.36.0-7.el7_5 No fix yet | 73.9% Actively Exploited | Directly Exposed |
| CVE-2015-2808 | MEDIUM6.5 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 73.9% Actively Exploited | Directly Exposed |
| CVE-2026-21945 | MEDIUM6.38 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.482.b08-1.el7_9 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-22016 | MEDIUM6.38 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.492.b09-1.el7_9 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-47057 | MEDIUM6.38 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.502.b07-1.1.el7_9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-47063 | MEDIUM6.38 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.502.b07-1.1.el7_9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41254 | MEDIUM6.38 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.502.b07-1.1.el7_9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-21945 | MEDIUM6.38 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.482.b08-1.el7_9 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-22016 | MEDIUM6.38 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.492.b09-1.el7_9 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-47057 | MEDIUM6.38 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.502.b07-1.1.el7_9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-47063 | MEDIUM6.38 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.502.b07-1.1.el7_9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41254 | MEDIUM6.38 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.502.b07-1.1.el7_9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-21945 | MEDIUM6.38 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.482.b08-1.el7_9 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-22016 | MEDIUM6.38 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.492.b09-1.el7_9 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-47057 | MEDIUM6.38 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.502.b07-1.1.el7_9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-47063 | MEDIUM6.38 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.502.b07-1.1.el7_9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41254 | MEDIUM6.38 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.502.b07-1.1.el7_9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-52999 | MEDIUM6.38 | com.fasterxml.jackson.core:jackson-core 2.9.8 fixed in 2.15.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-9823 | MEDIUM6.38 | org.eclipse.jetty:jetty-servlets 9.4.14.v20181114 fixed in 9.4.54, 10.0.18, 11.0.18 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-66566 | MEDIUM6.38 | org.lz4:lz4-java 1.5.0 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42198 | MEDIUM6.38 | org.postgresql:postgresql 42.2.5 fixed in 42.7.11 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-20918 | MEDIUM6.29 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.402.b06-1.el7_9 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-20952 | MEDIUM6.29 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.402.b06-1.el7_9 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-47058 | MEDIUM6.29 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.502.b07-1.1.el7_9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-21587 | MEDIUM6.29 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.452.b09-1.el7_9 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-20918 | MEDIUM6.29 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.402.b06-1.el7_9 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-20952 | MEDIUM6.29 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.402.b06-1.el7_9 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-47058 | MEDIUM6.29 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.502.b07-1.1.el7_9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-21587 | MEDIUM6.29 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.452.b09-1.el7_9 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-20918 | MEDIUM6.29 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.402.b06-1.el7_9 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-20952 | MEDIUM6.29 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.402.b06-1.el7_9 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-47058 | MEDIUM6.29 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.502.b07-1.1.el7_9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-21587 | MEDIUM6.29 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.452.b09-1.el7_9 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-56128 | MEDIUM6.29 | org.apache.kafka:kafka_2.12 2.2.0 fixed in 3.7.2, 3.8.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-13009 | MEDIUM6.12 | org.eclipse.jetty:jetty-server 9.4.14.v20181114 fixed in 9.4.57.v20241219 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-24553 | MEDIUM6.1 | libgcc 4.8.5-36.el7 No fix yet | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2020-24553 | MEDIUM6.1 | libstdc++ 4.8.5-36.el7 No fix yet | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-10241 | MEDIUM6.1 | org.eclipse.jetty:jetty-server 9.4.14.v20181114 fixed in 9.2.27.v20190403, 9.3.26.v20190403, 9.4.16.v20190411 | 9.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35559 | MEDIUM6.09 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 14.8% High Exploitation Risk | Directly Exposed |
| CVE-2021-35559 | MEDIUM6.09 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 14.8% High Exploitation Risk | Directly Exposed |
| CVE-2021-35559 | MEDIUM6.09 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 14.8% High Exploitation Risk | Directly Exposed |
| CVE-2019-1551 | MEDIUM6.09 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 14.3% High Exploitation Risk | Directly Exposed |
| CVE-2023-48161 | MEDIUM6.03 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.432.b06-1.el7_9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-48161 | MEDIUM6.03 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.432.b06-1.el7_9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-48161 | MEDIUM6.03 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.432.b06-1.el7_9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-2976 | MEDIUM6.03 | com.google.guava:guava 11.0.2 fixed in 32.0.0-android | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-2976 | MEDIUM6.03 | com.google.guava:guava 20.0 fixed in 32.0.0-android | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-23305 | MEDIUM6 | log4j:log4j 1.2.17 No fix yet | 66.5% Actively Exploited | Directly Exposed |
| CVE-2022-21363 | MEDIUM6 | mysql:mysql-connector-java 8.0.13 fixed in 8.0.28 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-1752 | MEDIUM5.95 | glibc 2.17-260.el7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | glibc 2.17-260.el7 fixed in 2.17-326.el7_9.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-1752 | MEDIUM5.95 | glibc-common 2.17-260.el7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | glibc-common 2.17-260.el7 fixed in 2.17-326.el7_9.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2016-4429 | MEDIUM5.9 | glibc 2.17-260.el7 No fix yet | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2019-25013 | MEDIUM5.9 | glibc 2.17-260.el7 fixed in 2.17-322.el7_9 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | glibc 2.17-260.el7 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | glibc 2.17-260.el7 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2015-8984 | MEDIUM5.9 | glibc 2.17-260.el7 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2015-8985 | MEDIUM5.9 | glibc 2.17-260.el7 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-10228 | MEDIUM5.9 | glibc 2.17-260.el7 No fix yet | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2017-15671 | MEDIUM5.9 | glibc 2.17-260.el7 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-4429 | MEDIUM5.9 | glibc-common 2.17-260.el7 No fix yet | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2019-25013 | MEDIUM5.9 | glibc-common 2.17-260.el7 fixed in 2.17-322.el7_9 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | glibc-common 2.17-260.el7 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | glibc-common 2.17-260.el7 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2015-8984 | MEDIUM5.9 | glibc-common 2.17-260.el7 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2015-8985 | MEDIUM5.9 | glibc-common 2.17-260.el7 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-10228 | MEDIUM5.9 | glibc-common 2.17-260.el7 No fix yet | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2017-15671 | MEDIUM5.9 | glibc-common 2.17-260.el7 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35550 | MEDIUM5.9 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 6.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21541 | MEDIUM5.9 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.342.b07-1.el7_9 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-21954 | MEDIUM5.9 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.372.b07-1.el7_9 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-21967 | MEDIUM5.9 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.372.b07-1.el7_9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-20926 | MEDIUM5.9 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.402.b06-1.el7_9 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35550 | MEDIUM5.9 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 6.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21541 | MEDIUM5.9 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.342.b07-1.el7_9 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-21954 | MEDIUM5.9 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.372.b07-1.el7_9 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-21967 | MEDIUM5.9 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.372.b07-1.el7_9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-20926 | MEDIUM5.9 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.402.b06-1.el7_9 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35550 | MEDIUM5.9 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 6.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21541 | MEDIUM5.9 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.342.b07-1.el7_9 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-21954 | MEDIUM5.9 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.372.b07-1.el7_9 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-21967 | MEDIUM5.9 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.372.b07-1.el7_9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-20926 | MEDIUM5.9 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.402.b06-1.el7_9 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9074 | MEDIUM5.9 | nss 3.36.0-7.el7_5 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9574 | MEDIUM5.9 | nss 3.36.0-7.el7_5 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7781 | MEDIUM5.9 | nss-softokn 3.36.0-5.el7_5 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7781 | MEDIUM5.9 | nss-softokn-freebl 3.36.0-5.el7_5 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9074 | MEDIUM5.9 | nss-sysinit 3.36.0-7.el7_5 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9574 | MEDIUM5.9 | nss-sysinit 3.36.0-7.el7_5 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-1971 | MEDIUM5.9 | openssl-libs 1:1.0.2k-16.el7 fixed in 1:1.0.2k-21.el7_9 | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-23841 | MEDIUM5.9 | openssl-libs 1:1.0.2k-16.el7 fixed in 1:1.0.2k-22.el7_9 | 7.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-0735 | MEDIUM5.9 | openssl-libs 1:1.0.2k-16.el7 fixed in 1:1.0.2k-16.el7_6.1 | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-41996 | MEDIUM5.9 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-5535 | MEDIUM5.9 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-10237 | MEDIUM5.9 | com.google.guava:guava 11.0.2 fixed in 24.1.1-android | 5.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-10237 | MEDIUM5.9 | com.google.guava:guava 20.0 fixed in 24.1.1-android | 5.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-38153 | MEDIUM5.9 | org.apache.kafka:kafka-clients 2.2.0 fixed in 2.6.3, 2.7.2, 2.8.1 | 6.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-38153 | MEDIUM5.9 | org.apache.kafka:kafka_2.12 2.2.0 fixed in 2.6.3, 2.7.2, 2.8.1 | 6.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-0201 | MEDIUM5.9 | org.apache.zookeeper:zookeeper 3.4.13 fixed in 3.4.14, 3.5.5 | 9.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7614 | MEDIUM5.88 | binutils 2.27-34.base.el7 No fix yet | 3.8% Low-Moderate Risk | Post-Exploit |
| CVE-2018-12699 | MEDIUM5.88 | binutils 2.27-34.base.el7 No fix yet | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2015-4042 | MEDIUM5.88 | coreutils 8.22-23.el7 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2016-8618 | MEDIUM5.88 | curl 7.29.0-51.el7 No fix yet | 4.6% Low-Moderate Risk | Post-Exploit |
| CVE-2016-8619 | MEDIUM5.88 | curl 7.29.0-51.el7 No fix yet | 5.0% Low-Moderate Risk | Post-Exploit |
| CVE-2016-8622 | MEDIUM5.88 | curl 7.29.0-51.el7 No fix yet | 4.7% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3520 | MEDIUM5.88 | lz4 1.7.5-2.el7 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-10160 | MEDIUM5.88 | python 2.7.5-76.el7 fixed in 2.7.5-80.el7_6 | 5.4% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9636 | MEDIUM5.88 | python 2.7.5-76.el7 fixed in 2.7.5-77.el7_6 | 9.1% Low-Moderate Risk | Post-Exploit |
| CVE-2017-1000158 | MEDIUM5.88 | python 2.7.5-76.el7 No fix yet | 8.2% Low-Moderate Risk | Post-Exploit |
| CVE-2020-27619 | MEDIUM5.88 | python 2.7.5-76.el7 No fix yet | 8.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-48565 | MEDIUM5.88 | python 2.7.5-76.el7 No fix yet | 4.3% Low-Moderate Risk | Post-Exploit |
| CVE-2020-35527 | MEDIUM5.88 | sqlite 3.7.17-8.el7 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2017-10989 | MEDIUM5.88 | sqlite 3.7.17-8.el7 No fix yet | 8.6% Low-Moderate Risk | Post-Exploit |
| CVE-2017-5953 | MEDIUM5.88 | vim-minimal 2:7.4.160-5.el7 No fix yet | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2017-6350 | MEDIUM5.88 | vim-minimal 2:7.4.160-5.el7 No fix yet | 3.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-3520 | MEDIUM5.88 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2020-14792 | MEDIUM5.8 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.272.b10-1.el7_9 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14792 | MEDIUM5.8 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.272.b10-1.el7_9 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14792 | MEDIUM5.8 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.272.b10-1.el7_9 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-42574 | MEDIUM5.73 | binutils 2.27-34.base.el7 fixed in 2.27-44.base.el7_9.1 | 12.2% High Exploitation Risk | Post-Exploit |
| CVE-2025-9230 | MEDIUM5.6 | openssl-libs 1:1.0.2k-16.el7 fixed in 1:1.0.2k-26.el7_9.1 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc 2.17-260.el7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc-common 2.17-260.el7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-60147 | MEDIUM5.52 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.502.b07-1.1.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-60147 | MEDIUM5.52 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.502.b07-1.1.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-60147 | MEDIUM5.52 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.502.b07-1.1.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-5388 | MEDIUM5.52 | nss 3.36.0-7.el7_5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-7531 | MEDIUM5.52 | nss 3.36.0-7.el7_5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-5388 | MEDIUM5.52 | nss-sysinit 3.36.0-7.el7_5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-7531 | MEDIUM5.52 | nss-sysinit 3.36.0-7.el7_5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11143 | MEDIUM5.52 | org.eclipse.jetty:jetty-http 9.4.14.v20181114 fixed in 12.0.31, 12.1.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-12183 | MEDIUM5.52 | org.lz4:lz4-java 1.5.0 fixed in 1.8.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libgcc 4.8.5-36.el7 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2016-4487 | MEDIUM5.5 | libgcc 4.8.5-36.el7 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2016-4488 | MEDIUM5.5 | libgcc 4.8.5-36.el7 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2016-4489 | MEDIUM5.5 | libgcc 4.8.5-36.el7 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2016-4490 | MEDIUM5.5 | libgcc 4.8.5-36.el7 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2016-4491 | MEDIUM5.5 | libgcc 4.8.5-36.el7 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2016-4493 | MEDIUM5.5 | libgcc 4.8.5-36.el7 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-14250 | MEDIUM5.5 | libgcc 4.8.5-36.el7 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libstdc++ 4.8.5-36.el7 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2016-4487 | MEDIUM5.5 | libstdc++ 4.8.5-36.el7 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2016-4488 | MEDIUM5.5 | libstdc++ 4.8.5-36.el7 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2016-4489 | MEDIUM5.5 | libstdc++ 4.8.5-36.el7 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2016-4490 | MEDIUM5.5 | libstdc++ 4.8.5-36.el7 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2016-4491 | MEDIUM5.5 | libstdc++ 4.8.5-36.el7 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2016-4493 | MEDIUM5.5 | libstdc++ 4.8.5-36.el7 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-14250 | MEDIUM5.5 | libstdc++ 4.8.5-36.el7 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-22569 | MEDIUM5.5 | com.google.protobuf:protobuf-java 2.6.1 fixed in 3.16.1, 3.18.2, 3.19.2 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-38750 | MEDIUM5.5 | org.yaml:snakeyaml 1.16 fixed in 1.31 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2017-6969 | MEDIUM5.46 | binutils 2.27-34.base.el7 No fix yet | 3.7% Low-Moderate Risk | Post-Exploit |
| CVE-2017-7226 | MEDIUM5.46 | binutils 2.27-34.base.el7 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2018-16842 | MEDIUM5.46 | curl 7.29.0-51.el7 fixed in 7.29.0-54.el7 | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-5436 | MEDIUM5.38 | curl 7.29.0-51.el7 fixed in 7.29.0-57.el7 | 49.7% High Exploitation Risk | Post-Exploit |
| CVE-2019-2692 | MEDIUM5.35 | mysql:mysql-connector-java 8.0.13 fixed in 8.0.16 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | glibc 2.17-260.el7 fixed in 2.17-326.el7_9.3 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | glibc-common 2.17-260.el7 fixed in 2.17-326.el7_9.3 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35565 | MEDIUM5.3 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 6.9% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2762 | MEDIUM5.3 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.222.b10-0.el7_6 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2769 | MEDIUM5.3 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.222.b10-0.el7_6 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14621 | MEDIUM5.3 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.262.b10-0.el7_8 | 4.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2781 | MEDIUM5.3 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.252.b09-2.el7_8 | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2830 | MEDIUM5.3 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.252.b09-2.el7_8 | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35556 | MEDIUM5.3 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 7.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35561 | MEDIUM5.3 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 6.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35564 | MEDIUM5.3 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35578 | MEDIUM5.3 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 6.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35586 | MEDIUM5.3 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 6.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21496 | MEDIUM5.3 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.332.b09-1.el7_9 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21540 | MEDIUM5.3 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.342.b07-1.el7_9 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21626 | MEDIUM5.3 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.352.b08-2.el7_9 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21628 | MEDIUM5.3 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.352.b08-2.el7_9 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-21830 | MEDIUM5.3 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.362.b08-1.el7_9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-21939 | MEDIUM5.3 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.372.b07-1.el7_9 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-22081 | MEDIUM5.3 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.392.b08-2.el7_9 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35565 | MEDIUM5.3 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 6.9% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2762 | MEDIUM5.3 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.222.b10-0.el7_6 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2769 | MEDIUM5.3 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.222.b10-0.el7_6 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14621 | MEDIUM5.3 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.262.b10-0.el7_8 | 4.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2781 | MEDIUM5.3 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.252.b09-2.el7_8 | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2830 | MEDIUM5.3 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.252.b09-2.el7_8 | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35556 | MEDIUM5.3 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 7.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35561 | MEDIUM5.3 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 6.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35564 | MEDIUM5.3 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35578 | MEDIUM5.3 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 6.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35586 | MEDIUM5.3 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 6.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21496 | MEDIUM5.3 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.332.b09-1.el7_9 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21540 | MEDIUM5.3 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.342.b07-1.el7_9 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21626 | MEDIUM5.3 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.352.b08-2.el7_9 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21628 | MEDIUM5.3 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.352.b08-2.el7_9 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-21830 | MEDIUM5.3 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.362.b08-1.el7_9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-21939 | MEDIUM5.3 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.372.b07-1.el7_9 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-22081 | MEDIUM5.3 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.392.b08-2.el7_9 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35565 | MEDIUM5.3 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 6.9% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2762 | MEDIUM5.3 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.222.b10-0.el7_6 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2769 | MEDIUM5.3 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.222.b10-0.el7_6 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14621 | MEDIUM5.3 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.262.b10-0.el7_8 | 4.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2781 | MEDIUM5.3 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.252.b09-2.el7_8 | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2830 | MEDIUM5.3 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.252.b09-2.el7_8 | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35556 | MEDIUM5.3 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 7.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35561 | MEDIUM5.3 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 6.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35564 | MEDIUM5.3 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35578 | MEDIUM5.3 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 6.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35586 | MEDIUM5.3 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 6.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21496 | MEDIUM5.3 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.332.b09-1.el7_9 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21540 | MEDIUM5.3 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.342.b07-1.el7_9 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21626 | MEDIUM5.3 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.352.b08-2.el7_9 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21628 | MEDIUM5.3 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.352.b08-2.el7_9 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-21830 | MEDIUM5.3 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.362.b08-1.el7_9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-21939 | MEDIUM5.3 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.372.b07-1.el7_9 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-22081 | MEDIUM5.3 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.392.b08-2.el7_9 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-6829 | MEDIUM5.3 | nspr 4.19.0-1.el7_5 fixed in 4.25.0-2.el7_9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-11727 | MEDIUM5.3 | nspr 4.19.0-1.el7_5 fixed in 4.25.0-2.el7_9 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-6829 | MEDIUM5.3 | nss 3.36.0-7.el7_5 fixed in 3.53.1-3.el7_9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-11727 | MEDIUM5.3 | nss 3.36.0-7.el7_5 fixed in 3.53.1-3.el7_9 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-6829 | MEDIUM5.3 | nss-softokn 3.36.0-5.el7_5 fixed in 3.53.1-6.el7_9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-11727 | MEDIUM5.3 | nss-softokn 3.36.0-5.el7_5 fixed in 3.53.1-6.el7_9 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-6829 | MEDIUM5.3 | nss-softokn-freebl 3.36.0-5.el7_5 fixed in 3.53.1-6.el7_9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-11727 | MEDIUM5.3 | nss-softokn-freebl 3.36.0-5.el7_5 fixed in 3.53.1-6.el7_9 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-6829 | MEDIUM5.3 | nss-sysinit 3.36.0-7.el7_5 fixed in 3.53.1-3.el7_9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-11727 | MEDIUM5.3 | nss-sysinit 3.36.0-7.el7_5 fixed in 3.53.1-3.el7_9 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-6829 | MEDIUM5.3 | nss-util 3.36.0-1.el7_5 fixed in 3.53.1-1.el7_9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-11727 | MEDIUM5.3 | nss-util 3.36.0-1.el7_5 fixed in 3.53.1-1.el7_9 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0466 | MEDIUM5.3 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0465 | MEDIUM5.3 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3446 | MEDIUM5.3 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 6.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3817 | MEDIUM5.3 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5678 | MEDIUM5.3 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-29362 | MEDIUM5.3 | p11-kit 0.23.5-3.el7 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-29362 | MEDIUM5.3 | p11-kit-trust 0.23.5-3.el7 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-40167 | MEDIUM5.3 | org.eclipse.jetty:jetty-http 9.4.14.v20181114 fixed in 9.4.52, 10.0.16, 11.0.16, 12.0.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-10246 | MEDIUM5.3 | org.eclipse.jetty:jetty-server 9.4.14.v20181114 fixed in 9.2.28.v20190418, 9.3.27.v20190418, 9.4.17.v20190418 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-10247 | MEDIUM5.3 | org.eclipse.jetty:jetty-server 9.4.14.v20181114 fixed in 9.2.28.v20190418, 9.3.27.v20190418, 9.4.17.v20190418 | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-26048 | MEDIUM5.3 | org.eclipse.jetty:jetty-server 9.4.14.v20181114 fixed in 9.4.51.v20230217, 10.0.14, 11.0.14 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-26049 | MEDIUM5.3 | org.eclipse.jetty:jetty-server 9.4.14.v20181114 fixed in 9.4.51.v20230217, 10.0.14, 11.0.14, 12.0.0.beta0 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-27534 | MEDIUM5.28 | curl 7.29.0-51.el7 No fix yet | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1271 | MEDIUM5.28 | gzip 1.5-10.el7 fixed in 1.5-11.el7_9 | 4.3% Low-Moderate Risk | Post-Exploit |
| CVE-2019-13734 | MEDIUM5.28 | sqlite 3.7.17-8.el7 fixed in 3.7.17-8.el7_7.1 | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2017-7000 | MEDIUM5.28 | sqlite 3.7.17-8.el7 No fix yet | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2019-5827 | MEDIUM5.28 | sqlite 3.7.17-8.el7 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1271 | MEDIUM5.28 | xz 5.2.2-1.el7 fixed in 5.2.2-2.el7_9 | 4.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-13757 | MEDIUM5.27 | p11-kit 0.23.5-3.el7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | p11-kit-trust 0.23.5-3.el7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-21933 | MEDIUM5.18 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.482.b08-1.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-21933 | MEDIUM5.18 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.482.b08-1.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-21933 | MEDIUM5.18 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.482.b08-1.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-6602 | MEDIUM5.18 | nss 3.36.0-7.el7_5 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-6602 | MEDIUM5.18 | nss-sysinit 3.36.0-7.el7_5 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-43551 | MEDIUM5.17 | curl 7.29.0-51.el7 No fix yet | 16.5% High Exploitation Risk | Post-Exploit |
| CVE-2024-2398 | MEDIUM5.17 | curl 7.29.0-51.el7 No fix yet | 36.1% High Exploitation Risk | Post-Exploit |
| CVE-2023-24329 | MEDIUM5.17 | python 2.7.5-76.el7 fixed in 2.7.5-93.el7_9 | 20.5% High Exploitation Risk | Post-Exploit |
| CVE-2018-14647 | MEDIUM5.17 | python 2.7.5-76.el7 fixed in 2.7.5-86.el7 | 11.3% High Exploitation Risk | Post-Exploit |
| CVE-2019-5010 | MEDIUM5.17 | python 2.7.5-76.el7 fixed in 2.7.5-86.el7 | 21.4% High Exploitation Risk | Post-Exploit |
| CVE-2021-3737 | MEDIUM5.17 | python 2.7.5-76.el7 No fix yet | 12.0% High Exploitation Risk | Post-Exploit |
| CVE-2015-7036 | MEDIUM5.17 | sqlite 3.7.17-8.el7 No fix yet | 39.3% High Exploitation Risk | Post-Exploit |
| CVE-2022-35737 | MEDIUM5.17 | sqlite 3.7.17-8.el7 No fix yet | 18.0% High Exploitation Risk | Post-Exploit |
| CVE-2016-6321 | MEDIUM5.17 | tar 2:1.26-35.el7 No fix yet | 15.2% High Exploitation Risk | Post-Exploit |
| CVE-2021-2388 | MEDIUM5.1 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.302.b08-0.el7_9 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-2388 | MEDIUM5.1 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.302.b08-0.el7_9 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-2388 | MEDIUM5.1 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.302.b08-0.el7_9 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc 2.17-260.el7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | glibc 2.17-260.el7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc-common 2.17-260.el7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | glibc-common 2.17-260.el7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-20919 | MEDIUM5.02 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.402.b06-1.el7_9 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-20921 | MEDIUM5.02 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.402.b06-1.el7_9 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-30761 | MEDIUM5.02 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.462.b08-1.el7_9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-53057 | MEDIUM5.02 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.472.b08-1.el7_9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46968 | MEDIUM5.02 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.502.b07-1.1.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-20919 | MEDIUM5.02 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.402.b06-1.el7_9 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-20921 | MEDIUM5.02 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.402.b06-1.el7_9 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-30761 | MEDIUM5.02 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.462.b08-1.el7_9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-53057 | MEDIUM5.02 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.472.b08-1.el7_9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46968 | MEDIUM5.02 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.502.b07-1.1.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-20919 | MEDIUM5.02 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.402.b06-1.el7_9 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-20921 | MEDIUM5.02 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.402.b06-1.el7_9 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-30761 | MEDIUM5.02 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.462.b08-1.el7_9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-53057 | MEDIUM5.02 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.472.b08-1.el7_9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46968 | MEDIUM5.02 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.502.b07-1.1.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-12413 | MEDIUM5.02 | nss 3.36.0-7.el7_5 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2020-12413 | MEDIUM5.02 | nss-sysinit 3.36.0-7.el7_5 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-15468 | MEDIUM5.02 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-1419 | MEDIUM5.02 | io.debezium:debezium-connector-mysql 0.9.2.Final fixed in 2.3.0.Alpha1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-1419 | MEDIUM5.02 | io.debezium:debezium-connector-sqlserver 0.9.2.Final fixed in 2.3.0.Alpha1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-1419 | MEDIUM5.02 | io.debezium:debezium-core 0.9.2.Final fixed in 2.3.0.Alpha1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-21476 | MEDIUM5 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.332.b09-1.el7_9 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14803 | MEDIUM5 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.272.b10-1.el7_9 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21282 | MEDIUM5 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21283 | MEDIUM5 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21293 | MEDIUM5 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 8.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21294 | MEDIUM5 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21296 | MEDIUM5 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21299 | MEDIUM5 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21305 | MEDIUM5 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21340 | MEDIUM5 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 7.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21341 | MEDIUM5 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21360 | MEDIUM5 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21365 | MEDIUM5 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21426 | MEDIUM5 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.332.b09-1.el7_9 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21434 | MEDIUM5 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.332.b09-1.el7_9 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21476 | MEDIUM5 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.332.b09-1.el7_9 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14803 | MEDIUM5 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.272.b10-1.el7_9 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21282 | MEDIUM5 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21283 | MEDIUM5 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21293 | MEDIUM5 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 8.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21294 | MEDIUM5 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21296 | MEDIUM5 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21299 | MEDIUM5 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21305 | MEDIUM5 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21340 | MEDIUM5 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 7.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21341 | MEDIUM5 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21360 | MEDIUM5 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21365 | MEDIUM5 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21426 | MEDIUM5 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.332.b09-1.el7_9 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21434 | MEDIUM5 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.332.b09-1.el7_9 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21476 | MEDIUM5 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.332.b09-1.el7_9 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14803 | MEDIUM5 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.272.b10-1.el7_9 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21282 | MEDIUM5 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21283 | MEDIUM5 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21293 | MEDIUM5 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 8.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21294 | MEDIUM5 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21296 | MEDIUM5 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21299 | MEDIUM5 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21305 | MEDIUM5 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21340 | MEDIUM5 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 7.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21341 | MEDIUM5 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21360 | MEDIUM5 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21365 | MEDIUM5 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21426 | MEDIUM5 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.332.b09-1.el7_9 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21434 | MEDIUM5 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.332.b09-1.el7_9 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2015-5276 | MEDIUM5 | libgcc 4.8.5-36.el7 No fix yet | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2015-5276 | MEDIUM5 | libstdc++ 4.8.5-36.el7 No fix yet | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2015-2613 | MEDIUM5 | nss-softokn 3.36.0-5.el7_5 No fix yet | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2015-2613 | MEDIUM5 | nss-softokn-freebl 3.36.0-5.el7_5 No fix yet | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27778 | MEDIUM4.86 | curl 7.29.0-51.el7 No fix yet | 3.7% Low-Moderate Risk | Post-Exploit |
| CVE-2016-9586 | MEDIUM4.86 | curl 7.29.0-51.el7 No fix yet | 4.9% Low-Moderate Risk | Post-Exploit |
| CVE-2019-17543 | MEDIUM4.86 | lz4 1.7.5-2.el7 No fix yet | 9.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-2816 | MEDIUM4.8 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.222.b10-0.el7_6 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2975 | MEDIUM4.8 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14556 | MEDIUM4.8 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.262.b10-0.el7_8 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2593 | MEDIUM4.8 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.242.b08-0.el7_7 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2800 | MEDIUM4.8 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.252.b09-2.el7_8 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2816 | MEDIUM4.8 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.222.b10-0.el7_6 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2975 | MEDIUM4.8 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14556 | MEDIUM4.8 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.262.b10-0.el7_8 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2593 | MEDIUM4.8 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.242.b08-0.el7_7 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2800 | MEDIUM4.8 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.252.b09-2.el7_8 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2816 | MEDIUM4.8 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.222.b10-0.el7_6 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2975 | MEDIUM4.8 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14556 | MEDIUM4.8 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.262.b10-0.el7_8 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2593 | MEDIUM4.8 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.242.b08-0.el7_7 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2800 | MEDIUM4.8 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.252.b09-2.el7_8 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2020-27218 | MEDIUM4.8 | org.eclipse.jetty:jetty-server 9.4.14.v20181114 fixed in 9.4.35.v20201120 | 8.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-30698 | MEDIUM4.76 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.452.b09-1.el7_9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-30698 | MEDIUM4.76 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.452.b09-1.el7_9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-30698 | MEDIUM4.76 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.452.b09-1.el7_9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-2999 | MEDIUM4.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2999 | MEDIUM4.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2999 | MEDIUM4.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5407 | MEDIUM4.7 | openssl-libs 1:1.0.2k-16.el7 fixed in 1:1.0.2k-16.el7_6.1 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1547 | MEDIUM4.7 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2007-4559 | MEDIUM4.69 | python 2.7.5-76.el7 No fix yet | 27.1% High Exploitation Risk | Post-Exploit |
| CVE-2019-18276 | MEDIUM4.68 | bash 4.2.46-31.el7 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-18483 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9075 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9077 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2021-20294 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 3.4% Low-Moderate Risk | Post-Exploit |
| CVE-2021-45078 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2016-2226 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 7.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-12449 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2017-12451 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2017-12452 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2017-12453 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2017-12454 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2017-12455 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2017-12456 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2017-12457 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2017-12458 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2017-12799 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 3.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-14729 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-14745 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2017-15020 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2017-15996 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2017-16826 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2017-16827 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2017-16828 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2017-16829 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2017-16830 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2017-16831 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2017-16832 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2017-17121 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2017-17122 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2017-17124 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2017-17125 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2017-17126 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2017-9042 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2017-9043 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2017-9742 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 8.1% Low-Moderate Risk | Post-Exploit |
| CVE-2017-9743 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2017-9744 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2017-9745 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2017-9746 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 8.5% Low-Moderate Risk | Post-Exploit |
| CVE-2017-9747 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 7.9% Low-Moderate Risk | Post-Exploit |
| CVE-2017-9748 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 7.9% Low-Moderate Risk | Post-Exploit |
| CVE-2017-9749 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 8.5% Low-Moderate Risk | Post-Exploit |
| CVE-2017-9750 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 8.1% Low-Moderate Risk | Post-Exploit |
| CVE-2017-9751 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2017-9752 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2017-9753 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2017-9754 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2017-9755 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2017-9756 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 8.1% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6323 | MEDIUM4.68 | binutils 2.27-34.base.el7 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-38185 | MEDIUM4.68 | cpio 2.11-27.el7 No fix yet | 4.1% Low-Moderate Risk | Post-Exploit |
| CVE-2020-8177 | MEDIUM4.68 | curl 7.29.0-51.el7 fixed in 7.29.0-59.el7_9.1 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3778 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3872 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3984 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2021-4019 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-4192 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-0359 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1621 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1629 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28417 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 fixed in 2:7.4.629-8.el7_9.1 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2017-11109 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3927 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3974 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2021-4069 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1154 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1619 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1720 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2124 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2125 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2126 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2129 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2175 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2182 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2183 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2206 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2207 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2210 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2284 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2285 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2286 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2288 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2289 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2343 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2344 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2345 | MEDIUM4.68 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2020-10029 | MEDIUM4.67 | glibc 2.17-260.el7 fixed in 2.17-322.el7_9 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | glibc 2.17-260.el7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-27618 | MEDIUM4.67 | glibc 2.17-260.el7 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-10029 | MEDIUM4.67 | glibc-common 2.17-260.el7 fixed in 2.17-322.el7_9 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | glibc-common 2.17-260.el7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-27618 | MEDIUM4.67 | glibc-common 2.17-260.el7 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | MEDIUM4.67 | libgcc 4.8.5-36.el7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc 4.8.5-36.el7 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | MEDIUM4.67 | libstdc++ 4.8.5-36.el7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libstdc++ 4.8.5-36.el7 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-15469 | MEDIUM4.67 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM4.67 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib 1.2.7-18.el7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-41946 | MEDIUM4.67 | org.postgresql:postgresql 42.2.5 fixed in 42.2.27, 42.3.8, 42.4.3, 42.5.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-17571 | MEDIUM4.58 | log4j:log4j 1.2.17 No fix yet | 66.5% Actively Exploited | Post-Exploit |
| CVE-2022-1471 | MEDIUM4.58 | org.yaml:snakeyaml 1.16 fixed in 2.0 | 99.6% Actively Exploited | Post-Exploit |
| CVE-2017-13710 | MEDIUM4.5 | binutils 2.27-34.base.el7 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2017-15938 | MEDIUM4.5 | binutils 2.27-34.base.el7 No fix yet | 4.7% Low-Moderate Risk | Post-Exploit |
| CVE-2017-7223 | MEDIUM4.5 | binutils 2.27-34.base.el7 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2017-7225 | MEDIUM4.5 | binutils 2.27-34.base.el7 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2017-7227 | MEDIUM4.5 | binutils 2.27-34.base.el7 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2017-7300 | MEDIUM4.5 | binutils 2.27-34.base.el7 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2017-7301 | MEDIUM4.5 | binutils 2.27-34.base.el7 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2017-7302 | MEDIUM4.5 | binutils 2.27-34.base.el7 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2017-7303 | MEDIUM4.5 | binutils 2.27-34.base.el7 No fix yet | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2017-7304 | MEDIUM4.5 | binutils 2.27-34.base.el7 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2017-8392 | MEDIUM4.5 | binutils 2.27-34.base.el7 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2017-8393 | MEDIUM4.5 | binutils 2.27-34.base.el7 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2017-8394 | MEDIUM4.5 | binutils 2.27-34.base.el7 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2017-8395 | MEDIUM4.5 | binutils 2.27-34.base.el7 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2017-8396 | MEDIUM4.5 | binutils 2.27-34.base.el7 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2017-8397 | MEDIUM4.5 | binutils 2.27-34.base.el7 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2017-8398 | MEDIUM4.5 | binutils 2.27-34.base.el7 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-12697 | MEDIUM4.5 | binutils 2.27-34.base.el7 fixed in 2.27-41.base.el7 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2018-12698 | MEDIUM4.5 | binutils 2.27-34.base.el7 No fix yet | 6.7% Low-Moderate Risk | Post-Exploit |
| CVE-2018-12934 | MEDIUM4.5 | binutils 2.27-34.base.el7 No fix yet | 3.3% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20657 | MEDIUM4.5 | binutils 2.27-34.base.el7 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2014-9471 | MEDIUM4.5 | coreutils 8.22-23.el7 No fix yet | 7.1% Low-Moderate Risk | Post-Exploit |
| CVE-2016-8615 | MEDIUM4.5 | curl 7.29.0-51.el7 No fix yet | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2016-8624 | MEDIUM4.5 | curl 7.29.0-51.el7 No fix yet | 5.9% Low-Moderate Risk | Post-Exploit |
| CVE-2016-8625 | MEDIUM4.5 | curl 7.29.0-51.el7 No fix yet | 4.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-1000254 | MEDIUM4.5 | curl 7.29.0-51.el7 No fix yet | 8.5% Low-Moderate Risk | Post-Exploit |
| CVE-2020-8285 | MEDIUM4.5 | curl 7.29.0-51.el7 No fix yet | 9.9% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22946 | MEDIUM4.5 | curl 7.29.0-51.el7 No fix yet | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27780 | MEDIUM4.5 | curl 7.29.0-51.el7 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27782 | MEDIUM4.5 | curl 7.29.0-51.el7 No fix yet | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2016-8621 | MEDIUM4.5 | curl 7.29.0-51.el7 No fix yet | 4.9% Low-Moderate Risk | Post-Exploit |
| CVE-2016-8623 | MEDIUM4.5 | curl 7.29.0-51.el7 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2020-8231 | MEDIUM4.5 | curl 7.29.0-51.el7 No fix yet | 3.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27781 | MEDIUM4.5 | curl 7.29.0-51.el7 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2019-13050 | MEDIUM4.5 | gnupg2 2.0.22-5.el7_5 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9234 | MEDIUM4.5 | gnupg2 2.0.22-5.el7_5 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2018-1123 | MEDIUM4.5 | procps-ng 3.3.10-23.el7 No fix yet | 9.1% Low-Moderate Risk | Post-Exploit |
| CVE-2018-1125 | MEDIUM4.5 | procps-ng 3.3.10-23.el7 No fix yet | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-16056 | MEDIUM4.5 | python 2.7.5-76.el7 fixed in 2.7.5-88.el7 | 5.4% Low-Moderate Risk | Post-Exploit |
| CVE-2019-20907 | MEDIUM4.5 | python 2.7.5-76.el7 fixed in 2.7.5-90.el7 | 6.0% Low-Moderate Risk | Post-Exploit |
| CVE-2020-10735 | MEDIUM4.5 | python 2.7.5-76.el7 No fix yet | 5.9% Low-Moderate Risk | Post-Exploit |
| CVE-2022-0391 | MEDIUM4.5 | python 2.7.5-76.el7 No fix yet | 8.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-45061 | MEDIUM4.5 | python 2.7.5-76.el7 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-48560 | MEDIUM4.5 | python 2.7.5-76.el7 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2024-6232 | MEDIUM4.5 | python 2.7.5-76.el7 No fix yet | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9674 | MEDIUM4.5 | python 2.7.5-76.el7 No fix yet | 5.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-7592 | MEDIUM4.5 | python 2.7.5-76.el7 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19603 | MEDIUM4.5 | sqlite 3.7.17-8.el7 No fix yet | 8.3% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19880 | MEDIUM4.5 | sqlite 3.7.17-8.el7 No fix yet | 6.9% Low-Moderate Risk | Post-Exploit |
| CVE-2019-20218 | MEDIUM4.5 | sqlite 3.7.17-8.el7 No fix yet | 3.6% Low-Moderate Risk | Post-Exploit |
| CVE-2017-15286 | MEDIUM4.5 | sqlite 3.7.17-8.el7 No fix yet | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2018-8740 | MEDIUM4.5 | sqlite 3.7.17-8.el7 No fix yet | 8.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19244 | MEDIUM4.5 | sqlite 3.7.17-8.el7 No fix yet | 3.3% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9923 | MEDIUM4.5 | tar 2:1.26-35.el7 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-3705 | MEDIUM4.5 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5344 | MEDIUM4.5 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2016-10739 | MEDIUM4.5 | glibc 2.17-260.el7 fixed in 2.17-292.el7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | glibc 2.17-260.el7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc 2.17-260.el7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-10739 | MEDIUM4.5 | glibc-common 2.17-260.el7 fixed in 2.17-292.el7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | glibc-common 2.17-260.el7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-common 2.17-260.el7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-22067 | MEDIUM4.5 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.392.b08-2.el7_9 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-22013 | MEDIUM4.5 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.492.b09-1.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22021 | MEDIUM4.5 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.492.b09-1.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23865 | MEDIUM4.5 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.492.b09-1.el7_9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-47021 | MEDIUM4.5 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.502.b07-1.1.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47027 | MEDIUM4.5 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.502.b07-1.1.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-22067 | MEDIUM4.5 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.392.b08-2.el7_9 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-22013 | MEDIUM4.5 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.492.b09-1.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22021 | MEDIUM4.5 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.492.b09-1.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23865 | MEDIUM4.5 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.492.b09-1.el7_9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-47021 | MEDIUM4.5 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.502.b07-1.1.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47027 | MEDIUM4.5 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.502.b07-1.1.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-22067 | MEDIUM4.5 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.392.b08-2.el7_9 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-22013 | MEDIUM4.5 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.492.b09-1.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22021 | MEDIUM4.5 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.492.b09-1.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23865 | MEDIUM4.5 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.492.b09-1.el7_9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-47021 | MEDIUM4.5 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.502.b07-1.1.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47027 | MEDIUM4.5 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.502.b07-1.1.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54514 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 2.18.8, 2.21.4, 3.1.4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54515 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-databind 2.9.8 fixed in 3.1.4, 2.18.9, 2.21.5, 2.22.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-6763 | MEDIUM4.5 | org.eclipse.jetty:jetty-http 9.4.14.v20181114 fixed in 12.0.12 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-47162 | MEDIUM4.49 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-7264 | MEDIUM4.48 | curl 7.29.0-51.el7 No fix yet | 17.3% High Exploitation Risk | Post-Exploit |
| CVE-2016-4492 | MEDIUM4.4 | libgcc 4.8.5-36.el7 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2016-4492 | MEDIUM4.4 | libstdc++ 4.8.5-36.el7 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2016-0755 | MEDIUM4.38 | curl 7.29.0-51.el7 No fix yet | 9.3% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3796 | MEDIUM4.38 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2019-2745 | MEDIUM4.33 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.222.b10-0.el7_6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-2745 | MEDIUM4.33 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.222.b10-0.el7_6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-2745 | MEDIUM4.33 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.222.b10-0.el7_6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-26116 | MEDIUM4.32 | python 2.7.5-76.el7 fixed in 2.7.5-92.el7_9 | 6.4% Low-Moderate Risk | Post-Exploit |
| CVE-2020-14781 | MEDIUM4.3 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.272.b10-1.el7_9 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14782 | MEDIUM4.3 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.272.b10-1.el7_9 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14797 | MEDIUM4.3 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.272.b10-1.el7_9 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-2341 | MEDIUM4.3 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.302.b08-0.el7_9 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-2369 | MEDIUM4.3 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.302.b08-0.el7_9 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21248 | MEDIUM4.3 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21443 | MEDIUM4.3 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.332.b09-1.el7_9 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14779 | MEDIUM4.3 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.272.b10-1.el7_9 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14781 | MEDIUM4.3 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.272.b10-1.el7_9 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14782 | MEDIUM4.3 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.272.b10-1.el7_9 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14797 | MEDIUM4.3 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.272.b10-1.el7_9 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-2341 | MEDIUM4.3 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.302.b08-0.el7_9 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-2369 | MEDIUM4.3 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.302.b08-0.el7_9 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21248 | MEDIUM4.3 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21443 | MEDIUM4.3 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.332.b09-1.el7_9 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14779 | MEDIUM4.3 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.272.b10-1.el7_9 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14781 | MEDIUM4.3 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.272.b10-1.el7_9 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14782 | MEDIUM4.3 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.272.b10-1.el7_9 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14797 | MEDIUM4.3 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.272.b10-1.el7_9 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-2341 | MEDIUM4.3 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.302.b08-0.el7_9 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-2369 | MEDIUM4.3 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.302.b08-0.el7_9 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21248 | MEDIUM4.3 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.322.b06-1.el7_9 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21443 | MEDIUM4.3 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.332.b09-1.el7_9 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14779 | MEDIUM4.3 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.272.b10-1.el7_9 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-4166 | MEDIUM4.26 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2287 | MEDIUM4.26 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-5450 | MEDIUM4.25 | glibc 2.17-260.el7 fixed in 2.17-326.el7_9.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc 2.17-260.el7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-common 2.17-260.el7 fixed in 2.17-326.el7_9.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc-common 2.17-260.el7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-1122 | MEDIUM4.2 | procps-ng 3.3.10-23.el7 fixed in 3.3.10-26.el7 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-51296 | MEDIUM4.18 | sqlite 3.7.17-8.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-34982 | MEDIUM4.18 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-52859 | MEDIUM4.18 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | curl 7.29.0-51.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | curl 7.29.0-51.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | MEDIUM4.13 | python 2.7.5-76.el7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-2961 | MEDIUM4.12 | glibc 2.17-260.el7 fixed in 2.17-326.el7_9.3 | 88.3% Actively Exploited | Post-Exploit |
| CVE-2024-2961 | MEDIUM4.12 | glibc-common 2.17-260.el7 fixed in 2.17-326.el7_9.3 | 88.3% Actively Exploited | Post-Exploit |
| CVE-2022-23307 | MEDIUM4.12 | log4j:log4j 1.2.17 No fix yet | 52.5% Actively Exploited | Post-Exploit |
| CVE-2022-23302 | MEDIUM4.12 | log4j:log4j 1.2.17 No fix yet | 61.8% Actively Exploited | Post-Exploit |
| CVE-2025-0938 | MEDIUM4.08 | python 2.7.5-76.el7 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-21140 | MEDIUM4.08 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.422.b05-1.el7_9 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-21145 | MEDIUM4.08 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.422.b05-1.el7_9 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-21235 | MEDIUM4.08 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.432.b06-1.el7_9 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-30691 | MEDIUM4.08 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.452.b09-1.el7_9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-30754 | MEDIUM4.08 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.462.b08-1.el7_9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-53066 | MEDIUM4.08 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.472.b08-1.el7_9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-21925 | MEDIUM4.08 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.482.b08-1.el7_9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-21140 | MEDIUM4.08 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.422.b05-1.el7_9 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-21145 | MEDIUM4.08 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.422.b05-1.el7_9 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-21235 | MEDIUM4.08 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.432.b06-1.el7_9 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-30691 | MEDIUM4.08 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.452.b09-1.el7_9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-30754 | MEDIUM4.08 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.462.b08-1.el7_9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-53066 | MEDIUM4.08 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.472.b08-1.el7_9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-21925 | MEDIUM4.08 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.482.b08-1.el7_9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-21140 | MEDIUM4.08 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.422.b05-1.el7_9 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-21145 | MEDIUM4.08 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.422.b05-1.el7_9 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-21235 | MEDIUM4.08 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.432.b06-1.el7_9 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-30691 | MEDIUM4.08 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.452.b09-1.el7_9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-30754 | MEDIUM4.08 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.462.b08-1.el7_9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-53066 | MEDIUM4.08 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.472.b08-1.el7_9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-21925 | MEDIUM4.08 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.482.b08-1.el7_9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-23336 | MEDIUM4.07 | python 2.7.5-76.el7 No fix yet | 35.7% High Exploitation Risk | Post-Exploit |
| CVE-2017-8817 | MEDIUM4.06 | curl 7.29.0-51.el7 No fix yet | 11.2% High Exploitation Risk | Post-Exploit |
| CVE-2019-5482 | MEDIUM4.06 | curl 7.29.0-51.el7 fixed in 7.29.0-59.el7 | 17.9% High Exploitation Risk | Post-Exploit |
| CVE-2018-14618 | MEDIUM4.06 | curl 7.29.0-51.el7 fixed in 7.29.0-51.el7_6.3 | 11.1% High Exploitation Risk | Post-Exploit |
| CVE-2021-43527 | MEDIUM4.06 | nss 3.36.0-7.el7_5 fixed in 3.67.0-4.el7_9 | 17.6% High Exploitation Risk | Post-Exploit |
| CVE-2021-43527 | MEDIUM4.06 | nss-sysinit 3.36.0-7.el7_5 fixed in 3.67.0-4.el7_9 | 17.6% High Exploitation Risk | Post-Exploit |
| CVE-2021-3177 | MEDIUM4.06 | python 2.7.5-76.el7 fixed in 2.7.5-92.el7_9 | 18.9% High Exploitation Risk | Post-Exploit |
| CVE-2019-8457 | MEDIUM4.06 | sqlite 3.7.17-8.el7 No fix yet | 45.4% High Exploitation Risk | Post-Exploit |
| CVE-2022-37434 | MEDIUM4.06 | zlib 1.2.7-18.el7 fixed in 1.2.7-21.el7_9 | 15.5% High Exploitation Risk | Post-Exploit |
| CVE-2024-20945 | MEDIUM4 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.402.b06-1.el7_9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-20945 | MEDIUM4 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.402.b06-1.el7_9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-20945 | MEDIUM4 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.402.b06-1.el7_9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-0495 | MEDIUM4 | nspr 4.19.0-1.el7_5 fixed in 4.21.0-1.el7 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-12400 | MEDIUM4 | nspr 4.19.0-1.el7_5 fixed in 4.25.0-2.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-12401 | MEDIUM4 | nspr 4.19.0-1.el7_5 fixed in 4.25.0-2.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-0495 | MEDIUM4 | nss 3.36.0-7.el7_5 fixed in 3.44.0-4.el7 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-12400 | MEDIUM4 | nss 3.36.0-7.el7_5 fixed in 3.53.1-3.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-12401 | MEDIUM4 | nss 3.36.0-7.el7_5 fixed in 3.53.1-3.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-0495 | MEDIUM4 | nss-softokn 3.36.0-5.el7_5 fixed in 3.44.0-5.el7 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-12400 | MEDIUM4 | nss-softokn 3.36.0-5.el7_5 fixed in 3.53.1-6.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-12401 | MEDIUM4 | nss-softokn 3.36.0-5.el7_5 fixed in 3.53.1-6.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-0495 | MEDIUM4 | nss-softokn-freebl 3.36.0-5.el7_5 fixed in 3.44.0-5.el7 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-12400 | MEDIUM4 | nss-softokn-freebl 3.36.0-5.el7_5 fixed in 3.53.1-6.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-12401 | MEDIUM4 | nss-softokn-freebl 3.36.0-5.el7_5 fixed in 3.53.1-6.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-0495 | MEDIUM4 | nss-sysinit 3.36.0-7.el7_5 fixed in 3.44.0-4.el7 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-12400 | MEDIUM4 | nss-sysinit 3.36.0-7.el7_5 fixed in 3.53.1-3.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-12401 | MEDIUM4 | nss-sysinit 3.36.0-7.el7_5 fixed in 3.53.1-3.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-0495 | MEDIUM4 | nss-util 3.36.0-1.el7_5 fixed in 3.44.0-3.el7 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-12400 | MEDIUM4 | nss-util 3.36.0-1.el7_5 fixed in 3.53.1-1.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-12401 | MEDIUM4 | nss-util 3.36.0-1.el7_5 fixed in 3.53.1-1.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | glibc 2.17-260.el7 fixed in 2.17-326.el7_9.3 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | glibc-common 2.17-260.el7 fixed in 2.17-326.el7_9.3 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2012-6711 | LOW3.98 | bash 4.2.46-31.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2019-9924 | LOW3.98 | bash 4.2.46-31.el7 fixed in 4.2.46-34.el7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2018-1000876 | LOW3.98 | binutils 2.27-34.base.el7 fixed in 2.27-41.base.el7 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2021-37322 | LOW3.98 | binutils 2.27-34.base.el7 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2023-1579 | LOW3.98 | binutils 2.27-34.base.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils 2.27-34.base.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils 2.27-34.base.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils 2.27-34.base.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils 2.27-34.base.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils 2.27-34.base.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-44840 | LOW3.98 | binutils 2.27-34.base.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2015-4041 | LOW3.98 | coreutils 8.22-23.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2018-20483 | LOW3.98 | curl 7.29.0-51.el7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-9287 | LOW3.98 | python 2.7.5-76.el7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2017-7500 | LOW3.98 | rpm 4.11.3-35.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2017-7501 | LOW3.98 | rpm 4.11.3-35.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2014-9114 | LOW3.98 | util-linux 2.23.2-59.el7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2016-2779 | LOW3.98 | util-linux 2.23.2-59.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-57456 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-28421 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 fixed in 2:7.4.629-8.el7_9.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-39881 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-55693 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57455 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-59856 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59858 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-3903 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-0351 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-2571 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2580 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2581 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2816 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2817 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2819 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-2845 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2849 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2862 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2022-2889 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2946 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3037 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3234 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3235 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3256 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3296 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3352 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3591 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-4292 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-0049 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-0051 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-0054 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-0288 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-0433 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-0512 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-1127 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-2610 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-5535 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-22667 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1215 | LOW3.98 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2015-8538 | LOW3.9 | binutils 2.27-34.base.el7 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2017-12967 | LOW3.9 | binutils 2.27-34.base.el7 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2018-17794 | LOW3.9 | binutils 2.27-34.base.el7 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-17450 | LOW3.9 | binutils 2.27-34.base.el7 No fix yet | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-17451 | LOW3.9 | binutils 2.27-34.base.el7 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3826 | LOW3.9 | binutils 2.27-34.base.el7 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2016-2037 | LOW3.9 | cpio 2.11-27.el7 No fix yet | 5.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27776 | LOW3.9 | curl 7.29.0-51.el7 No fix yet | 3.7% Low-Moderate Risk | Post-Exploit |
| CVE-2017-1000100 | LOW3.9 | curl 7.29.0-51.el7 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-34903 | LOW3.9 | gnupg2 2.0.22-5.el7_5 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2025-47268 | LOW3.9 | iputils 20160308-10.el7 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2020-26137 | LOW3.9 | python 2.7.5-76.el7 fixed in 2.7.5-92.el7_9 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2020-8492 | LOW3.9 | python 2.7.5-76.el7 No fix yet | 6.7% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3733 | LOW3.9 | python 2.7.5-76.el7 No fix yet | 4.7% Low-Moderate Risk | Post-Exploit |
| CVE-2019-13751 | LOW3.9 | sqlite 3.7.17-8.el7 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2019-13752 | LOW3.9 | sqlite 3.7.17-8.el7 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2019-13753 | LOW3.9 | sqlite 3.7.17-8.el7 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-51297 | LOW3.88 | sqlite 3.7.17-8.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-51302 | LOW3.88 | sqlite 3.7.17-8.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-51303 | LOW3.88 | sqlite 3.7.17-8.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-51304 | LOW3.88 | sqlite 3.7.17-8.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils 2.27-34.base.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils 2.27-34.base.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils 2.27-34.base.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils 2.27-34.base.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-11586 | LOW3.82 | curl 7.29.0-51.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | curl 7.29.0-51.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | curl 7.29.0-51.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9079 | LOW3.82 | curl 7.29.0-51.el7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | curl 7.29.0-51.el7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | curl 7.29.0-51.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-15308 | LOW3.82 | python 2.7.5-76.el7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3644 | LOW3.82 | python 2.7.5-76.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW3.82 | python 2.7.5-76.el7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW3.82 | python 2.7.5-76.el7 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-51298 | LOW3.82 | sqlite 3.7.17-8.el7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-29087 | LOW3.82 | sqlite 3.7.17-8.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2020-35525 | LOW3.82 | sqlite 3.7.17-8.el7 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-59871 | LOW3.82 | tar 2:1.26-35.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-26269 | LOW3.82 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2019-9948 | LOW3.77 | python 2.7.5-76.el7 fixed in 2.7.5-86.el7 | 12.3% High Exploitation Risk | Post-Exploit |
| CVE-2020-12402 | LOW3.74 | nspr 4.19.0-1.el7_5 fixed in 4.25.0-2.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-12402 | LOW3.74 | nss 3.36.0-7.el7_5 fixed in 3.53.1-3.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-12402 | LOW3.74 | nss-softokn 3.36.0-5.el7_5 fixed in 3.53.1-6.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-12402 | LOW3.74 | nss-softokn-freebl 3.36.0-5.el7_5 fixed in 3.53.1-6.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-12402 | LOW3.74 | nss-sysinit 3.36.0-7.el7_5 fixed in 3.53.1-3.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-12402 | LOW3.74 | nss-util 3.36.0-1.el7_5 fixed in 3.53.1-1.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2019-14866 | LOW3.72 | cpio 2.11-27.el7 fixed in 2.11-28.el7 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-33412 | LOW3.72 | vim-minimal 2:7.4.160-5.el7 fixed in 2:7.4.629-8.el7_9.1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-25749 | LOW3.72 | vim-minimal 2:7.4.160-5.el7 fixed in 2:7.4.629-8.el7_9.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41411 | LOW3.72 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2019-2842 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.222.b10-0.el7_6 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2978 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14578 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.262.b10-0.el7_8 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14579 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.262.b10-0.el7_8 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2590 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.242.b08-0.el7_7 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2654 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.242.b08-0.el7_7 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2773 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.252.b09-2.el7_8 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-22049 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.382.b05-1.el7_9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-21011 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.412.b08-1.el7_9 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-21068 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.412.b08-1.el7_9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-21085 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.412.b08-1.el7_9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-21131 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.422.b05-1.el7_9 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-21138 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.422.b05-1.el7_9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-21144 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.422.b05-1.el7_9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-21208 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.432.b06-1.el7_9 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-21217 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.432.b06-1.el7_9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2962 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2964 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2973 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2981 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2983 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2987 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2988 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2992 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14577 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.262.b10-0.el7_8 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2583 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.242.b08-0.el7_7 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2659 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.242.b08-0.el7_7 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2754 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.252.b09-2.el7_8 | 4.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2755 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.252.b09-2.el7_8 | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2756 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.252.b09-2.el7_8 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2757 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.252.b09-2.el7_8 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35603 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 4.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21619 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.352.b08-2.el7_9 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21624 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.352.b08-2.el7_9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-21843 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.362.b08-1.el7_9 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-21937 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.372.b07-1.el7_9 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-21938 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.372.b07-1.el7_9 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-21968 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.372.b07-1.el7_9 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-22045 | LOW3.7 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.382.b05-1.el7_9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2842 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.222.b10-0.el7_6 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2978 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14578 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.262.b10-0.el7_8 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14579 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.262.b10-0.el7_8 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2590 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.242.b08-0.el7_7 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2654 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.242.b08-0.el7_7 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2773 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.252.b09-2.el7_8 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-22049 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.382.b05-1.el7_9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-21011 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.412.b08-1.el7_9 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-21068 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.412.b08-1.el7_9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-21085 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.412.b08-1.el7_9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-21131 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.422.b05-1.el7_9 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-21138 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.422.b05-1.el7_9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-21144 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.422.b05-1.el7_9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-21208 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.432.b06-1.el7_9 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-21217 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.432.b06-1.el7_9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2962 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2964 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2973 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2981 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2983 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2987 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2988 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2992 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14577 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.262.b10-0.el7_8 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2583 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.242.b08-0.el7_7 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2659 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.242.b08-0.el7_7 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2754 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.252.b09-2.el7_8 | 4.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2755 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.252.b09-2.el7_8 | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2756 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.252.b09-2.el7_8 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2757 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.252.b09-2.el7_8 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35603 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 4.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21619 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.352.b08-2.el7_9 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21624 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.352.b08-2.el7_9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-21843 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.362.b08-1.el7_9 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-21937 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.372.b07-1.el7_9 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-21938 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.372.b07-1.el7_9 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-21968 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.372.b07-1.el7_9 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-22045 | LOW3.7 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.382.b05-1.el7_9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2842 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.222.b10-0.el7_6 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2978 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14578 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.262.b10-0.el7_8 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14579 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.262.b10-0.el7_8 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2590 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.242.b08-0.el7_7 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2654 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.242.b08-0.el7_7 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2773 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.252.b09-2.el7_8 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-22049 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.382.b05-1.el7_9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-21011 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.412.b08-1.el7_9 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-21068 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.412.b08-1.el7_9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-21085 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.412.b08-1.el7_9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-21131 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.422.b05-1.el7_9 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-21138 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.422.b05-1.el7_9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-21144 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.422.b05-1.el7_9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-21208 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.432.b06-1.el7_9 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-21217 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.432.b06-1.el7_9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2962 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2964 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2973 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2981 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2983 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2987 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2988 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2992 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14577 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.262.b10-0.el7_8 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2583 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.242.b08-0.el7_7 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2659 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.242.b08-0.el7_7 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2754 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.252.b09-2.el7_8 | 4.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2755 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.252.b09-2.el7_8 | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2756 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.252.b09-2.el7_8 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-2757 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.252.b09-2.el7_8 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35603 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 4.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21619 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.352.b08-2.el7_9 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-21624 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.352.b08-2.el7_9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-21843 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.362.b08-1.el7_9 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-21937 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.372.b07-1.el7_9 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-21938 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.372.b07-1.el7_9 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-21968 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.372.b07-1.el7_9 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-22045 | LOW3.7 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.382.b05-1.el7_9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1563 | LOW3.7 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2020-1968 | LOW3.7 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2025-48924 | LOW3.7 | org.apache.commons:commons-lang3 3.8.1 fixed in 3.18.0 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-35494 | LOW3.66 | binutils 2.27-34.base.el7 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-16935 | LOW3.66 | python 2.7.5-76.el7 fixed in 2.7.5-89.el7 | 4.7% Low-Moderate Risk | Post-Exploit |
| CVE-2019-18348 | LOW3.66 | python 2.7.5-76.el7 No fix yet | 3.5% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9740 | LOW3.66 | python 2.7.5-76.el7 fixed in 2.7.5-86.el7 | 5.5% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9947 | LOW3.66 | python 2.7.5-76.el7 fixed in 2.7.5-86.el7 | 5.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-6135 | LOW3.65 | nss 3.36.0-7.el7_5 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-6135 | LOW3.65 | nss-sysinit 3.36.0-7.el7_5 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-54369 | LOW3.62 | acl 2.2.51-14.el7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-25584 | LOW3.62 | binutils 2.27-34.base.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-4156 | LOW3.62 | gawk 4.0.2-4.el7_3.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4786 | LOW3.62 | python 2.7.5-76.el7 fixed in 2.7.5-94.el7_9.5 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW3.62 | python 2.7.5-76.el7 fixed in 2.7.5-94.el7_9.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW3.62 | python 2.7.5-76.el7 fixed in 2.7.5-94.el7_9.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-35177 | LOW3.62 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-6965 | LOW3.61 | sqlite 3.7.17-8.el7 fixed in 3.7.17-9.el7_9.1 | 74.4% Actively Exploited | Post-Exploit |
| CVE-2005-2541 | LOW3.6 | tar 2:1.26-35.el7 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2016-8617 | LOW3.57 | curl 7.29.0-51.el7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gnupg2 2.0.22-5.el7_5 fixed in 2.0.22-5.el7_9.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-20271 | LOW3.57 | rpm 4.11.3-35.el7 fixed in 4.11.3-48.el7_9 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-44604 | LOW3.57 | rpm 4.11.3-35.el7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-46483 | LOW3.57 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-8058 | LOW3.57 | glibc 2.17-260.el7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | glibc-common 2.17-260.el7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-12735 | LOW3.56 | vim-minimal 2:7.4.160-5.el7 fixed in 2:7.4.160-6.el7_6 | 19.1% High Exploitation Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils 2.27-34.base.el7 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22947 | LOW3.54 | curl 7.29.0-51.el7 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-32208 | LOW3.54 | curl 7.29.0-51.el7 No fix yet | 6.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27535 | LOW3.54 | curl 7.29.0-51.el7 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27536 | LOW3.54 | curl 7.29.0-51.el7 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28321 | LOW3.54 | curl 7.29.0-51.el7 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2016-8616 | LOW3.54 | curl 7.29.0-51.el7 No fix yet | 3.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-43552 | LOW3.54 | curl 7.29.0-51.el7 fixed in 7.29.0-59.el7_9.2 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-11053 | LOW3.54 | curl 7.29.0-51.el7 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2015-0837 | LOW3.54 | gnupg2 2.0.22-5.el7_5 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-1121 | LOW3.54 | procps-ng 3.3.10-23.el7 No fix yet | 4.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-48566 | LOW3.54 | python 2.7.5-76.el7 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2014-9939 | LOW3.53 | binutils 2.27-34.base.el7 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2014-5044 | LOW3.53 | libgcc 4.8.5-36.el7 No fix yet | 5.7% Low-Moderate Risk | Post-Exploit |
| CVE-2014-5044 | LOW3.53 | libstdc++ 4.8.5-36.el7 No fix yet | 5.7% Low-Moderate Risk | Post-Exploit |
| CVE-2025-13034 | LOW3.47 | curl 7.29.0-51.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | curl 7.29.0-51.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-6923 | LOW3.47 | python 2.7.5-76.el7 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2014-5461 | LOW3.45 | lua 5.1.4-15.el7 No fix yet | 11.6% High Exploitation Risk | Post-Exploit |
| CVE-2021-35938 | LOW3.42 | rpm 4.11.3-35.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2021-35939 | LOW3.42 | rpm 4.11.3-35.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2020-21583 | LOW3.42 | util-linux 2.23.2-59.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-27774 | LOW3.42 | curl 7.29.0-51.el7 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-33602 | LOW3.4 | glibc 2.17-260.el7 fixed in 2.17-326.el7_9.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | glibc 2.17-260.el7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | glibc-common 2.17-260.el7 fixed in 2.17-326.el7_9.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | glibc-common 2.17-260.el7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW3.4 | openssl-libs 1:1.0.2k-16.el7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-49128 | LOW3.4 | com.fasterxml.jackson.core:jackson-core 2.9.8 fixed in 2.13.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2019-2786 | LOW3.4 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.222.b10-0.el7_6 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2786 | LOW3.4 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.222.b10-0.el7_6 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2786 | LOW3.4 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.222.b10-0.el7_6 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28419 | LOW3.37 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-1170 | LOW3.37 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-1175 | LOW3.37 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils 2.27-34.base.el7 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2016-2781 | LOW3.31 | coreutils 8.22-23.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | curl 7.29.0-51.el7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | curl 7.29.0-51.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | curl 7.29.0-51.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | curl 7.29.0-51.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl 7.29.0-51.el7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | curl 7.29.0-51.el7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW3.31 | python 2.7.5-76.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-33056 | LOW3.31 | tar 2:1.26-35.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2017-6965 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2017-6966 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9074 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2020-16592 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2016-4487 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2016-4488 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2016-4489 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2016-4490 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2016-4491 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2016-4493 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13757 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2017-14128 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2017-14129 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2017-14130 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2017-14529 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2017-14930 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2017-14932 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-14933 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-14934 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2017-14938 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2017-14939 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 5.9% Low-Moderate Risk | Post-Exploit |
| CVE-2017-14940 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2017-15021 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2017-15022 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2017-15023 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2017-15024 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2017-15025 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2017-15225 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2017-15939 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2017-17080 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-17123 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2017-7209 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2017-7210 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2017-7224 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2017-7299 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2017-9038 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2017-9039 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2017-9040 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2017-9041 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2017-9044 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2017-9954 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2017-9955 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2018-12641 | LOW3.3 | binutils 2.27-34.base.el7 fixed in 2.27-41.base.el7 | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2018-17360 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2018-17985 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2018-18484 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2018-18605 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2018-18606 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2018-18607 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2018-18700 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2018-18701 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2018-19932 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20002 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6759 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6872 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010204 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-12972 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-14250 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2020-16593 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2020-16599 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2020-35493 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2020-35495 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2020-35496 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2020-35507 | LOW3.3 | binutils 2.27-34.base.el7 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27538 | LOW3.3 | curl 7.29.0-51.el7 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2015-1606 | LOW3.3 | gnupg2 2.0.22-5.el7_5 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2015-1607 | LOW3.3 | gnupg2 2.0.22-5.el7_5 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2021-43519 | LOW3.3 | lua 5.1.4-15.el7 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-44605 | LOW3.3 | rpm 4.11.3-35.el7 No fix yet | — | Post-Exploit |
| CVE-2017-13685 | LOW3.3 | sqlite 3.7.17-8.el7 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-48303 | LOW3.3 | tar 2:1.26-35.el7 No fix yet | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2021-4193 | LOW3.3 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2208 | LOW3.3 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2231 | LOW3.3 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2598 | LOW3.3 | vim-minimal 2:7.4.160-5.el7 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-35937 | LOW3.26 | rpm 4.11.3-35.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54370 | LOW3.21 | acl 2.2.51-14.el7 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-20197 | LOW3.21 | binutils 2.27-34.base.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5958 | LOW3.21 | sed 4.2.2-5.el7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-22876 | LOW3.18 | curl 7.29.0-51.el7 No fix yet | 5.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27779 | LOW3.18 | curl 7.29.0-51.el7 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2025-9086 | LOW3.18 | curl 7.29.0-51.el7 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22925 | LOW3.18 | curl 7.29.0-51.el7 No fix yet | 4.9% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20852 | LOW3.18 | python 2.7.5-76.el7 fixed in 2.7.5-88.el7 | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2021-4189 | LOW3.18 | python 2.7.5-76.el7 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27043 | LOW3.18 | python 2.7.5-76.el7 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-8088 | LOW3.18 | python 2.7.5-76.el7 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19924 | LOW3.18 | sqlite 3.7.17-8.el7 No fix yet | 7.9% Low-Moderate Risk | Post-Exploit |
| CVE-2024-0450 | LOW3.16 | python 2.7.5-76.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-21094 | LOW3.15 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.412.b08-1.el7_9 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-21210 | LOW3.15 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.432.b06-1.el7_9 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22018 | LOW3.15 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.492.b09-1.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47010 | LOW3.15 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.502.b07-1.1.el7_9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-47059 | LOW3.15 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.502.b07-1.1.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-21094 | LOW3.15 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.412.b08-1.el7_9 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-21210 | LOW3.15 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.432.b06-1.el7_9 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22018 | LOW3.15 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.492.b09-1.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47010 | LOW3.15 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.502.b07-1.1.el7_9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-47059 | LOW3.15 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.502.b07-1.1.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-21094 | LOW3.15 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.412.b08-1.el7_9 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-21210 | LOW3.15 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.432.b06-1.el7_9 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22018 | LOW3.15 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.492.b09-1.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47010 | LOW3.15 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.502.b07-1.1.el7_9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-47059 | LOW3.15 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.502.b07-1.1.el7_9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.11 | binutils 2.27-34.base.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56391 | LOW3.11 | coreutils 8.22-23.el7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.11 | python 2.7.5-76.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.23.2-59.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2019-2945 | LOW3.1 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35588 | LOW3.1 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2945 | LOW3.1 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35588 | LOW3.1 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-2945 | LOW3.1 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.232.b09-0.el7_7 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35588 | LOW3.1 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.312.b07-1.el7_9 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36479 | LOW3.1 | org.eclipse.jetty:jetty-servlets 9.4.14.v20181114 fixed in 9.4.52, 10.0.16, 11.0.16 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5713 | LOW3.06 | python 2.7.5-76.el7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2016-6153 | LOW3.01 | sqlite 3.7.17-8.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2015-3153 | LOW3 | curl 7.29.0-51.el7 No fix yet | 7.5% Low-Moderate Risk | Post-Exploit |
| CVE-2014-4617 | LOW3 | gnupg2 2.0.22-5.el7_5 No fix yet | 3.3% Low-Moderate Risk | Post-Exploit |
| CVE-2013-1664 | LOW3 | python 2.7.5-76.el7 No fix yet | 4.9% Low-Moderate Risk | Post-Exploit |
| CVE-2013-1665 | LOW3 | python 2.7.5-76.el7 No fix yet | 4.6% Low-Moderate Risk | Post-Exploit |
| CVE-2021-34428 | LOW2.98 | org.eclipse.jetty:jetty-server 9.4.14.v20181114 fixed in 9.4.41, 10.0.3, 11.0.3 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2021-20266 | LOW2.94 | rpm 4.11.3-35.el7 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | curl 7.29.0-51.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-15003 | LOW2.86 | binutils 2.27-34.base.el7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-45582 | LOW2.86 | tar 2:1.26-35.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2020-16590 | LOW2.8 | binutils 2.27-34.base.el7 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-4285 | LOW2.8 | binutils 2.27-34.base.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils 2.27-34.base.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils 2.27-34.base.el7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-14974 | LOW2.8 | binutils 2.27-34.base.el7 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2017-8421 | LOW2.8 | binutils 2.27-34.base.el7 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2020-16591 | LOW2.8 | binutils 2.27-34.base.el7 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-38533 | LOW2.8 | binutils 2.27-34.base.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-47007 | LOW2.8 | binutils 2.27-34.base.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47008 | LOW2.8 | binutils 2.27-34.base.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47010 | LOW2.8 | binutils 2.27-34.base.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47011 | LOW2.8 | binutils 2.27-34.base.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-25585 | LOW2.8 | binutils 2.27-34.base.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-25588 | LOW2.8 | binutils 2.27-34.base.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils 2.27-34.base.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils 2.27-34.base.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils 2.27-34.base.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils 2.27-34.base.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils 2.27-34.base.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils 2.27-34.base.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils 2.27-34.base.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils 2.27-34.base.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils 2.27-34.base.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-7207 | LOW2.8 | cpio 2.11-27.el7 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-24883 | LOW2.8 | gnupg2 2.0.22-5.el7_5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-13837 | LOW2.8 | python 2.7.5-76.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42308 | LOW2.8 | python 2.7.5-76.el7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-6075 | LOW2.8 | python 2.7.5-76.el7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-3421 | LOW2.8 | rpm 4.11.3-35.el7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-4641 | LOW2.8 | shadow-utils 2:4.1.5.1-25.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2019-19645 | LOW2.8 | sqlite 3.7.17-8.el7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2020-13435 | LOW2.8 | sqlite 3.7.17-8.el7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2020-13631 | LOW2.8 | sqlite 3.7.17-8.el7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2020-24736 | LOW2.8 | sqlite 3.7.17-8.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-29088 | LOW2.8 | sqlite 3.7.17-8.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-0232 | LOW2.8 | sqlite 3.7.17-8.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53655 | LOW2.8 | tar 2:1.26-35.el7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 2:1.26-35.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.23.2-59.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-37600 | LOW2.8 | util-linux 2.23.2-59.el7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-43790 | LOW2.8 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-9390 | LOW2.8 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-28418 | LOW2.8 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45130 | LOW2.8 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55892 | LOW2.8 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-59857 | LOW2.8 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-1000382 | LOW2.8 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2017-17087 | LOW2.8 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-3236 | LOW2.8 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-2874 | LOW2.8 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2923 | LOW2.8 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2980 | LOW2.8 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2022-3153 | LOW2.8 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-1264 | LOW2.8 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-2609 | LOW2.8 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-46246 | LOW2.8 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-5441 | LOW2.8 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-45306 | LOW2.8 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-22134 | LOW2.8 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-24014 | LOW2.8 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2019-19126 | LOW2.8 | glibc 2.17-260.el7 fixed in 2.17-317.el7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-19126 | LOW2.8 | glibc-common 2.17-260.el7 fixed in 2.17-317.el7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-8908 | LOW2.8 | com.google.guava:guava 11.0.2 fixed in 32.0.0-android | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2020-8908 | LOW2.8 | com.google.guava:guava 20.0 fixed in 32.0.0-android | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-7216 | LOW2.7 | cpio 2.11-27.el7 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | curl 7.29.0-51.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | curl 7.29.0-51.el7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | curl 7.29.0-51.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-48964 | LOW2.7 | iputils 20160308-10.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-40217 | LOW2.7 | python 2.7.5-76.el7 fixed in 2.7.5-94.el7_9 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-12084 | LOW2.7 | python 2.7.5-76.el7 fixed in 2.7.5-94.el7_9.2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW2.7 | python 2.7.5-76.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW2.7 | python 2.7.5-76.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4360 | LOW2.7 | python 2.7.5-76.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59875 | LOW2.7 | tar 2:1.26-35.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux 2.23.2-59.el7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-20807 | LOW2.7 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-44656 | LOW2.7 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-34743 | LOW2.7 | xz 5.2.2-1.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-2047 | LOW2.7 | org.eclipse.jetty:jetty-http 9.4.14.v20181114 fixed in 9.4.47, 10.0.10, 11.0.10 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2016-4492 | LOW2.64 | binutils 2.27-34.base.el7 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2025-4516 | LOW2.6 | python 2.7.5-76.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-2163 | LOW2.6 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.292.b10-1.el7_9 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14796 | LOW2.6 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.272.b10-1.el7_9 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-2163 | LOW2.6 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.292.b10-1.el7_9 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14796 | LOW2.6 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.272.b10-1.el7_9 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-2163 | LOW2.6 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.292.b10-1.el7_9 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14796 | LOW2.6 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.272.b10-1.el7_9 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-30115 | LOW2.58 | curl 7.29.0-51.el7 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2013-7040 | LOW2.58 | python 2.7.5-76.el7 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2021-45346 | LOW2.58 | sqlite 3.7.17-8.el7 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils 2.27-34.base.el7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | binutils 2.27-34.base.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-0397 | LOW2.55 | python 2.7.5-76.el7 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2019-11360 | LOW2.52 | iptables 1.4.21-28.el7 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-22007 | LOW2.46 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.492.b09-1.el7_9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34268 | LOW2.46 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.492.b09-1.el7_9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22007 | LOW2.46 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.492.b09-1.el7_9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34268 | LOW2.46 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.492.b09-1.el7_9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22007 | LOW2.46 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.492.b09-1.el7_9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34268 | LOW2.46 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 fixed in 1:1.8.0.492.b09-1.el7_9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14017 | LOW2.45 | curl 7.29.0-51.el7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | LOW2.45 | python 2.7.5-76.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.45 | python 2.7.5-76.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 8.22-23.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl 7.29.0-51.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gnupg2 2.0.22-5.el7_5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gnupg2 2.0.22-5.el7_5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.5-10.el7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-3521 | LOW2.4 | rpm 4.11.3-35.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-64118 | LOW2.4 | tar 2:1.26-35.el7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-20482 | LOW2.4 | tar 2:1.26-35.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57452 | LOW2.4 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-48706 | LOW2.4 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-43374 | LOW2.4 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-47814 | LOW2.4 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11468 | LOW2.29 | python 2.7.5-76.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0865 | LOW2.29 | python 2.7.5-76.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW2.29 | python 2.7.5-76.el7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-43802 | LOW2.29 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils 8.22-23.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW2.24 | coreutils 8.22-23.el7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-20795 | LOW2.24 | iproute 4.11.0-14.el7_6.2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-29768 | LOW2.24 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-28420 | LOW2.24 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42307 | LOW2.24 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2020-8284 | LOW2.22 | curl 7.29.0-51.el7 No fix yet | 3.9% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22924 | LOW2.22 | curl 7.29.0-51.el7 No fix yet | 6.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-35252 | LOW2.22 | curl 7.29.0-51.el7 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28322 | LOW2.22 | curl 7.29.0-51.el7 No fix yet | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-38546 | LOW2.22 | curl 7.29.0-51.el7 No fix yet | 6.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4032 | LOW2.22 | python 2.7.5-76.el7 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-6069 | LOW2.19 | python 2.7.5-76.el7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8291 | LOW2.19 | python 2.7.5-76.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-48231 | LOW2.19 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48232 | LOW2.19 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48233 | LOW2.19 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48234 | LOW2.19 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48235 | LOW2.19 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48236 | LOW2.19 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48237 | LOW2.19 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2018-1000030 | LOW2.16 | python 2.7.5-76.el7 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2014-3591 | LOW2.14 | gnupg2 2.0.22-5.el7_5 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-41965 | LOW2.14 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-26603 | LOW2.14 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-53905 | LOW2.09 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-53906 | LOW2.09 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2020-35448 | LOW1.98 | binutils 2.27-34.base.el7 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2021-20193 | LOW1.98 | tar 2:1.26-35.el7 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils 2.27-34.base.el7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2021-22898 | LOW1.86 | curl 7.29.0-51.el7 No fix yet | 4.4% Low-Moderate Risk | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | shadow-utils 2:4.1.5.1-25.el7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils 2.27-34.base.el7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils 2.27-34.base.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils 2.27-34.base.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils 2.27-34.base.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils 2.27-34.base.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils 2.27-34.base.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.27-34.base.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gnupg2 2.0.22-5.el7_5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-4016 | LOW1.68 | procps-ng 3.3.10-23.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4519 | LOW1.68 | python 2.7.5-76.el7 fixed in 2.7.5-94.el7_9.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW1.68 | python 2.7.5-76.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.68 | python 2.7.5-76.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python 2.7.5-76.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-70873 | LOW1.68 | sqlite 3.7.17-8.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-39804 | LOW1.68 | tar 2:1.26-35.el7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils 2.27-34.base.el7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils 2.27-34.base.el7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1795 | LOW1.58 | python 2.7.5-76.el7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gnupg2 2.0.22-5.el7_5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils 2.27-34.base.el7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils 2.27-34.base.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils 2.27-34.base.el7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-5642 | LOW1.38 | python 2.7.5-76.el7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2017-7407 | LOW1.22 | curl 7.29.0-51.el7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2015-1197 | LOW1.14 | cpio 2.11-27.el7 No fix yet | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28422 | LOW1.12 | vim-minimal 2:7.4.160-5.el7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2015-5218 | LOW1.07 | util-linux 2.23.2-59.el7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2019-12900 | NONE0 | bzip2-libs 1.0.6-13.el7 No fix yet | 8.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-37920 | NONE0 | ca-certificates 2018.2.22-70.0.el7_5 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-47175 | NONE0 | cups-libs 1:1.6.3-35.el7 No fix yet | 63.8% Actively Exploited | Not Applicable |
| CVE-2018-16402 | NONE0 | elfutils-default-yama-scope 0.172-2.el7 fixed in 0.176-2.el7 | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2018-16402 | NONE0 | elfutils-libelf 0.172-2.el7 fixed in 0.176-2.el7 | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2018-16402 | NONE0 | elfutils-libs 0.172-2.el7 fixed in 0.176-2.el7 | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2022-22822 | NONE0 | expat 2.1.0-10.el7_3 fixed in 2.1.0-14.el7_9 | 4.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-22823 | NONE0 | expat 2.1.0-10.el7_3 fixed in 2.1.0-14.el7_9 | 3.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-22824 | NONE0 | expat 2.1.0-10.el7_3 fixed in 2.1.0-14.el7_9 | 3.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-25235 | NONE0 | expat 2.1.0-10.el7_3 fixed in 2.1.0-14.el7_9 | 5.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-25236 | NONE0 | expat 2.1.0-10.el7_3 fixed in 2.1.0-14.el7_9 | 35.9% High Exploitation Risk | Not Applicable |
| CVE-2022-25315 | NONE0 | expat 2.1.0-10.el7_3 fixed in 2.1.0-14.el7_9 | 4.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-23852 | NONE0 | expat 2.1.0-10.el7_3 fixed in 2.1.0-14.el7_9 | 4.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-45491 | NONE0 | expat 2.1.0-10.el7_3 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-45492 | NONE0 | expat 2.1.0-10.el7_3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2016-9063 | NONE0 | expat 2.1.0-10.el7_3 No fix yet | 5.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-8105 | NONE0 | freetype 2.8-12.el7_6.1 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2017-8287 | NONE0 | freetype 2.8-12.el7_6.1 No fix yet | 3.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-27404 | NONE0 | freetype 2.8-12.el7_6.1 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2014-9746 | NONE0 | freetype 2.8-12.el7_6.1 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2015-8391 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 6.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-12450 | NONE0 | glib2 2.56.1-2.el7 fixed in 2.56.1-7.el7 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2025-14087 | NONE0 | glib2 2.56.1-2.el7 fixed in 2.56.1-12.el7_9 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2015-8386 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 7.1% Low-Moderate Risk | Not Applicable |
| CVE-2017-15088 | NONE0 | krb5-libs 1.15.1-34.el7 No fix yet | 8.4% Low-Moderate Risk | Not Applicable |
| CVE-2017-11462 | NONE0 | krb5-libs 1.15.1-34.el7 No fix yet | 5.5% Low-Moderate Risk | Not Applicable |
| CVE-2021-31535 | NONE0 | libX11 1.6.5-2.el7 fixed in 1.6.7-4.el7_9 | 10.6% High Exploitation Risk | Not Applicable |
| CVE-2016-7943 | NONE0 | libX11 1.6.5-2.el7 No fix yet | 4.3% Low-Moderate Risk | Not Applicable |
| CVE-2018-14599 | NONE0 | libX11 1.6.5-2.el7 fixed in 1.6.7-2.el7 | 4.8% Low-Moderate Risk | Not Applicable |
| CVE-2018-14600 | NONE0 | libX11 1.6.5-2.el7 fixed in 1.6.7-2.el7 | 9.3% Low-Moderate Risk | Not Applicable |
| CVE-2016-7942 | NONE0 | libX11 1.6.5-2.el7 No fix yet | 4.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-31535 | NONE0 | libX11-common 1.6.5-2.el7 fixed in 1.6.7-4.el7_9 | 10.6% High Exploitation Risk | Not Applicable |
| CVE-2016-7943 | NONE0 | libX11-common 1.6.5-2.el7 No fix yet | 4.3% Low-Moderate Risk | Not Applicable |
| CVE-2018-14599 | NONE0 | libX11-common 1.6.5-2.el7 fixed in 1.6.7-2.el7 | 4.8% Low-Moderate Risk | Not Applicable |
| CVE-2018-14600 | NONE0 | libX11-common 1.6.5-2.el7 fixed in 1.6.7-2.el7 | 9.3% Low-Moderate Risk | Not Applicable |
| CVE-2016-7942 | NONE0 | libX11-common 1.6.5-2.el7 No fix yet | 4.3% Low-Moderate Risk | Not Applicable |
| CVE-2016-7944 | NONE0 | libXfixes 5.0.3-1.el7 No fix yet | 3.4% Low-Moderate Risk | Not Applicable |
| CVE-2016-7947 | NONE0 | libXrandr 1.5.1-2.el7 No fix yet | 3.6% Low-Moderate Risk | Not Applicable |
| CVE-2016-7948 | NONE0 | libXrandr 1.5.1-2.el7 No fix yet | 3.6% Low-Moderate Risk | Not Applicable |
| CVE-2016-7949 | NONE0 | libXrender 0.9.10-1.el7 No fix yet | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2016-7950 | NONE0 | libXrender 0.9.10-1.el7 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2016-7951 | NONE0 | libXtst 1.2.3-1.el7 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2016-8618 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 4.6% Low-Moderate Risk | Not Applicable |
| CVE-2016-8619 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 5.0% Low-Moderate Risk | Not Applicable |
| CVE-2017-8817 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 11.2% High Exploitation Risk | Not Applicable |
| CVE-2019-5482 | NONE0 | libcurl 7.29.0-51.el7 fixed in 7.29.0-59.el7 | 17.9% High Exploitation Risk | Not Applicable |
| CVE-2016-8622 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 4.7% Low-Moderate Risk | Not Applicable |
| CVE-2018-14618 | NONE0 | libcurl 7.29.0-51.el7 fixed in 7.29.0-51.el7_6.3 | 11.1% High Exploitation Risk | Not Applicable |
| CVE-2017-14062 | NONE0 | libidn 1.28-4.el7 No fix yet | 3.9% Low-Moderate Risk | Not Applicable |
| CVE-2017-12652 | NONE0 | libpng 2:1.5.13-7.el7_2 fixed in 2:1.5.13-8.el7 | 4.1% Low-Moderate Risk | Not Applicable |
| CVE-2016-9538 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 3.4% Low-Moderate Risk | Not Applicable |
| CVE-2016-9539 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2017-5225 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 4.4% Low-Moderate Risk | Not Applicable |
| CVE-2017-9117 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-56171 | NONE0 | libxml2 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7_9.9 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2016-4658 | NONE0 | libxml2 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7_9.6 | 8.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-16931 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 4.3% Low-Moderate Risk | Not Applicable |
| CVE-2017-7375 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2024-56171 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7_9.9 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2016-4658 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7_9.6 | 8.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-16931 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 4.3% Low-Moderate Risk | Not Applicable |
| CVE-2017-7375 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2016-4607 | NONE0 | libxslt 1.1.28-5.el7 No fix yet | 5.1% Low-Moderate Risk | Not Applicable |
| CVE-2016-4608 | NONE0 | libxslt 1.1.28-5.el7 No fix yet | 5.1% Low-Moderate Risk | Not Applicable |
| CVE-2016-4609 | NONE0 | libxslt 1.1.28-5.el7 No fix yet | 5.1% Low-Moderate Risk | Not Applicable |
| CVE-2016-4610 | NONE0 | libxslt 1.1.28-5.el7 No fix yet | 5.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-11068 | NONE0 | libxslt 1.1.28-5.el7 fixed in 1.1.28-6.el7 | 5.1% Low-Moderate Risk | Not Applicable |
| CVE-2017-10684 | NONE0 | ncurses 5.9-14.20130511.el7_4 No fix yet | 4.9% Low-Moderate Risk | Not Applicable |
| CVE-2017-10685 | NONE0 | ncurses 5.9-14.20130511.el7_4 No fix yet | 4.3% Low-Moderate Risk | Not Applicable |
| CVE-2017-10684 | NONE0 | ncurses-base 5.9-14.20130511.el7_4 No fix yet | 4.9% Low-Moderate Risk | Not Applicable |
| CVE-2017-10685 | NONE0 | ncurses-base 5.9-14.20130511.el7_4 No fix yet | 4.3% Low-Moderate Risk | Not Applicable |
| CVE-2017-10684 | NONE0 | ncurses-libs 5.9-14.20130511.el7_4 No fix yet | 4.9% Low-Moderate Risk | Not Applicable |
| CVE-2017-10685 | NONE0 | ncurses-libs 5.9-14.20130511.el7_4 No fix yet | 4.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-43527 | NONE0 | nss-tools 3.36.0-7.el7_5 fixed in 3.67.0-4.el7_9 | 17.6% High Exploitation Risk | Not Applicable |
| CVE-2019-17006 | NONE0 | nss-tools 3.36.0-7.el7_5 fixed in 3.53.1-3.el7_9 | 3.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-29155 | NONE0 | openldap 2.4.44-20.el7 No fix yet | 64.5% Actively Exploited | Not Applicable |
| CVE-2019-1010238 | NONE0 | pango 1.42.4-2.el7_6 fixed in 1.42.4-4.el7_7 | 6.3% Low-Moderate Risk | Not Applicable |
| CVE-2019-10160 | NONE0 | python-libs 2.7.5-76.el7 fixed in 2.7.5-80.el7_6 | 5.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-9636 | NONE0 | python-libs 2.7.5-76.el7 fixed in 2.7.5-77.el7_6 | 9.1% Low-Moderate Risk | Not Applicable |
| CVE-2017-1000158 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 8.2% Low-Moderate Risk | Not Applicable |
| CVE-2020-27619 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 8.4% Low-Moderate Risk | Not Applicable |
| CVE-2021-3177 | NONE0 | python-libs 2.7.5-76.el7 fixed in 2.7.5-92.el7_9 | 18.9% High Exploitation Risk | Not Applicable |
| CVE-2022-48565 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 4.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-2526 | NONE0 | systemd 219-62.el7 fixed in 219-78.el7_9.7 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-2526 | NONE0 | systemd-libs 219-62.el7 fixed in 219-78.el7_9.7 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2020-15999 | NONE0 | freetype 2.8-12.el7_6.1 fixed in 2.8-14.el7_9.1 | 50.6% Actively Exploited | Not Applicable |
| CVE-2017-6519 | NONE0 | avahi-libs 0.6.31-19.el7 fixed in 0.6.31-20.el7 | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-58016 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2015-5073 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 7.7% Low-Moderate Risk | Not Applicable |
| CVE-2024-37371 | NONE0 | krb5-libs 1.15.1-34.el7 fixed in 1.15.1-55.el7_9.2 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2018-16842 | NONE0 | libcurl 7.29.0-51.el7 fixed in 7.29.0-54.el7 | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-7598 | NONE0 | libssh2 1.4.3-12.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-3858 | NONE0 | libssh2 1.4.3-12.el7 fixed in 1.8.0-3.el7 | 6.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-3859 | NONE0 | libssh2 1.4.3-12.el7 No fix yet | 6.3% Low-Moderate Risk | Not Applicable |
| CVE-2019-3860 | NONE0 | libssh2 1.4.3-12.el7 No fix yet | 5.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-3861 | NONE0 | libssh2 1.4.3-12.el7 fixed in 1.8.0-3.el7 | 5.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-3862 | NONE0 | libssh2 1.4.3-12.el7 fixed in 1.4.3-12.el7_6.3 | 8.1% Low-Moderate Risk | Not Applicable |
| CVE-2021-46848 | NONE0 | libtasn1 4.10-1.el7 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2016-6223 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-49794 | NONE0 | libxml2 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7_9.10 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-49796 | NONE0 | libxml2 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7_9.10 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2017-8872 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-49794 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7_9.10 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-49796 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7_9.10 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2017-8872 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-12403 | NONE0 | nss-tools 3.36.0-7.el7_5 fixed in 3.53.1-3.el7_9 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2019-9948 | NONE0 | python-libs 2.7.5-76.el7 fixed in 2.7.5-86.el7 | 12.3% High Exploitation Risk | Not Applicable |
| CVE-2024-3596 | NONE0 | krb5-libs 1.15.1-34.el7 fixed in 1.15.1-55.el7_9.3 | 14.9% High Exploitation Risk | Not Applicable |
| CVE-2019-8675 | NONE0 | cups-libs 1:1.6.3-35.el7 fixed in 1:1.6.3-51.el7 | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-8696 | NONE0 | cups-libs 1:1.6.3-35.el7 fixed in 1:1.6.3-51.el7 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-24407 | NONE0 | cyrus-sasl-lib 2.1.26-23.el7 fixed in 2.1.26-24.el7_9 | 4.1% Low-Moderate Risk | Not Applicable |
| CVE-2021-45960 | NONE0 | expat 2.1.0-10.el7_3 fixed in 2.1.0-14.el7_9 | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-22825 | NONE0 | expat 2.1.0-10.el7_3 fixed in 2.1.0-14.el7_9 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-22826 | NONE0 | expat 2.1.0-10.el7_3 fixed in 2.1.0-14.el7_9 | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-22827 | NONE0 | expat 2.1.0-10.el7_3 fixed in 2.1.0-14.el7_9 | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2018-7999 | NONE0 | graphite2 1.3.10-1.el7_3 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2018-19540 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2018-19541 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-42898 | NONE0 | krb5-libs 1.15.1-34.el7 fixed in 1.15.1-55.el7_9 | 6.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-27534 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2016-3616 | NONE0 | libjpeg-turbo 1.2.90-6.el7 fixed in 1.2.90-8.el7 | 4.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-17541 | NONE0 | libjpeg-turbo 1.2.90-6.el7 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-9614 | NONE0 | libjpeg-turbo 1.2.90-6.el7 No fix yet | 8.2% Low-Moderate Risk | Not Applicable |
| CVE-2015-8540 | NONE0 | libpng 2:1.5.13-7.el7_2 No fix yet | 6.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-3855 | NONE0 | libssh2 1.4.3-12.el7 fixed in 1.4.3-12.el7_6.2 | 9.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-3856 | NONE0 | libssh2 1.4.3-12.el7 fixed in 1.4.3-12.el7_6.2 | 6.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-3857 | NONE0 | libssh2 1.4.3-12.el7 fixed in 1.4.3-12.el7_6.2 | 6.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-3863 | NONE0 | libssh2 1.4.3-12.el7 fixed in 1.4.3-12.el7_6.2 | 3.4% Low-Moderate Risk | Not Applicable |
| CVE-2025-5372 | NONE0 | libssh2 1.4.3-12.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-6891 | NONE0 | libtasn1 4.10-1.el7 No fix yet | 5.6% Low-Moderate Risk | Not Applicable |
| CVE-2025-9900 | NONE0 | libtiff 4.0.3-27.el7_3 fixed in 4.0.3-35.el7_9.1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2017-11335 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 3.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-17095 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 10.6% High Exploitation Risk | Not Applicable |
| CVE-2017-5563 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2017-9935 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 3.9% Low-Moderate Risk | Not Applicable |
| CVE-2018-12900 | NONE0 | libtiff 4.0.3-27.el7_3 fixed in 4.0.3-32.el7 | 25.2% High Exploitation Risk | Not Applicable |
| CVE-2018-16335 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-18557 | NONE0 | libtiff 4.0.3-27.el7_3 fixed in 4.0.3-32.el7 | 15.0% High Exploitation Risk | Not Applicable |
| CVE-2019-17546 | NONE0 | libtiff 4.0.3-27.el7_3 fixed in 4.0.3-35.el7 | 3.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-6128 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 3.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-3970 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2017-17942 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-17100 | NONE0 | libtiff 4.0.3-27.el7_3 fixed in 4.0.3-32.el7 | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-17101 | NONE0 | libtiff 4.0.3-27.el7_3 fixed in 4.0.3-32.el7 | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2018-5360 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2018-8905 | NONE0 | libtiff 4.0.3-27.el7_3 fixed in 4.0.3-32.el7 | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2016-5131 | NONE0 | libxml2 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7.4 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2017-15412 | NONE0 | libxml2 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7.4 | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2021-3518 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2016-5131 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7.4 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2017-15412 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7.4 | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2021-3518 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2016-1841 | NONE0 | libxslt 1.1.28-5.el7 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2016-4738 | NONE0 | libxslt 1.1.28-5.el7 No fix yet | 4.1% Low-Moderate Risk | Not Applicable |
| CVE-2021-39537 | NONE0 | ncurses 5.9-14.20130511.el7_4 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-39537 | NONE0 | ncurses-base 5.9-14.20130511.el7_4 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-39537 | NONE0 | ncurses-libs 5.9-14.20130511.el7_4 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-11745 | NONE0 | nss-tools 3.36.0-7.el7_5 fixed in 3.44.0-7.el7_7 | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-0767 | NONE0 | nss-tools 3.36.0-7.el7_5 fixed in 3.79.0-5.el7_9 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2019-11756 | NONE0 | nss-tools 3.36.0-7.el7_5 fixed in 3.53.1-3.el7_9 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-44638 | NONE0 | pixman 0.34.0-1.el7 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-15688 | NONE0 | systemd 219-62.el7 fixed in 219-62.el7_6.2 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2018-15688 | NONE0 | systemd-libs 219-62.el7 fixed in 219-62.el7_6.2 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2022-1271 | NONE0 | xz-libs 5.2.2-1.el7 fixed in 5.2.2-2.el7_9 | 4.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-8616 | NONE0 | bind-license 32:9.9.4-72.el7 fixed in 32:9.11.4-16.P2.el7_8.6 | 10.6% High Exploitation Risk | Not Applicable |
| CVE-2026-13321 | NONE0 | bind-license 32:9.9.4-72.el7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-3517 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 8.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-3517 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 8.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-55200 | NONE0 | libssh2 1.4.3-12.el7 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-58010 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-3890 | NONE0 | atk 2.28.1-1.el7 fixed in 2.28.1-2.el7 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2020-8625 | NONE0 | bind-license 32:9.9.4-72.el7 fixed in 32:9.11.4-26.P2.el7_9.4 | 64.2% Actively Exploited | Not Applicable |
| CVE-2022-40674 | NONE0 | expat 2.1.0-10.el7_3 fixed in 2.1.0-15.el7_9 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2016-4472 | NONE0 | expat 2.1.0-10.el7_3 No fix yet | 12.4% High Exploitation Risk | Not Applicable |
| CVE-2025-27363 | NONE0 | freetype 2.8-12.el7_6.1 fixed in 2.8-15.el7_9.1 | 26.0% High Exploitation Risk | Not Applicable |
| CVE-2026-8286 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-27778 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2016-9586 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 4.9% Low-Moderate Risk | Not Applicable |
| CVE-2025-15079 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-13790 | NONE0 | libjpeg-turbo 1.2.90-6.el7 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-25646 | NONE0 | libpng 2:1.5.13-7.el7_2 fixed in 2:1.5.13-8.el7_9.2 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2019-13115 | NONE0 | libssh2 1.4.3-12.el7 No fix yet | 11.7% High Exploitation Risk | Not Applicable |
| CVE-2019-17498 | NONE0 | libssh2 1.4.3-12.el7 fixed in 1.8.0-4.el7 | 3.8% Low-Moderate Risk | Not Applicable |
| CVE-2025-5987 | NONE0 | libssh2 1.4.3-12.el7 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-6100 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-58060 | NONE0 | cups-libs 1:1.6.3-35.el7 fixed in 1:1.6.3-52.el7_9.1 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2020-35492 | NONE0 | cairo 1.15.12-3.el7 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2016-6318 | NONE0 | cracklib 2.9.0-11.el7 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2016-6318 | NONE0 | cracklib-dicts 2.9.0-11.el7 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2018-4180 | NONE0 | cups-libs 1:1.6.3-35.el7 fixed in 1:1.6.3-43.el7 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-3898 | NONE0 | cups-libs 1:1.6.3-35.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-35512 | NONE0 | dbus 1:1.10.24-12.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-35512 | NONE0 | dbus-libs 1:1.10.24-12.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-46143 | NONE0 | expat 2.1.0-10.el7_3 fixed in 2.1.0-14.el7_9 | 3.8% Low-Moderate Risk | Not Applicable |
| CVE-2016-10244 | NONE0 | freetype 2.8-12.el7_6.1 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-18397 | NONE0 | fribidi 1.0.2-1.el7 fixed in 1.0.2-1.el7_7.1 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-25308 | NONE0 | fribidi 1.0.2-1.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2015-8875 | NONE0 | gdk-pixbuf2 2.36.12-3.el7 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2017-2870 | NONE0 | gdk-pixbuf2 2.36.12-3.el7 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-48622 | NONE0 | gdk-pixbuf2 2.36.12-3.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-7245 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2017-7246 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-6852 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2020-27828 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2016-8886 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2018-19543 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-51257 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-12762 | NONE0 | json-c 0.11-4.el7_0 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2020-14363 | NONE0 | libX11 1.6.5-2.el7 fixed in 1.6.7-3.el7_9 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2018-15857 | NONE0 | libX11 1.6.5-2.el7 fixed in 1.6.7-2.el7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-43787 | NONE0 | libX11 1.6.5-2.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-14363 | NONE0 | libX11-common 1.6.5-2.el7 fixed in 1.6.7-3.el7_9 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2018-15857 | NONE0 | libX11-common 1.6.5-2.el7 fixed in 1.6.7-2.el7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-43787 | NONE0 | libX11-common 1.6.5-2.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2014-9114 | NONE0 | libblkid 2.23.2-59.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2016-2779 | NONE0 | libblkid 2.23.2-59.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-2603 | NONE0 | libcap 2.22-9.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-1304 | NONE0 | libcom_err 1.42.9-13.el7 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-8177 | NONE0 | libcurl 7.29.0-51.el7 fixed in 7.29.0-59.el7_9.1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2018-20483 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2019-5436 | NONE0 | libcurl 7.29.0-51.el7 fixed in 7.29.0-57.el7 | 49.7% High Exploitation Risk | Not Applicable |
| CVE-2017-10140 | NONE0 | libdb 5.3.21-24.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2017-10140 | NONE0 | libdb-utils 5.3.21-24.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-2201 | NONE0 | libjpeg-turbo 1.2.90-6.el7 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2014-9114 | NONE0 | libmount 2.23.2-59.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2016-2779 | NONE0 | libmount 2.23.2-59.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-8176 | NONE0 | libtiff 4.0.3-27.el7_3 fixed in 4.0.3-35.el7_9.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8177 | NONE0 | libtiff 4.0.3-27.el7_3 fixed in 4.0.3-35.el7_9.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-4775 | NONE0 | libtiff 4.0.3-27.el7_3 fixed in 4.0.3-35.el7_9.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2016-10092 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2016-10093 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2016-10094 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2016-9453 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2020-35523 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2020-35524 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2016-10268 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2016-10269 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2016-10270 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2016-10271 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2016-10272 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2017-7592 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2017-7596 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2017-7597 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2017-7598 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-7599 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2017-7600 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-7601 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-7602 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2014-9114 | NONE0 | libuuid 2.23.2-59.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2016-2779 | NONE0 | libuuid 2.23.2-59.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-7425 | NONE0 | libxml2 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7_9.12 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2017-0663 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2021-3516 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-40304 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 6.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-49043 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11979 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-7425 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7_9.12 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2017-0663 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2021-3516 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-40304 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 6.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-49043 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11979 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-55549 | NONE0 | libxslt 1.1.28-5.el7 fixed in 1.1.28-9.el7_9 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-24855 | NONE0 | libxslt 1.1.28-5.el7 fixed in 1.1.28-9.el7_9 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-29491 | NONE0 | ncurses 5.9-14.20130511.el7_4 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2017-16879 | NONE0 | ncurses 5.9-14.20130511.el7_4 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-29491 | NONE0 | ncurses-base 5.9-14.20130511.el7_4 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2017-16879 | NONE0 | ncurses-base 5.9-14.20130511.el7_4 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-29491 | NONE0 | ncurses-libs 5.9-14.20130511.el7_4 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2017-16879 | NONE0 | ncurses-libs 5.9-14.20130511.el7_4 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2025-6020 | NONE0 | pam 1.1.8-22.el7 fixed in 1.1.8-23.el7_9.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-8941 | NONE0 | pam 1.1.8-22.el7 fixed in 1.1.8-23.el7_9.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2017-7245 | NONE0 | pcre 8.32-17.el7 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2017-7246 | NONE0 | pcre 8.32-17.el7 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2024-9287 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2017-7500 | NONE0 | rpm-build-libs 4.11.3-35.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-7501 | NONE0 | rpm-build-libs 4.11.3-35.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-7500 | NONE0 | rpm-libs 4.11.3-35.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-7501 | NONE0 | rpm-libs 4.11.3-35.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-7500 | NONE0 | rpm-python 4.11.3-35.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-7501 | NONE0 | rpm-python 4.11.3-35.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-16864 | NONE0 | systemd 219-62.el7 fixed in 219-62.el7_6.2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2018-16865 | NONE0 | systemd 219-62.el7 fixed in 219-62.el7_6.2 | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2017-18078 | NONE0 | systemd 219-62.el7 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-15686 | NONE0 | systemd 219-62.el7 fixed in 219-67.el7 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2018-6954 | NONE0 | systemd 219-62.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-26604 | NONE0 | systemd 219-62.el7 fixed in 219-78.el7_9.11 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-16864 | NONE0 | systemd-libs 219-62.el7 fixed in 219-62.el7_6.2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2018-16865 | NONE0 | systemd-libs 219-62.el7 fixed in 219-62.el7_6.2 | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2017-18078 | NONE0 | systemd-libs 219-62.el7 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-15686 | NONE0 | systemd-libs 219-62.el7 fixed in 219-67.el7 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2018-6954 | NONE0 | systemd-libs 219-62.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-26604 | NONE0 | systemd-libs 219-62.el7 fixed in 219-78.el7_9.11 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-13601 | NONE0 | glib2 2.56.1-2.el7 fixed in 2.56.1-11.el7_9 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-24928 | NONE0 | libxml2 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7_9.9 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-24928 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7_9.9 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2015-8947 | NONE0 | harfbuzz 1.7.5-2.el7 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2016-2052 | NONE0 | harfbuzz 1.7.5-2.el7 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2018-5743 | NONE0 | bind-license 32:9.9.4-72.el7 fixed in 32:9.9.4-74.el7_6.1 | 6.5% Low-Moderate Risk | Not Applicable |
| CVE-2021-25215 | NONE0 | bind-license 32:9.9.4-72.el7 fixed in 32:9.11.4-26.P2.el7_9.5 | 11.4% High Exploitation Risk | Not Applicable |
| CVE-2022-38177 | NONE0 | bind-license 32:9.9.4-72.el7 fixed in 32:9.11.4-26.P2.el7_9.10 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-38178 | NONE0 | bind-license 32:9.9.4-72.el7 fixed in 32:9.11.4-26.P2.el7_9.10 | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-2828 | NONE0 | bind-license 32:9.9.4-72.el7 fixed in 32:9.11.4-26.P2.el7_9.14 | 3.8% Low-Moderate Risk | Not Applicable |
| CVE-2023-3341 | NONE0 | bind-license 32:9.9.4-72.el7 fixed in 32:9.11.4-26.P2.el7_9.15 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-4408 | NONE0 | bind-license 32:9.9.4-72.el7 fixed in 32:9.11.4-26.P2.el7_9.16 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-50387 | NONE0 | bind-license 32:9.9.4-72.el7 fixed in 32:9.11.4-26.P2.el7_9.16 | 100.0% Actively Exploited | Not Applicable |
| CVE-2023-50868 | NONE0 | bind-license 32:9.9.4-72.el7 fixed in 32:9.11.4-26.P2.el7_9.16 | 81.7% Actively Exploited | Not Applicable |
| CVE-2024-11187 | NONE0 | bind-license 32:9.9.4-72.el7 fixed in 32:9.11.4-26.P2.el7_9.18 | 15.5% High Exploitation Risk | Not Applicable |
| CVE-2024-1737 | NONE0 | bind-license 32:9.9.4-72.el7 fixed in 32:9.11.4-26.P2.el7_9.17 | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-1975 | NONE0 | bind-license 32:9.9.4-72.el7 fixed in 32:9.11.4-26.P2.el7_9.17 | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-11331 | NONE0 | bind-license 32:9.9.4-72.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-11622 | NONE0 | bind-license 32:9.9.4-72.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-11721 | NONE0 | bind-license 32:9.9.4-72.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12617 | NONE0 | bind-license 32:9.9.4-72.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-13204 | NONE0 | bind-license 32:9.9.4-72.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-3039 | NONE0 | bind-license 32:9.9.4-72.el7 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-5946 | NONE0 | bind-license 32:9.9.4-72.el7 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2018-5742 | NONE0 | bind-license 32:9.9.4-72.el7 fixed in 32:9.9.4-73.el7_6 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2019-6477 | NONE0 | bind-license 32:9.9.4-72.el7 fixed in 32:9.11.4-16.P2.el7 | 4.1% Low-Moderate Risk | Not Applicable |
| CVE-2020-8623 | NONE0 | bind-license 32:9.9.4-72.el7 fixed in 32:9.11.4-26.P2.el7_9.2 | 6.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-3094 | NONE0 | bind-license 32:9.9.4-72.el7 No fix yet | 13.2% High Exploitation Risk | Not Applicable |
| CVE-2017-9814 | NONE0 | cairo 1.15.12-3.el7 No fix yet | 3.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-5818 | NONE0 | cairo 1.15.12-3.el7 fixed in 1.15.12-4.el7 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2018-5819 | NONE0 | cairo 1.15.12-3.el7 fixed in 1.15.12-4.el7 | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2017-18190 | NONE0 | cups-libs 1:1.6.3-35.el7 fixed in 1:1.6.3-51.el7 | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2026-34980 | NONE0 | cups-libs 1:1.6.3-35.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-19906 | NONE0 | cyrus-sasl-lib 2.1.26-23.el7 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-6893 | NONE0 | dracut 033-554.el7 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-45186 | NONE0 | expat 2.1.0-10.el7_3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2015-2716 | NONE0 | expat 2.1.0-10.el7_3 fixed in 2.1.0-11.el7 | 7.4% Low-Moderate Risk | Not Applicable |
| CVE-2016-5300 | NONE0 | expat 2.1.0-10.el7_3 No fix yet | 6.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-9233 | NONE0 | expat 2.1.0-10.el7_3 No fix yet | 9.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-20843 | NONE0 | expat 2.1.0-10.el7_3 fixed in 2.1.0-12.el7 | 7.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-23990 | NONE0 | expat 2.1.0-10.el7_3 No fix yet | 4.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-43680 | NONE0 | expat 2.1.0-10.el7_3 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-52425 | NONE0 | expat 2.1.0-10.el7_3 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2024-45490 | NONE0 | expat 2.1.0-10.el7_3 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2024-8176 | NONE0 | expat 2.1.0-10.el7_3 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2019-15903 | NONE0 | expat 2.1.0-10.el7_3 fixed in 2.1.0-12.el7 | 6.7% Low-Moderate Risk | Not Applicable |
| CVE-2022-27405 | NONE0 | freetype 2.8-12.el7_6.1 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-27406 | NONE0 | freetype 2.8-12.el7_6.1 No fix yet | 3.4% Low-Moderate Risk | Not Applicable |
| CVE-2014-9747 | NONE0 | freetype 2.8-12.el7_6.1 No fix yet | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-5201 | NONE0 | gdk-pixbuf2 2.36.12-3.el7 fixed in 2.36.12-5.el7_9 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2016-6352 | NONE0 | gdk-pixbuf2 2.36.12-3.el7 No fix yet | 3.9% Low-Moderate Risk | Not Applicable |
| CVE-2025-7345 | NONE0 | gdk-pixbuf2 2.36.12-3.el7 fixed in 2.36.12-4.el7_9 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2021-27219 | NONE0 | glib2 2.56.1-2.el7 fixed in 2.56.1-9.el7_9 | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2015-2327 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 4.0% Low-Moderate Risk | Not Applicable |
| CVE-2015-2328 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2015-3217 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 6.2% Low-Moderate Risk | Not Applicable |
| CVE-2015-8388 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 6.6% Low-Moderate Risk | Not Applicable |
| CVE-2021-27218 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 4.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-58011 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2017-11164 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-16429 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 3.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-5818 | NONE0 | glib2 2.56.1-2.el7 fixed in 2.56.1-5.el7 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2018-5819 | NONE0 | glib2 2.56.1-2.el7 fixed in 2.56.1-5.el7 | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-13012 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-29499 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-32636 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2021-43618 | NONE0 | gmp 1:6.0.0-15.el7 No fix yet | 3.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-25193 | NONE0 | harfbuzz 1.7.5-2.el7 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2017-13748 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 4.7% Low-Moderate Risk | Not Applicable |
| CVE-2016-9397 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 3.6% Low-Moderate Risk | Not Applicable |
| CVE-2016-9398 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 6.0% Low-Moderate Risk | Not Applicable |
| CVE-2016-9399 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 3.8% Low-Moderate Risk | Not Applicable |
| CVE-2017-13745 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 3.9% Low-Moderate Risk | Not Applicable |
| CVE-2017-13747 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 3.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-13749 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 3.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-13751 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 3.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-13752 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 3.6% Low-Moderate Risk | Not Applicable |
| CVE-2020-28196 | NONE0 | krb5-libs 1.15.1-34.el7 No fix yet | 4.4% Low-Moderate Risk | Not Applicable |
| CVE-2021-36222 | NONE0 | krb5-libs 1.15.1-34.el7 No fix yet | 10.3% High Exploitation Risk | Not Applicable |
| CVE-2024-37370 | NONE0 | krb5-libs 1.15.1-34.el7 fixed in 1.15.1-55.el7_9.2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-40355 | NONE0 | krb5-libs 1.15.1-34.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-40356 | NONE0 | krb5-libs 1.15.1-34.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2018-14598 | NONE0 | libX11 1.6.5-2.el7 fixed in 1.6.7-2.el7 | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-3138 | NONE0 | libX11 1.6.5-2.el7 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2018-14598 | NONE0 | libX11-common 1.6.5-2.el7 fixed in 1.6.7-2.el7 | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-3138 | NONE0 | libX11-common 1.6.5-2.el7 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-16612 | NONE0 | libXcursor 1.1.15-1.el7 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2016-7945 | NONE0 | libXi 1.7.9-1.el7 No fix yet | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2016-7946 | NONE0 | libXi 1.7.9-1.el7 No fix yet | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2016-7952 | NONE0 | libXtst 1.2.3-1.el7 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-11586 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8927 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8932 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9079 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2016-8615 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 4.5% Low-Moderate Risk | Not Applicable |
| CVE-2016-8624 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 5.9% Low-Moderate Risk | Not Applicable |
| CVE-2016-8625 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 4.3% Low-Moderate Risk | Not Applicable |
| CVE-2017-1000254 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 8.5% Low-Moderate Risk | Not Applicable |
| CVE-2020-8285 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 9.9% Low-Moderate Risk | Not Applicable |
| CVE-2021-22946 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 4.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-27780 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-27782 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-43551 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 16.5% High Exploitation Risk | Not Applicable |
| CVE-2024-2398 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 36.1% High Exploitation Risk | Not Applicable |
| CVE-2026-5773 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2016-8621 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 4.9% Low-Moderate Risk | Not Applicable |
| CVE-2016-8623 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2020-8231 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2022-27781 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-6276 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-33560 | NONE0 | libgcrypt 1.5.3-14.el7 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-41989 | NONE0 | libgcrypt 1.5.3-14.el7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2015-2059 | NONE0 | libidn 1.28-4.el7 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2015-8948 | NONE0 | libidn 1.28-4.el7 No fix yet | 6.7% Low-Moderate Risk | Not Applicable |
| CVE-2016-6261 | NONE0 | libidn 1.28-4.el7 No fix yet | 3.9% Low-Moderate Risk | Not Applicable |
| CVE-2016-6262 | NONE0 | libidn 1.28-4.el7 No fix yet | 6.5% Low-Moderate Risk | Not Applicable |
| CVE-2016-6263 | NONE0 | libidn 1.28-4.el7 No fix yet | 3.9% Low-Moderate Risk | Not Applicable |
| CVE-2018-11813 | NONE0 | libjpeg-turbo 1.2.90-6.el7 fixed in 1.2.90-8.el7 | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-33416 | NONE0 | libpng 2:1.5.13-7.el7_2 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2016-10087 | NONE0 | libpng 2:1.5.13-7.el7_2 No fix yet | 5.5% Low-Moderate Risk | Not Applicable |
| CVE-2020-22218 | NONE0 | libssh2 1.4.3-12.el7 fixed in 1.8.0-4.el7_9.1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-3731 | NONE0 | libssh2 1.4.3-12.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-55199 | NONE0 | libssh2 1.4.3-12.el7 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-58050 | NONE0 | libssh2 1.4.3-12.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-6003 | NONE0 | libtasn1 4.10-1.el7 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2017-10790 | NONE0 | libtasn1 4.10-1.el7 No fix yet | 5.0% Low-Moderate Risk | Not Applicable |
| CVE-2016-5323 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2020-19131 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-52355 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2023-52356 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-7006 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2016-3624 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 4.1% Low-Moderate Risk | Not Applicable |
| CVE-2016-3631 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2016-9297 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 6.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-10688 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 6.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-12944 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-16232 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 5.4% Low-Moderate Risk | Not Applicable |
| CVE-2016-4483 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 6.2% Low-Moderate Risk | Not Applicable |
| CVE-2017-16932 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 5.9% Low-Moderate Risk | Not Applicable |
| CVE-2017-9047 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2017-9049 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 4.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-9050 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 4.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-14404 | NONE0 | libxml2 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7.4 | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-19956 | NONE0 | libxml2 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7.5 | 5.5% Low-Moderate Risk | Not Applicable |
| CVE-2019-20388 | NONE0 | libxml2 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7.5 | 4.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-7595 | NONE0 | libxml2 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7.5 | 7.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-23308 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 6.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-40303 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 22.8% High Exploitation Risk | Not Applicable |
| CVE-2024-25062 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2025-32414 | NONE0 | libxml2 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7_9.10 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-32415 | NONE0 | libxml2 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7_9.13 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-6021 | NONE0 | libxml2 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7_9.10 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-6732 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2017-9048 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 4.9% Low-Moderate Risk | Not Applicable |
| CVE-2025-27113 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2016-4483 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 6.2% Low-Moderate Risk | Not Applicable |
| CVE-2017-16932 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 5.9% Low-Moderate Risk | Not Applicable |
| CVE-2017-9047 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2017-9049 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 4.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-9050 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 4.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-14404 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7.4 | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-19956 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7.5 | 5.5% Low-Moderate Risk | Not Applicable |
| CVE-2019-20388 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7.5 | 4.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-7595 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7.5 | 7.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-23308 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 6.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-40303 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 22.8% High Exploitation Risk | Not Applicable |
| CVE-2024-25062 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2025-32414 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7_9.10 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-32415 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7_9.13 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-6021 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7_9.10 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-6732 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2017-9048 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 4.9% Low-Moderate Risk | Not Applicable |
| CVE-2025-27113 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2016-1683 | NONE0 | libxslt 1.1.28-5.el7 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2016-1684 | NONE0 | libxslt 1.1.28-5.el7 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-18197 | NONE0 | libxslt 1.1.28-5.el7 fixed in 1.1.28-6.el7 | 4.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-11112 | NONE0 | ncurses 5.9-14.20130511.el7_4 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2017-11113 | NONE0 | ncurses 5.9-14.20130511.el7_4 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2017-13728 | NONE0 | ncurses 5.9-14.20130511.el7_4 No fix yet | 3.9% Low-Moderate Risk | Not Applicable |
| CVE-2017-11112 | NONE0 | ncurses-base 5.9-14.20130511.el7_4 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2017-11113 | NONE0 | ncurses-base 5.9-14.20130511.el7_4 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2017-13728 | NONE0 | ncurses-base 5.9-14.20130511.el7_4 No fix yet | 3.9% Low-Moderate Risk | Not Applicable |
| CVE-2017-11112 | NONE0 | ncurses-libs 5.9-14.20130511.el7_4 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2017-11113 | NONE0 | ncurses-libs 5.9-14.20130511.el7_4 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2017-13728 | NONE0 | ncurses-libs 5.9-14.20130511.el7_4 No fix yet | 3.9% Low-Moderate Risk | Not Applicable |
| CVE-2016-2183 | NONE0 | nss-tools 3.36.0-7.el7_5 No fix yet | 95.7% Actively Exploited | Not Applicable |
| CVE-2019-11719 | NONE0 | nss-tools 3.36.0-7.el7_5 fixed in 3.53.1-3.el7_9 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-11729 | NONE0 | nss-tools 3.36.0-7.el7_5 fixed in 3.44.0-7.el7_7 | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-17007 | NONE0 | nss-tools 3.36.0-7.el7_5 fixed in 3.44.0-4.el7 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-25648 | NONE0 | nss-tools 3.36.0-7.el7_5 fixed in 3.53.1-7.el7_9 | 3.9% Low-Moderate Risk | Not Applicable |
| CVE-2019-13565 | NONE0 | openldap 2.4.44-20.el7 No fix yet | 5.0% Low-Moderate Risk | Not Applicable |
| CVE-2020-12243 | NONE0 | openldap 2.4.44-20.el7 fixed in 2.4.44-22.el7 | 4.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-25692 | NONE0 | openldap 2.4.44-20.el7 fixed in 2.4.44-23.el7_9 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2020-25709 | NONE0 | openldap 2.4.44-20.el7 fixed in 2.4.44-25.el7_9 | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2020-25710 | NONE0 | openldap 2.4.44-20.el7 fixed in 2.4.44-25.el7_9 | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2020-36221 | NONE0 | openldap 2.4.44-20.el7 No fix yet | 84.2% Actively Exploited | Not Applicable |
| CVE-2020-36222 | NONE0 | openldap 2.4.44-20.el7 No fix yet | 77.7% Actively Exploited | Not Applicable |
| CVE-2020-36223 | NONE0 | openldap 2.4.44-20.el7 No fix yet | 4.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-36224 | NONE0 | openldap 2.4.44-20.el7 No fix yet | 4.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-36225 | NONE0 | openldap 2.4.44-20.el7 No fix yet | 4.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-36226 | NONE0 | openldap 2.4.44-20.el7 No fix yet | 4.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-36227 | NONE0 | openldap 2.4.44-20.el7 No fix yet | 77.7% Actively Exploited | Not Applicable |
| CVE-2020-36228 | NONE0 | openldap 2.4.44-20.el7 No fix yet | 83.4% Actively Exploited | Not Applicable |
| CVE-2020-36229 | NONE0 | openldap 2.4.44-20.el7 No fix yet | 4.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-36230 | NONE0 | openldap 2.4.44-20.el7 No fix yet | 12.3% High Exploitation Risk | Not Applicable |
| CVE-2021-27212 | NONE0 | openldap 2.4.44-20.el7 No fix yet | 64.1% Actively Exploited | Not Applicable |
| CVE-2023-2953 | NONE0 | openldap 2.4.44-20.el7 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2018-5818 | NONE0 | pango 1.42.4-2.el7_6 fixed in 1.42.4-3.el7 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2018-5819 | NONE0 | pango 1.42.4-2.el7_6 fixed in 1.42.4-3.el7 | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2017-6004 | NONE0 | pcre 8.32-17.el7 No fix yet | 4.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-7186 | NONE0 | pcre 8.32-17.el7 No fix yet | 5.0% Low-Moderate Risk | Not Applicable |
| CVE-2017-11164 | NONE0 | pcre 8.32-17.el7 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2016-10109 | NONE0 | pcsc-lite-libs 1.8.8-8.el7 No fix yet | 4.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-24329 | NONE0 | python-libs 2.7.5-76.el7 fixed in 2.7.5-93.el7_9 | 20.5% High Exploitation Risk | Not Applicable |
| CVE-2026-15308 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2018-14647 | NONE0 | python-libs 2.7.5-76.el7 fixed in 2.7.5-86.el7 | 11.3% High Exploitation Risk | Not Applicable |
| CVE-2019-16056 | NONE0 | python-libs 2.7.5-76.el7 fixed in 2.7.5-88.el7 | 5.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-20907 | NONE0 | python-libs 2.7.5-76.el7 fixed in 2.7.5-90.el7 | 6.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-5010 | NONE0 | python-libs 2.7.5-76.el7 fixed in 2.7.5-86.el7 | 21.4% High Exploitation Risk | Not Applicable |
| CVE-2020-10735 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 5.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-0391 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 8.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-45061 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-48560 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2024-6232 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-3644 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4224 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-7210 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2019-9674 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 5.5% Low-Moderate Risk | Not Applicable |
| CVE-2021-3737 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 12.0% High Exploitation Risk | Not Applicable |
| CVE-2024-7592 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2015-8865 | NONE0 | file-libs 5.11-35.el7 No fix yet | 5.0% Low-Moderate Risk | Not Applicable |
| CVE-2016-0755 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 9.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-12912 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-61144 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-17049 | NONE0 | krb5-libs 1.15.1-34.el7 No fix yet | 13.8% High Exploitation Risk | Not Applicable |
| CVE-2020-26116 | NONE0 | python-libs 2.7.5-76.el7 fixed in 2.7.5-92.el7_9 | 6.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-34241 | NONE0 | cups-libs 1:1.6.3-35.el7 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-12749 | NONE0 | dbus 1:1.10.24-12.el7 fixed in 1:1.10.24-15.el7 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-12749 | NONE0 | dbus-libs 1:1.10.24-12.el7 fixed in 1:1.10.24-15.el7 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2017-6313 | NONE0 | gdk-pixbuf2 2.36.12-3.el7 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2020-23922 | NONE0 | giflib 4.1.6-9.el7 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-48161 | NONE0 | giflib 4.1.6-9.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-14822 | NONE0 | glib2 2.56.1-2.el7 fixed in 2.56.1-7.el7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-26926 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2015-2696 | NONE0 | krb5-libs 1.15.1-34.el7 No fix yet | 4.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-54369 | NONE0 | libacl 2.2.51-14.el7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2021-29390 | NONE0 | libjpeg-turbo 1.2.90-6.el7 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-64720 | NONE0 | libpng 2:1.5.13-7.el7_2 fixed in 2:1.5.13-8.el7_9.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-0891 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-4786 | NONE0 | python-libs 2.7.5-76.el7 fixed in 2.7.5-94.el7_9.5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-15366 | NONE0 | python-libs 2.7.5-76.el7 fixed in 2.7.5-94.el7_9.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15367 | NONE0 | python-libs 2.7.5-76.el7 fixed in 2.7.5-94.el7_9.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-43818 | NONE0 | python-lxml 3.2.1-4.el7 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-4504 | NONE0 | cups-libs 1:1.6.3-35.el7 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-23868 | NONE0 | giflib 4.1.6-9.el7 fixed in 4.1.6-9.el7_9.1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-52533 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-6655 | NONE0 | gtk-update-icon-cache 3.22.30-3.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-6655 | NONE0 | gtk2 2.24.31-1.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-4878 | NONE0 | libcap 2.22-9.el7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2016-8617 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-20271 | NONE0 | rpm-build-libs 4.11.3-35.el7 fixed in 4.11.3-48.el7_9 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-44604 | NONE0 | rpm-build-libs 4.11.3-35.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-20271 | NONE0 | rpm-libs 4.11.3-35.el7 fixed in 4.11.3-48.el7_9 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-44604 | NONE0 | rpm-libs 4.11.3-35.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-20271 | NONE0 | rpm-python 4.11.3-35.el7 fixed in 4.11.3-48.el7_9 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-44604 | NONE0 | rpm-python 4.11.3-35.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-3842 | NONE0 | systemd 219-62.el7 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-3842 | NONE0 | systemd-libs 219-62.el7 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-56132 | NONE0 | expat 2.1.0-10.el7_3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56403 | NONE0 | expat 2.1.0-10.el7_3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56404 | NONE0 | expat 2.1.0-10.el7_3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56405 | NONE0 | expat 2.1.0-10.el7_3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56407 | NONE0 | expat 2.1.0-10.el7_3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2021-25220 | NONE0 | bind-license 32:9.9.4-72.el7 fixed in 32:9.11.4-26.P2.el7_9.13 | 3.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-10723 | NONE0 | bind-license 32:9.9.4-72.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2016-4484 | NONE0 | dracut 033-554.el7 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2013-0340 | NONE0 | expat 2.1.0-10.el7_3 No fix yet | 20.1% High Exploitation Risk | Not Applicable |
| CVE-2015-7673 | NONE0 | gdk-pixbuf2 2.36.12-3.el7 No fix yet | 5.4% Low-Moderate Risk | Not Applicable |
| CVE-2015-7674 | NONE0 | gdk-pixbuf2 2.36.12-3.el7 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2014-3564 | NONE0 | gpgme 1.3.2-5.el7 No fix yet | 4.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-13034 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-1965 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2017-7526 | NONE0 | libgcrypt 1.5.3-14.el7 No fix yet | 3.9% Low-Moderate Risk | Not Applicable |
| CVE-2026-22185 | NONE0 | openldap 2.4.44-20.el7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2007-4559 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 27.1% High Exploitation Risk | Not Applicable |
| CVE-2024-6923 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-0938 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-35235 | NONE0 | cups-libs 1:1.6.3-35.el7 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2025-61915 | NONE0 | cups-libs 1:1.6.3-35.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-14344 | NONE0 | libX11 1.6.5-2.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-14344 | NONE0 | libX11-common 1.6.5-2.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-21583 | NONE0 | libblkid 2.23.2-59.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-5094 | NONE0 | libcom_err 1.42.9-13.el7 fixed in 1.42.9-19.el7 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-5188 | NONE0 | libcom_err 1.42.9-13.el7 fixed in 1.42.9-19.el7 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2020-21583 | NONE0 | libmount 2.23.2-59.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-21583 | NONE0 | libuuid 2.23.2-59.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-35938 | NONE0 | rpm-build-libs 4.11.3-35.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-35939 | NONE0 | rpm-build-libs 4.11.3-35.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-35938 | NONE0 | rpm-libs 4.11.3-35.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-35939 | NONE0 | rpm-libs 4.11.3-35.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-35938 | NONE0 | rpm-python 4.11.3-35.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-35939 | NONE0 | rpm-python 4.11.3-35.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-13776 | NONE0 | systemd 219-62.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-4105 | NONE0 | systemd 219-62.el7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2020-13776 | NONE0 | systemd-libs 219-62.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-4105 | NONE0 | systemd-libs 219-62.el7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2021-3782 | NONE0 | libwayland-client 1.15.0-1.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-3782 | NONE0 | libwayland-server 1.15.0-1.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2018-15587 | NONE0 | atk 2.28.1-1.el7 fixed in 2.28.1-2.el7 | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2025-68468 | NONE0 | avahi-libs 0.6.31-19.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68471 | NONE0 | avahi-libs 0.6.31-19.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-24401 | NONE0 | avahi-libs 0.6.31-19.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2018-5741 | NONE0 | bind-license 32:9.9.4-72.el7 fixed in 32:9.11.4-9.P2.el7 | 3.5% Low-Moderate Risk | Not Applicable |
| CVE-2020-8622 | NONE0 | bind-license 32:9.9.4-72.el7 fixed in 32:9.11.4-26.P2.el7_9.2 | 5.6% Low-Moderate Risk | Not Applicable |
| CVE-2021-25214 | NONE0 | bind-license 32:9.9.4-72.el7 fixed in 32:9.11.4-26.P2.el7_9.7 | 6.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-10822 | NONE0 | bind-license 32:9.9.4-72.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-6170 | NONE0 | bind-license 32:9.9.4-72.el7 No fix yet | 40.5% High Exploitation Risk | Not Applicable |
| CVE-2016-3189 | NONE0 | bzip2-libs 1.0.6-13.el7 No fix yet | 15.8% High Exploitation Risk | Not Applicable |
| CVE-2018-18064 | NONE0 | cairo 1.15.12-3.el7 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2019-6461 | NONE0 | cairo 1.15.12-3.el7 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-6462 | NONE0 | cairo 1.15.12-3.el7 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-58364 | NONE0 | cups-libs 1:1.6.3-35.el7 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-34978 | NONE0 | cups-libs 1:1.6.3-35.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-42010 | NONE0 | dbus 1:1.10.24-12.el7 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-42011 | NONE0 | dbus 1:1.10.24-12.el7 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-42012 | NONE0 | dbus 1:1.10.24-12.el7 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-34969 | NONE0 | dbus 1:1.10.24-12.el7 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-42010 | NONE0 | dbus-libs 1:1.10.24-12.el7 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-42011 | NONE0 | dbus-libs 1:1.10.24-12.el7 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-42012 | NONE0 | dbus-libs 1:1.10.24-12.el7 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-34969 | NONE0 | dbus-libs 1:1.10.24-12.el7 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-18520 | NONE0 | elfutils-default-yama-scope 0.172-2.el7 fixed in 0.176-2.el7 | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-7149 | NONE0 | elfutils-default-yama-scope 0.172-2.el7 fixed in 0.176-2.el7 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2018-18520 | NONE0 | elfutils-libelf 0.172-2.el7 fixed in 0.176-2.el7 | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-7149 | NONE0 | elfutils-libelf 0.172-2.el7 fixed in 0.176-2.el7 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2018-18520 | NONE0 | elfutils-libs 0.172-2.el7 fixed in 0.176-2.el7 | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-7149 | NONE0 | elfutils-libs 0.172-2.el7 fixed in 0.176-2.el7 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-25313 | NONE0 | expat 2.1.0-10.el7_3 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2018-10360 | NONE0 | file-libs 5.11-35.el7 fixed in 5.11-36.el7 | 3.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-6942 | NONE0 | freetype 2.8-12.el7_6.1 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-14512 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2013-7447 | NONE0 | gtk2 2.24.31-1.el7 No fix yet | 4.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-9252 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2017-14132 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2018-19539 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2018-19542 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2018-20570 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2018-20622 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2021-37750 | NONE0 | krb5-libs 1.15.1-34.el7 fixed in 1.15.1-51.el7_9 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-24528 | NONE0 | krb5-libs 1.15.1-34.el7 fixed in 1.15.1-55.el7_9.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-27776 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2026-11856 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-3784 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-5545 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6429 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8924 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2017-1000100 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 4.0% Low-Moderate Risk | Not Applicable |
| CVE-2024-7264 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 17.3% High Exploitation Risk | Not Applicable |
| CVE-2025-14524 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2018-14498 | NONE0 | libjpeg-turbo 1.2.90-6.el7 fixed in 1.2.90-8.el7 | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2014-9092 | NONE0 | libjpeg-turbo 1.2.90-6.el7 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2017-15232 | NONE0 | libjpeg-turbo 1.2.90-6.el7 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-11212 | NONE0 | libjpeg-turbo 1.2.90-6.el7 fixed in 1.2.90-8.el7 | 5.0% Low-Moderate Risk | Not Applicable |
| CVE-2018-11213 | NONE0 | libjpeg-turbo 1.2.90-6.el7 fixed in 1.2.90-8.el7 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-11214 | NONE0 | libjpeg-turbo 1.2.90-6.el7 fixed in 1.2.90-8.el7 | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-2283 | NONE0 | libssh2 1.4.3-12.el7 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-15661 | NONE0 | libssh2 1.4.3-12.el7 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-5351 | NONE0 | libssh2 1.4.3-12.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58051 | NONE0 | libssh2 1.4.3-12.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-59844 | NONE0 | libssh2 1.4.3-12.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-66032 | NONE0 | libssh2 1.4.3-12.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-66033 | NONE0 | libssh2 1.4.3-12.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-5318 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 4.8% Low-Moderate Risk | Not Applicable |
| CVE-2016-5319 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2016-5321 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2018-10801 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-14973 | NONE0 | libtiff 4.0.3-27.el7_3 fixed in 4.0.3-35.el7 | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-0865 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-2056 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-2057 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-2058 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-2519 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-3597 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-3598 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-3599 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-3626 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-3627 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-40090 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-3316 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-3618 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-40745 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-41175 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-6277 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2014-8128 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 3.9% Low-Moderate Risk | Not Applicable |
| CVE-2016-3622 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 3.9% Low-Moderate Risk | Not Applicable |
| CVE-2017-13726 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-13727 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2017-9147 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 7.0% Low-Moderate Risk | Not Applicable |
| CVE-2017-9403 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2017-9404 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-9815 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-9936 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 7.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-9937 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2018-10779 | NONE0 | libtiff 4.0.3-27.el7_3 fixed in 4.0.3-32.el7 | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2018-10963 | NONE0 | libtiff 4.0.3-27.el7_3 fixed in 4.0.3-32.el7 | 3.8% Low-Moderate Risk | Not Applicable |
| CVE-2018-18661 | NONE0 | libtiff 4.0.3-27.el7_3 fixed in 4.0.3-32.el7 | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2018-19210 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 3.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-5784 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2018-7456 | NONE0 | libtiff 4.0.3-27.el7_3 fixed in 4.0.3-32.el7 | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-2520 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-2521 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2020-24977 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-3541 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-29824 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2023-28484 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-29469 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-39615 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2017-18258 | NONE0 | libxml2 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7.4 | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2018-14567 | NONE0 | libxml2 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7.4 | 4.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-45322 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2020-24977 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-3541 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-29824 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2023-28484 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-29469 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-39615 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2017-18258 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7.4 | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2018-14567 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7.4 | 4.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-45322 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-40403 | NONE0 | libxslt 1.1.28-5.el7 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-19217 | NONE0 | ncurses 5.9-14.20130511.el7_4 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2017-13729 | NONE0 | ncurses 5.9-14.20130511.el7_4 No fix yet | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2017-13730 | NONE0 | ncurses 5.9-14.20130511.el7_4 No fix yet | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2017-13731 | NONE0 | ncurses 5.9-14.20130511.el7_4 No fix yet | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2017-13732 | NONE0 | ncurses 5.9-14.20130511.el7_4 No fix yet | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2017-13733 | NONE0 | ncurses 5.9-14.20130511.el7_4 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-13734 | NONE0 | ncurses 5.9-14.20130511.el7_4 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2020-19185 | NONE0 | ncurses 5.9-14.20130511.el7_4 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19186 | NONE0 | ncurses 5.9-14.20130511.el7_4 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2020-19187 | NONE0 | ncurses 5.9-14.20130511.el7_4 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19188 | NONE0 | ncurses 5.9-14.20130511.el7_4 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19189 | NONE0 | ncurses 5.9-14.20130511.el7_4 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2020-19190 | NONE0 | ncurses 5.9-14.20130511.el7_4 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses 5.9-14.20130511.el7_4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2018-19217 | NONE0 | ncurses-base 5.9-14.20130511.el7_4 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2017-13729 | NONE0 | ncurses-base 5.9-14.20130511.el7_4 No fix yet | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2017-13730 | NONE0 | ncurses-base 5.9-14.20130511.el7_4 No fix yet | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2017-13731 | NONE0 | ncurses-base 5.9-14.20130511.el7_4 No fix yet | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2017-13732 | NONE0 | ncurses-base 5.9-14.20130511.el7_4 No fix yet | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2017-13733 | NONE0 | ncurses-base 5.9-14.20130511.el7_4 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-13734 | NONE0 | ncurses-base 5.9-14.20130511.el7_4 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2020-19185 | NONE0 | ncurses-base 5.9-14.20130511.el7_4 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19186 | NONE0 | ncurses-base 5.9-14.20130511.el7_4 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2020-19187 | NONE0 | ncurses-base 5.9-14.20130511.el7_4 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19188 | NONE0 | ncurses-base 5.9-14.20130511.el7_4 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19189 | NONE0 | ncurses-base 5.9-14.20130511.el7_4 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2020-19190 | NONE0 | ncurses-base 5.9-14.20130511.el7_4 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 5.9-14.20130511.el7_4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2018-19217 | NONE0 | ncurses-libs 5.9-14.20130511.el7_4 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2017-13729 | NONE0 | ncurses-libs 5.9-14.20130511.el7_4 No fix yet | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2017-13730 | NONE0 | ncurses-libs 5.9-14.20130511.el7_4 No fix yet | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2017-13731 | NONE0 | ncurses-libs 5.9-14.20130511.el7_4 No fix yet | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2017-13732 | NONE0 | ncurses-libs 5.9-14.20130511.el7_4 No fix yet | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2017-13733 | NONE0 | ncurses-libs 5.9-14.20130511.el7_4 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-13734 | NONE0 | ncurses-libs 5.9-14.20130511.el7_4 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2020-19185 | NONE0 | ncurses-libs 5.9-14.20130511.el7_4 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19186 | NONE0 | ncurses-libs 5.9-14.20130511.el7_4 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2020-19187 | NONE0 | ncurses-libs 5.9-14.20130511.el7_4 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19188 | NONE0 | ncurses-libs 5.9-14.20130511.el7_4 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19189 | NONE0 | ncurses-libs 5.9-14.20130511.el7_4 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2020-19190 | NONE0 | ncurses-libs 5.9-14.20130511.el7_4 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-libs 5.9-14.20130511.el7_4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2018-18508 | NONE0 | nss-tools 3.36.0-7.el7_5 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-5388 | NONE0 | nss-tools 3.36.0-7.el7_5 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2019-17023 | NONE0 | nss-tools 3.36.0-7.el7_5 fixed in 3.53.1-3.el7_9 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-7531 | NONE0 | nss-tools 3.36.0-7.el7_5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-26137 | NONE0 | python-libs 2.7.5-76.el7 fixed in 2.7.5-92.el7_9 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-8492 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 6.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-3733 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 4.7% Low-Moderate Risk | Not Applicable |
| CVE-2026-11972 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12610 | NONE0 | pam 1.1.8-22.el7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2015-8382 | NONE0 | pcre 8.32-17.el7 No fix yet | 4.1% Low-Moderate Risk | Not Applicable |
| CVE-2021-35937 | NONE0 | rpm-build-libs 4.11.3-35.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-35937 | NONE0 | rpm-libs 4.11.3-35.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-35937 | NONE0 | rpm-python 4.11.3-35.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-27447 | NONE0 | cups-libs 1:1.6.3-35.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54370 | NONE0 | libacl 2.2.51-14.el7 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-54371 | NONE0 | libattr 2.4.46-13.el7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-39314 | NONE0 | cups-libs 1:1.6.3-35.el7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-39316 | NONE0 | cups-libs 1:1.6.3-35.el7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2016-3186 | NONE0 | libtiff 4.0.3-27.el7_3 fixed in 4.0.3-32.el7 | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-1757 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-1757 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-0450 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libblkid 2.23.2-59.el7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libmount 2.23.2-59.el7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-64506 | NONE0 | libpng 2:1.5.13-7.el7_2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-1355 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-1916 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libuuid 2.23.2-59.el7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2016-3709 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2016-3709 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-6602 | NONE0 | nss-tools 3.36.0-7.el7_5 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2019-16935 | NONE0 | python-libs 2.7.5-76.el7 fixed in 2.7.5-89.el7 | 4.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-18348 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 3.5% Low-Moderate Risk | Not Applicable |
| CVE-2019-9740 | NONE0 | python-libs 2.7.5-76.el7 fixed in 2.7.5-86.el7 | 5.5% Low-Moderate Risk | Not Applicable |
| CVE-2019-9947 | NONE0 | python-libs 2.7.5-76.el7 fixed in 2.7.5-86.el7 | 5.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-6019 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-19787 | NONE0 | python-lxml 3.2.1-4.el7 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-27783 | NONE0 | python-lxml 3.2.1-4.el7 No fix yet | 3.9% Low-Moderate Risk | Not Applicable |
| CVE-2021-28957 | NONE0 | python-lxml 3.2.1-4.el7 No fix yet | 4.0% Low-Moderate Risk | Not Applicable |
| CVE-2020-13529 | NONE0 | systemd 219-62.el7 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-13529 | NONE0 | systemd-libs 219-62.el7 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-5713 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2020-8617 | NONE0 | bind-license 32:9.9.4-72.el7 fixed in 32:9.11.4-16.P2.el7_8.6 | 93.4% Actively Exploited | Not Applicable |
| CVE-2013-5661 | NONE0 | bind-license 32:9.9.4-72.el7 No fix yet | 3.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-4300 | NONE0 | cups-libs 1:1.6.3-35.el7 fixed in 1:1.6.3-43.el7 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2012-6702 | NONE0 | expat 2.1.0-10.el7_3 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2024-50602 | NONE0 | expat 2.1.0-10.el7_3 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-50219 | NONE0 | expat 2.1.0-10.el7_3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56412 | NONE0 | expat 2.1.0-10.el7_3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-31344 | NONE0 | giflib 4.1.6-9.el7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-3576 | NONE0 | krb5-libs 1.15.1-34.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26458 | NONE0 | krb5-libs 1.15.1-34.el7 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | krb5-libs 1.15.1-34.el7 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2021-22947 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-32208 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 6.8% Low-Moderate Risk | Not Applicable |
| CVE-2023-27535 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-27536 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-28321 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2016-8616 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 3.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-43552 | NONE0 | libcurl 7.29.0-51.el7 fixed in 7.29.0-59.el7_9.2 | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-11053 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-12904 | NONE0 | libgcrypt 1.5.3-14.el7 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2021-40528 | NONE0 | libgcrypt 1.5.3-14.el7 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2024-2236 | NONE0 | libgcrypt 1.5.3-14.el7 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2015-0837 | NONE0 | libgcrypt 1.5.3-14.el7 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-48795 | NONE0 | libssh2 1.4.3-12.el7 No fix yet | 93.3% Actively Exploited | Not Applicable |
| CVE-2026-66034 | NONE0 | libssh2 1.4.3-12.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2016-4008 | NONE0 | libtasn1 4.10-1.el7 No fix yet | 25.9% High Exploitation Risk | Not Applicable |
| CVE-2025-13151 | NONE0 | libtasn1 4.10-1.el7 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2021-3537 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 3.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-0990 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2021-3537 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 3.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-0990 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2016-9074 | NONE0 | nss-tools 3.36.0-7.el7_5 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2016-9574 | NONE0 | nss-tools 3.36.0-7.el7_5 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-12404 | NONE0 | nss-tools 3.36.0-7.el7_5 fixed in 3.44.0-4.el7 | 44.4% High Exploitation Risk | Not Applicable |
| CVE-2020-12413 | NONE0 | nss-tools 3.36.0-7.el7_5 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-23336 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 35.7% High Exploitation Risk | Not Applicable |
| CVE-2022-48566 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-41066 | NONE0 | python-lxml 3.2.1-4.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-27774 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2026-3783 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-3468 | NONE0 | avahi-libs 0.6.31-19.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-1981 | NONE0 | avahi-libs 0.6.31-19.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-38469 | NONE0 | avahi-libs 0.6.31-19.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-38470 | NONE0 | avahi-libs 0.6.31-19.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-38471 | NONE0 | avahi-libs 0.6.31-19.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-38472 | NONE0 | avahi-libs 0.6.31-19.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-38473 | NONE0 | avahi-libs 0.6.31-19.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-59529 | NONE0 | avahi-libs 0.6.31-19.el7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68276 | NONE0 | avahi-libs 0.6.31-19.el7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-34933 | NONE0 | avahi-libs 0.6.31-19.el7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2016-9082 | NONE0 | cairo 1.15.12-3.el7 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2017-7475 | NONE0 | cairo 1.15.12-3.el7 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2023-32360 | NONE0 | cups-libs 1:1.6.3-35.el7 fixed in 1:1.6.3-52.el7_9 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2018-4181 | NONE0 | cups-libs 1:1.6.3-35.el7 fixed in 1:1.6.3-43.el7 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-10001 | NONE0 | cups-libs 1:1.6.3-35.el7 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-32324 | NONE0 | cups-libs 1:1.6.3-35.el7 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-58436 | NONE0 | cups-libs 1:1.6.3-35.el7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-12049 | NONE0 | dbus 1:1.10.24-12.el7 fixed in 1:1.10.24-14.el7_8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2020-12049 | NONE0 | dbus-libs 1:1.10.24-12.el7 fixed in 1:1.10.24-14.el7_8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-33294 | NONE0 | elfutils-default-yama-scope 0.172-2.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2016-10254 | NONE0 | elfutils-default-yama-scope 0.172-2.el7 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2016-10255 | NONE0 | elfutils-default-yama-scope 0.172-2.el7 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-7607 | NONE0 | elfutils-default-yama-scope 0.172-2.el7 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-7608 | NONE0 | elfutils-default-yama-scope 0.172-2.el7 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2017-7609 | NONE0 | elfutils-default-yama-scope 0.172-2.el7 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7610 | NONE0 | elfutils-default-yama-scope 0.172-2.el7 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2017-7611 | NONE0 | elfutils-default-yama-scope 0.172-2.el7 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2017-7612 | NONE0 | elfutils-default-yama-scope 0.172-2.el7 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2017-7613 | NONE0 | elfutils-default-yama-scope 0.172-2.el7 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2018-16062 | NONE0 | elfutils-default-yama-scope 0.172-2.el7 fixed in 0.176-2.el7 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2018-16403 | NONE0 | elfutils-default-yama-scope 0.172-2.el7 fixed in 0.176-2.el7 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2018-18310 | NONE0 | elfutils-default-yama-scope 0.172-2.el7 fixed in 0.176-2.el7 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-18521 | NONE0 | elfutils-default-yama-scope 0.172-2.el7 fixed in 0.176-2.el7 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-7150 | NONE0 | elfutils-default-yama-scope 0.172-2.el7 fixed in 0.176-2.el7 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-7664 | NONE0 | elfutils-default-yama-scope 0.172-2.el7 fixed in 0.176-2.el7 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-7665 | NONE0 | elfutils-default-yama-scope 0.172-2.el7 fixed in 0.176-2.el7 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2021-33294 | NONE0 | elfutils-libelf 0.172-2.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2016-10254 | NONE0 | elfutils-libelf 0.172-2.el7 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2016-10255 | NONE0 | elfutils-libelf 0.172-2.el7 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-7607 | NONE0 | elfutils-libelf 0.172-2.el7 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-7608 | NONE0 | elfutils-libelf 0.172-2.el7 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2017-7609 | NONE0 | elfutils-libelf 0.172-2.el7 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7610 | NONE0 | elfutils-libelf 0.172-2.el7 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2017-7611 | NONE0 | elfutils-libelf 0.172-2.el7 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2017-7612 | NONE0 | elfutils-libelf 0.172-2.el7 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2017-7613 | NONE0 | elfutils-libelf 0.172-2.el7 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2018-16062 | NONE0 | elfutils-libelf 0.172-2.el7 fixed in 0.176-2.el7 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2018-16403 | NONE0 | elfutils-libelf 0.172-2.el7 fixed in 0.176-2.el7 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2018-18310 | NONE0 | elfutils-libelf 0.172-2.el7 fixed in 0.176-2.el7 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-18521 | NONE0 | elfutils-libelf 0.172-2.el7 fixed in 0.176-2.el7 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-7150 | NONE0 | elfutils-libelf 0.172-2.el7 fixed in 0.176-2.el7 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-7664 | NONE0 | elfutils-libelf 0.172-2.el7 fixed in 0.176-2.el7 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-7665 | NONE0 | elfutils-libelf 0.172-2.el7 fixed in 0.176-2.el7 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2021-33294 | NONE0 | elfutils-libs 0.172-2.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2016-10254 | NONE0 | elfutils-libs 0.172-2.el7 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2016-10255 | NONE0 | elfutils-libs 0.172-2.el7 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-7607 | NONE0 | elfutils-libs 0.172-2.el7 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-7608 | NONE0 | elfutils-libs 0.172-2.el7 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2017-7609 | NONE0 | elfutils-libs 0.172-2.el7 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7610 | NONE0 | elfutils-libs 0.172-2.el7 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2017-7611 | NONE0 | elfutils-libs 0.172-2.el7 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2017-7612 | NONE0 | elfutils-libs 0.172-2.el7 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2017-7613 | NONE0 | elfutils-libs 0.172-2.el7 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2018-16062 | NONE0 | elfutils-libs 0.172-2.el7 fixed in 0.176-2.el7 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2018-16403 | NONE0 | elfutils-libs 0.172-2.el7 fixed in 0.176-2.el7 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2018-18310 | NONE0 | elfutils-libs 0.172-2.el7 fixed in 0.176-2.el7 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-18521 | NONE0 | elfutils-libs 0.172-2.el7 fixed in 0.176-2.el7 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-7150 | NONE0 | elfutils-libs 0.172-2.el7 fixed in 0.176-2.el7 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-7664 | NONE0 | elfutils-libs 0.172-2.el7 fixed in 0.176-2.el7 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-7665 | NONE0 | elfutils-libs 0.172-2.el7 fixed in 0.176-2.el7 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-52426 | NONE0 | expat 2.1.0-10.el7_3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32776 | NONE0 | expat 2.1.0-10.el7_3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-32777 | NONE0 | expat 2.1.0-10.el7_3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-32778 | NONE0 | expat 2.1.0-10.el7_3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66382 | NONE0 | expat 2.1.0-10.el7_3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48554 | NONE0 | file-libs 5.11-35.el7 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2022-25309 | NONE0 | fribidi 1.0.2-1.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-25310 | NONE0 | fribidi 1.0.2-1.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2017-6312 | NONE0 | gdk-pixbuf2 2.36.12-3.el7 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2017-6314 | NONE0 | gdk-pixbuf2 2.36.12-3.el7 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2015-7555 | NONE0 | giflib 4.1.6-9.el7 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-28506 | NONE0 | giflib 4.1.6-9.el7 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2016-3977 | NONE0 | giflib 4.1.6-9.el7 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-39742 | NONE0 | giflib 4.1.6-9.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-3800 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2017-7244 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-32611 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-32665 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-5504 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-9055 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2021-26927 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2021-3272 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2021-3443 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2021-3467 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2016-9395 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-6851 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-9782 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-18873 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-19139 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2022-40755 | NONE0 | jasper-libs 1.900.1-33.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-26462 | NONE0 | krb5-libs 1.15.1-34.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-43785 | NONE0 | libX11 1.6.5-2.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-43786 | NONE0 | libX11 1.6.5-2.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-15853 | NONE0 | libX11 1.6.5-2.el7 fixed in 1.6.7-2.el7 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-15854 | NONE0 | libX11 1.6.5-2.el7 fixed in 1.6.7-2.el7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-15855 | NONE0 | libX11 1.6.5-2.el7 fixed in 1.6.7-2.el7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-15856 | NONE0 | libX11 1.6.5-2.el7 fixed in 1.6.7-2.el7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-15859 | NONE0 | libX11 1.6.5-2.el7 fixed in 1.6.7-2.el7 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-15861 | NONE0 | libX11 1.6.5-2.el7 fixed in 1.6.7-2.el7 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-15862 | NONE0 | libX11 1.6.5-2.el7 fixed in 1.6.7-2.el7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-15863 | NONE0 | libX11 1.6.5-2.el7 fixed in 1.6.7-2.el7 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-15864 | NONE0 | libX11 1.6.5-2.el7 fixed in 1.6.7-2.el7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-43785 | NONE0 | libX11-common 1.6.5-2.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-43786 | NONE0 | libX11-common 1.6.5-2.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-15853 | NONE0 | libX11-common 1.6.5-2.el7 fixed in 1.6.7-2.el7 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-15854 | NONE0 | libX11-common 1.6.5-2.el7 fixed in 1.6.7-2.el7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-15855 | NONE0 | libX11-common 1.6.5-2.el7 fixed in 1.6.7-2.el7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-15856 | NONE0 | libX11-common 1.6.5-2.el7 fixed in 1.6.7-2.el7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-15859 | NONE0 | libX11-common 1.6.5-2.el7 fixed in 1.6.7-2.el7 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-15861 | NONE0 | libX11-common 1.6.5-2.el7 fixed in 1.6.7-2.el7 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-15862 | NONE0 | libX11-common 1.6.5-2.el7 fixed in 1.6.7-2.el7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-15863 | NONE0 | libX11-common 1.6.5-2.el7 fixed in 1.6.7-2.el7 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-15864 | NONE0 | libX11-common 1.6.5-2.el7 fixed in 1.6.7-2.el7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libblkid 2.23.2-59.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-37600 | NONE0 | libblkid 2.23.2-59.el7 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-27538 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2019-13960 | NONE0 | libjpeg-turbo 1.2.90-6.el7 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libmount 2.23.2-59.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-37600 | NONE0 | libmount 2.23.2-59.el7 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2018-1000654 | NONE0 | libtasn1 4.10-1.el7 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2016-5102 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-0561 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-0562 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-0924 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-22844 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-2867 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2869 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2953 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-3570 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-4645 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-48281 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-0795 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-0796 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-0797 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-0798 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-0799 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-0800 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-0801 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-0802 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-0803 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-0804 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-25433 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-25435 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-26966 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-30086 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-30774 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-30775 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-3164 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-3576 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-61143 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2016-10266 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2016-10267 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2016-10371 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2016-9273 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 3.8% Low-Moderate Risk | Not Applicable |
| CVE-2016-9532 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2017-7593 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2017-7594 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2017-7595 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-18768 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-35521 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2020-35522 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-0908 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-1056 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-2868 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6228 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libuuid 2.23.2-59.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-37600 | NONE0 | libuuid 2.23.2-59.el7 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2016-9318 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2025-9714 | NONE0 | libxml2 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7_9.14 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-34459 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2016-9318 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2025-9714 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7_9.14 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-34459 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-10911 | NONE0 | libxslt 1.1.28-5.el7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-19211 | NONE0 | ncurses 5.9-14.20130511.el7_4 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2018-19211 | NONE0 | ncurses-base 5.9-14.20130511.el7_4 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2018-19211 | NONE0 | ncurses-libs 5.9-14.20130511.el7_4 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | pam 1.1.8-22.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2017-7244 | NONE0 | pcre 8.32-17.el7 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-13837 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42308 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6075 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2021-3421 | NONE0 | rpm-build-libs 4.11.3-35.el7 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-44605 | NONE0 | rpm-build-libs 4.11.3-35.el7 No fix yet | — | Not Applicable |
| CVE-2021-3421 | NONE0 | rpm-libs 4.11.3-35.el7 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-44605 | NONE0 | rpm-libs 4.11.3-35.el7 No fix yet | — | Not Applicable |
| CVE-2021-3421 | NONE0 | rpm-python 4.11.3-35.el7 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-44605 | NONE0 | rpm-python 4.11.3-35.el7 No fix yet | — | Not Applicable |
| CVE-2019-6454 | NONE0 | systemd 219-62.el7 fixed in 219-62.el7_6.5 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2021-3997 | NONE0 | systemd 219-62.el7 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-3821 | NONE0 | systemd 219-62.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-4415 | NONE0 | systemd 219-62.el7 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-45873 | NONE0 | systemd 219-62.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-6454 | NONE0 | systemd-libs 219-62.el7 fixed in 219-62.el7_6.5 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2021-3997 | NONE0 | systemd-libs 219-62.el7 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-3821 | NONE0 | systemd-libs 219-62.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-4415 | NONE0 | systemd-libs 219-62.el7 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-45873 | NONE0 | systemd-libs 219-62.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-41079 | NONE0 | cups-libs 1:1.6.3-35.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-1489 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-17595 | NONE0 | ncurses 5.9-14.20130511.el7_4 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-17595 | NONE0 | ncurses-base 5.9-14.20130511.el7_4 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-17595 | NONE0 | ncurses-libs 5.9-14.20130511.el7_4 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2015-5186 | NONE0 | audit-libs 2.8.4-4.el7 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2024-52615 | NONE0 | avahi-libs 0.6.31-19.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-52616 | NONE0 | avahi-libs 0.6.31-19.el7 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-25219 | NONE0 | bind-license 32:9.9.4-72.el7 No fix yet | 8.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-2795 | NONE0 | bind-license 32:9.9.4-72.el7 fixed in 32:9.11.4-26.P2.el7_9.13 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2026-3592 | NONE0 | bind-license 32:9.9.4-72.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5950 | NONE0 | bind-license 32:9.9.4-72.el7 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2019-6465 | NONE0 | bind-license 32:9.9.4-72.el7 fixed in 32:9.11.4-16.P2.el7 | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2026-34979 | NONE0 | cups-libs 1:1.6.3-35.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-18248 | NONE0 | cups-libs 1:1.6.3-35.el7 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-23865 | NONE0 | freetype 2.8-12.el7_6.1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-16768 | NONE0 | gdk-pixbuf2 2.36.12-3.el7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-15588 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-28153 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-22693 | NONE0 | harfbuzz 1.7.5-2.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-20217 | NONE0 | krb5-libs 1.15.1-34.el7 fixed in 1.15.1-37.el7_7.2 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-13595 | NONE0 | libblkid 2.23.2-59.el7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2021-22876 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 5.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-27779 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2025-9086 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-4873 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6253 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-7168 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-22925 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 4.9% Low-Moderate Risk | Not Applicable |
| CVE-2026-13595 | NONE0 | libmount 2.23.2-59.el7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-66035 | NONE0 | libssh2 1.4.3-12.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6918 | NONE0 | libssh2 1.4.3-12.el7 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2024-12133 | NONE0 | libtasn1 4.10-1.el7 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-8851 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libuuid 2.23.2-59.el7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2015-9019 | NONE0 | libxslt 1.1.28-5.el7 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-13117 | NONE0 | libxslt 1.1.28-5.el7 No fix yet | 6.5% Low-Moderate Risk | Not Applicable |
| CVE-2019-13118 | NONE0 | libxslt 1.1.28-5.el7 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-17594 | NONE0 | ncurses 5.9-14.20130511.el7_4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-17594 | NONE0 | ncurses-base 5.9-14.20130511.el7_4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-17594 | NONE0 | ncurses-libs 5.9-14.20130511.el7_4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-6829 | NONE0 | nss-tools 3.36.0-7.el7_5 fixed in 3.53.1-3.el7_9 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2019-11727 | NONE0 | nss-tools 3.36.0-7.el7_5 fixed in 3.53.1-3.el7_9 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2020-14155 | NONE0 | pcre 8.32-17.el7 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-40217 | NONE0 | python-libs 2.7.5-76.el7 fixed in 2.7.5-94.el7_9 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2018-20852 | NONE0 | python-libs 2.7.5-76.el7 fixed in 2.7.5-88.el7 | 4.0% Low-Moderate Risk | Not Applicable |
| CVE-2021-4189 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2023-27043 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-8088 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-12084 | NONE0 | python-libs 2.7.5-76.el7 fixed in 2.7.5-94.el7_9.2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-12781 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-3276 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-4360 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34743 | NONE0 | xz-libs 5.2.2-1.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-34990 | NONE0 | cups-libs 1:1.6.3-35.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-4516 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42250 | NONE0 | bzip2-libs 1.0.6-13.el7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2014-9620 | NONE0 | file-libs 5.11-35.el7 No fix yet | 4.7% Low-Moderate Risk | Not Applicable |
| CVE-2014-9745 | NONE0 | freetype 2.8-12.el7_6.1 No fix yet | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2015-2695 | NONE0 | krb5-libs 1.15.1-34.el7 No fix yet | 6.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-11850 | NONE0 | krb5-libs 1.15.1-34.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2015-3153 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 7.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-28164 | NONE0 | libpng 2:1.5.13-7.el7_2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-61145 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2015-7995 | NONE0 | libxslt 1.1.28-5.el7 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2015-2808 | NONE0 | nss-tools 3.36.0-7.el7_5 No fix yet | 73.9% Actively Exploited | Not Applicable |
| CVE-2013-1664 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 4.9% Low-Moderate Risk | Not Applicable |
| CVE-2013-1665 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 4.6% Low-Moderate Risk | Not Applicable |
| CVE-2024-0397 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2018-5745 | NONE0 | bind-license 32:9.9.4-72.el7 fixed in 32:9.11.4-16.P2.el7 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2019-13057 | NONE0 | openldap 2.4.44-20.el7 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-20266 | NONE0 | rpm-build-libs 4.11.3-35.el7 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-20266 | NONE0 | rpm-libs 4.11.3-35.el7 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-20266 | NONE0 | rpm-python 4.11.3-35.el7 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2025-4373 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-14017 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | pam 1.1.8-22.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-15282 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0672 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15224 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-5969 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-5969 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-0495 | NONE0 | nss-tools 3.36.0-7.el7_5 fixed in 3.44.0-4.el7 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2020-12400 | NONE0 | nss-tools 3.36.0-7.el7_5 fixed in 3.53.1-3.el7_9 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-12401 | NONE0 | nss-tools 3.36.0-7.el7_5 fixed in 3.53.1-3.el7_9 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2016-4984 | NONE0 | openldap 2.4.44-20.el7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | pam 1.1.8-22.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-3521 | NONE0 | rpm-build-libs 4.11.3-35.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-3521 | NONE0 | rpm-libs 4.11.3-35.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-3521 | NONE0 | rpm-python 4.11.3-35.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-4598 | NONE0 | systemd 219-62.el7 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2018-16888 | NONE0 | systemd 219-62.el7 fixed in 219-67.el7 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-4598 | NONE0 | systemd-libs 219-62.el7 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2018-16888 | NONE0 | systemd-libs 219-62.el7 fixed in 219-67.el7 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2015-0247 | NONE0 | libcom_err 1.42.9-13.el7 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2015-1572 | NONE0 | libcom_err 1.42.9-13.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-11468 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0865 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-1502 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-64505 | NONE0 | libpng 2:1.5.13-7.el7_2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-34757 | NONE0 | libpng 2:1.5.13-7.el7_2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-5068 | NONE0 | mesa-libEGL 18.0.5-4.el7_6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-5068 | NONE0 | mesa-libGL 18.0.5-4.el7_6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-5068 | NONE0 | mesa-libgbm 18.0.5-4.el7_6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-5068 | NONE0 | mesa-libglapi 18.0.5-4.el7_6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-12402 | NONE0 | nss-tools 3.36.0-7.el7_5 fixed in 3.53.1-3.el7_9 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2016-7091 | NONE0 | readline 6.2-10.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25068 | NONE0 | alsa-lib 1.1.6-2.el7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-8624 | NONE0 | bind-license 32:9.9.4-72.el7 fixed in 32:9.11.4-26.P2.el7_9.2 | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-3820 | NONE0 | gtk-update-icon-cache 3.22.30-3.el7 fixed in 3.22.30-5.el7 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-30115 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-6135 | NONE0 | nss-tools 3.36.0-7.el7_5 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2013-7040 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-6069 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-8291 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2014-3146 | NONE0 | python-lxml 3.2.1-4.el7 No fix yet | 6.3% Low-Moderate Risk | Not Applicable |
| CVE-2019-3820 | NONE0 | shared-mime-info 1.8-4.el7 fixed in 1.8-5.el7 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-1484 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2014-3591 | NONE0 | libgcrypt 1.5.3-14.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2020-15719 | NONE0 | openldap 2.4.44-20.el7 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-25260 | NONE0 | elfutils-default-yama-scope 0.172-2.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-25260 | NONE0 | elfutils-libelf 0.172-2.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-25260 | NONE0 | elfutils-libs 0.172-2.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2015-2697 | NONE0 | krb5-libs 1.15.1-34.el7 No fix yet | 4.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-34397 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-41080 | NONE0 | expat 2.1.0-10.el7_3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-3360 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-7039 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0988 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-8284 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 3.9% Low-Moderate Risk | Not Applicable |
| CVE-2021-22924 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 6.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-35252 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2023-28322 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-38546 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 6.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-0989 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0989 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-4032 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-4878 | NONE0 | libssh2 1.4.3-12.el7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-1000030 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-25317 | NONE0 | cups-libs 1:1.6.3-35.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-6199 | NONE0 | gdk-pixbuf2 2.36.12-3.el7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-2602 | NONE0 | libcap 2.22-9.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-2708 | NONE0 | libdb 5.3.21-24.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-2708 | NONE0 | libdb-utils 5.3.21-24.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-41990 | NONE0 | libgcrypt 1.5.3-14.el7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-36084 | NONE0 | libsepol 2.5-10.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-36085 | NONE0 | libsepol 2.5-10.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-36086 | NONE0 | libsepol 2.5-10.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-36087 | NONE0 | libsepol 2.5-10.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-8961 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-9165 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4519 | NONE0 | python-libs 2.7.5-76.el7 fixed in 2.7.5-94.el7_9.4 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-13462 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-2297 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3479 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | systemd 219-62.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-16866 | NONE0 | systemd 219-62.el7 fixed in 219-67.el7 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2016-6349 | NONE0 | systemd 219-62.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-3815 | NONE0 | systemd 219-62.el7 fixed in 219-62.el7_6.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | systemd-libs 219-62.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-16866 | NONE0 | systemd-libs 219-62.el7 fixed in 219-67.el7 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2016-6349 | NONE0 | systemd-libs 219-62.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-3815 | NONE0 | systemd-libs 219-62.el7 fixed in 219-62.el7_6.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-22898 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 4.4% Low-Moderate Risk | Not Applicable |
| CVE-2025-8277 | NONE0 | libssh2 1.4.3-12.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-11731 | NONE0 | libxslt 1.1.28-5.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-1795 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-0992 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0992 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-1485 | NONE0 | glib2 2.56.1-2.el7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-5642 | NONE0 | python-libs 2.7.5-76.el7 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2015-8035 | NONE0 | libxml2 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7.4 | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2015-8035 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 fixed in 2.9.1-6.el7.4 | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-24515 | NONE0 | expat 2.1.0-10.el7_3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-13978 | NONE0 | libtiff 4.0.3-27.el7_3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6170 | NONE0 | libxml2 2.9.1-6.el7_2.3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6170 | NONE0 | libxml2-python 2.9.1-6.el7_2.3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-7407 | NONE0 | libcurl 7.29.0-51.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-20386 | NONE0 | systemd 219-62.el7 fixed in 219-78.el7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-20386 | NONE0 | systemd-libs 219-62.el7 fixed in 219-78.el7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-8991 | NONE0 | device-mapper 7:1.02.149-8.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-8991 | NONE0 | device-mapper-libs 7:1.02.149-8.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2014-3477 | NONE0 | dbus 1:1.10.24-12.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2014-3532 | NONE0 | dbus 1:1.10.24-12.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2014-3533 | NONE0 | dbus 1:1.10.24-12.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2014-3637 | NONE0 | dbus 1:1.10.24-12.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2014-3638 | NONE0 | dbus 1:1.10.24-12.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2014-3639 | NONE0 | dbus 1:1.10.24-12.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2014-3477 | NONE0 | dbus-libs 1:1.10.24-12.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2014-3532 | NONE0 | dbus-libs 1:1.10.24-12.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2014-3533 | NONE0 | dbus-libs 1:1.10.24-12.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2014-3637 | NONE0 | dbus-libs 1:1.10.24-12.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2014-3638 | NONE0 | dbus-libs 1:1.10.24-12.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2014-3639 | NONE0 | dbus-libs 1:1.10.24-12.el7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2014-5351 | NONE0 | krb5-libs 1.15.1-34.el7 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2015-5218 | NONE0 | libblkid 2.23.2-59.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2014-5270 | NONE0 | libgcrypt 1.5.3-14.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2015-5218 | NONE0 | libmount 2.23.2-59.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2015-5218 | NONE0 | libuuid 2.23.2-59.el7 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2014-3636 | NONE0 | dbus 1:1.10.24-12.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2015-0245 | NONE0 | dbus 1:1.10.24-12.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2014-3636 | NONE0 | dbus-libs 1:1.10.24-12.el7 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2015-0245 | NONE0 | dbus-libs 1:1.10.24-12.el7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2018-4700 | NONE0 | cups-libs 1:1.6.3-35.el7 fixed in 1:1.6.3-43.el7 | — | Not Applicable |
| CVE-2026-22020 | NONE0 | java-1.8.0-openjdk 1:1.8.0.212.b04-0.el7_6 No fix yet | — | Not Applicable |
| CVE-2026-22020 | NONE0 | java-1.8.0-openjdk-devel 1:1.8.0.212.b04-0.el7_6 No fix yet | — | Not Applicable |
| CVE-2026-22020 | NONE0 | java-1.8.0-openjdk-headless 1:1.8.0.212.b04-0.el7_6 No fix yet | — | Not Applicable |
| CVE-2026-22020 | NONE0 | libpng 2:1.5.13-7.el7_2 No fix yet | — | Not Applicable |
| GHSA-r7wm-3cxj-wff9 | NONE0 | com.fasterxml.jackson.core:jackson-core 2.9.8 fixed in 2.18.8, 2.21.4, 2.22.1 | — | Not Applicable |
| GHSA-72hv-8253-57qq | NONE0 | com.fasterxml.jackson.core:jackson-core 2.9.8 fixed in 2.21.1, 2.18.6 | — | Not Applicable |
| CVE-2026-33558 | NONE0 | org.apache.kafka:kafka-clients 2.2.0 fixed in 3.9.2, 4.0.1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-10050 | NONE0 | org.eclipse.jetty:jetty-security 9.4.14.v20181114 fixed in 9.4.63, 10.0.31, 11.0.31, 12.0.36, 12.1.10 | — | Not Applicable |
| CVE-2026-6790 | NONE0 | org.eclipse.jetty:jetty-server 9.4.14.v20181114 fixed in 12.0.35, 12.1.9 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-59949 | NONE0 | org.lz4:lz4-java 1.5.0 No fix yet | — | Not Applicable |
| GHSA-673j-qm5f-xpv8 | NONE0 | org.postgresql:postgresql 42.2.5 fixed in 42.3.3 | — | 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.
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.