This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker could cause denial of service via CVE-2023-2650 if the container connects to a malicious server, or potentially achieve code execution via CVE-2026-5121 if on 32-bit architecture. However, CVE-2026-5121 only affects 32-bit systems, so deploying on 64-bit infrastructure eliminates that risk. Frequent monitoring and network segmentation are advised.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2023-2650 | HIGH8.45 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 77.9% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2026-5121 | HIGH7.5 | libarchive 3.3.3-6.el8_10 fixed in 3.3.3-7.el8_10 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42013 | MEDIUM6.97 | gnutls 3.6.16-8.el8_10.4 fixed in 3.6.16-8.el8_10.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM6.97 | gnutls 3.6.16-8.el8_10.4 fixed in 3.6.16-8.el8_10.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-0966 | MEDIUM6.97 | libssh 0.9.6-16.el8_10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-0966 | MEDIUM6.97 | libssh-config 0.9.6-16.el8_10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6100 | MEDIUM6.88 | python3-libs 3.6.8-71.el8_10 fixed in 3.6.8-76.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6100 | MEDIUM6.88 | python3.12-libs 3.12.11-2.el8_10 fixed in 3.12.13-2.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-0938 | MEDIUM6.8 | python3-libs 3.6.8-71.el8_10 fixed in 3.6.8-74.el8_10 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-0938 | MEDIUM6.8 | python3.12-libs 3.12.11-2.el8_10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-35512 | MEDIUM6.63 | dbus-daemon 1:1.12.8-27.el8_10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-35512 | MEDIUM6.63 | dbus-libs 1:1.12.8-27.el8_10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-25724 | MEDIUM6.63 | libarchive 3.3.3-6.el8_10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48864 | MEDIUM6.63 | libsolv 0.7.20-6.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | systemd-libs 239-82.el8_10.8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | systemd-pam 239-82.el8_10.8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13601 | MEDIUM6.54 | glib2 2.56.4-167.el8_10 fixed in 2.56.4-168.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-4209 | MEDIUM6.5 | gnutls 3.6.16-8.el8_10.4 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-1000879 | MEDIUM6.5 | libarchive 3.3.3-6.el8_10 No fix yet | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-1000880 | MEDIUM6.5 | libarchive 3.3.3-6.el8_10 No fix yet | 4.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45186 | MEDIUM6.38 | expat 2.5.0-1.el8_10 fixed in 2.5.0-2.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-29499 | MEDIUM6.38 | glib2 2.56.4-167.el8_10 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-32636 | MEDIUM6.38 | glib2 2.56.4-167.el8_10 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-33846 | MEDIUM6.38 | gnutls 3.6.16-8.el8_10.4 fixed in 3.6.16-8.el8_10.6 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-42009 | MEDIUM6.38 | gnutls 3.6.16-8.el8_10.4 fixed in 3.6.16-8.el8_10.6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-4424 | MEDIUM6.38 | libarchive 3.3.3-6.el8_10 fixed in 3.3.3-7.el8_10 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-41989 | MEDIUM6.38 | libgcrypt 1.8.5-7.el8_6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27135 | MEDIUM6.38 | libnghttp2 1.33.0-6.el8_10.1 fixed in 1.33.0-6.el8_10.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3731 | MEDIUM6.38 | libssh 0.9.6-16.el8_10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3731 | MEDIUM6.38 | libssh-config 0.9.6-16.el8_10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6732 | MEDIUM6.38 | libxml2 2.9.7-21.el8_10.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.38 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-34183 | MEDIUM6.38 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM6.38 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM6.38 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-41409 | MEDIUM6.38 | pcre2 10.32-3.el8_6 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | python3-libs 3.6.8-71.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.38 | python3-libs 3.6.8-71.el8_10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | python3-libs 3.6.8-71.el8_10 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-66418 | MEDIUM6.38 | python3-urllib3 1.24.2-8.el8_10 fixed in 1.24.2-9.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-66471 | MEDIUM6.38 | python3-urllib3 1.24.2-8.el8_10 fixed in 1.24.2-9.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-21441 | MEDIUM6.38 | python3-urllib3 1.24.2-8.el8_10 fixed in 1.24.2-9.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | python3.12-libs 3.12.11-2.el8_10 fixed in 3.12.13-2.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.38 | python3.12-libs 3.12.11-2.el8_10 fixed in 3.12.13-2.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | python3.12-libs 3.12.11-2.el8_10 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-3833 | MEDIUM6.29 | gnutls 3.6.16-8.el8_10.4 fixed in 3.6.16-8.el8_10.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM6.29 | gnutls 3.6.16-8.el8_10.4 fixed in 3.6.16-8.el8_10.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | openssl-libs 1:1.1.1k-14.el8_6 fixed in 1:1.1.1k-15.el8_6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-0235 | MEDIUM6.1 | python3-cloud-what 1.28.44-1.el8_10 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0235 | MEDIUM6.1 | python3-subscription-manager-rhsm 1.28.44-1.el8_10 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0235 | MEDIUM6.1 | python3-syspurpose 1.28.44-1.el8_10 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42012 | MEDIUM6.03 | gnutls 3.6.16-8.el8_10.4 fixed in 3.6.16-8.el8_10.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4786 | MEDIUM6.03 | python3-libs 3.6.8-71.el8_10 fixed in 3.6.8-76.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | python3-libs 3.6.8-71.el8_10 fixed in 3.6.8-73.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | python3-libs 3.6.8-71.el8_10 fixed in 3.6.8-73.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1299 | MEDIUM6.03 | python3-libs 3.6.8-71.el8_10 fixed in 3.6.8-73.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4786 | MEDIUM6.03 | python3.12-libs 3.12.11-2.el8_10 fixed in 3.12.13-2.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | python3.12-libs 3.12.11-2.el8_10 fixed in 3.12.12-3.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | python3.12-libs 3.12.11-2.el8_10 fixed in 3.12.12-3.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1299 | MEDIUM6.03 | python3.12-libs 3.12.11-2.el8_10 fixed in 3.12.12-3.el8_10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-0464 | MEDIUM6 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 3.7% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2025-13836 | MEDIUM6 | python3.12-libs 3.12.11-2.el8_10 fixed in 3.12.12-2.el8_10 | 1.5% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-4878 | MEDIUM5.95 | libcap 2.48-6.el8_9 fixed in 2.48-6.el8_10.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44604 | MEDIUM5.95 | python3-rpm 4.14.3-32.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44604 | MEDIUM5.95 | rpm-build-libs 4.14.3-32.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44604 | MEDIUM5.95 | rpm-libs 4.14.3-32.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-12904 | MEDIUM5.9 | libgcrypt 1.8.5-7.el8_6 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt 1.8.5-7.el8_6 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1 4.13-5.el8_10 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-41996 | MEDIUM5.9 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | openldap 2.4.46-21.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | systemd-libs 239-82.el8_10.8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | systemd-pam 239-82.el8_10.8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.61 | gnutls 3.6.16-8.el8_10.4 fixed in 3.6.16-8.el8_10.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5915 | MEDIUM5.61 | libarchive 3.3.3-6.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5918 | MEDIUM5.61 | libarchive 3.3.3-6.el8_10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | openssl-libs 1:1.1.1k-14.el8_6 fixed in 1:1.1.1k-14.el8_10 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4741 | MEDIUM5.6 | openssl-libs 1:1.1.1k-14.el8_6 fixed in 1:1.1.1k-16.el8_6 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14512 | MEDIUM5.52 | glib2 2.56.4-167.el8_10 fixed in 2.56.4-169.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc 2.28-251.el8_10.25 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | glibc 2.28-251.el8_10.25 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc-common 2.28-251.el8_10.25 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | glibc-common 2.28-251.el8_10.25 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | glibc-minimal-langpack 2.28-251.el8_10.25 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | glibc-minimal-langpack 2.28-251.el8_10.25 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4426 | MEDIUM5.52 | libarchive 3.3.3-6.el8_10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-9149 | MEDIUM5.52 | libsolv 0.7.20-6.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5351 | MEDIUM5.52 | libssh 0.9.6-16.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-5351 | MEDIUM5.52 | libssh-config 0.9.6-16.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-45322 | MEDIUM5.52 | libxml2 2.9.7-21.el8_10.3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2019-14250 | MEDIUM5.5 | libatomic 8.5.0-28.el8_10 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-14250 | MEDIUM5.5 | libgcc 8.5.0-28.el8_10 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-14250 | MEDIUM5.5 | libgomp 8.5.0-28.el8_10 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-14250 | MEDIUM5.5 | libstdc++ 8.5.0-28.el8_10 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-1000654 | MEDIUM5.5 | libtasn1 4.13-5.el8_10 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-34459 | MEDIUM5.5 | libxml2 2.9.7-21.el8_10.3 fixed in 2.9.7-21.el8_10.5 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3997 | MEDIUM5.5 | systemd-libs 239-82.el8_10.8 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3997 | MEDIUM5.5 | systemd-pam 239-82.el8_10.8 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-0964 | MEDIUM5.35 | libssh 0.9.6-16.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0964 | MEDIUM5.35 | libssh-config 0.9.6-16.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM5.35 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-0466 | MEDIUM5.3 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0465 | MEDIUM5.3 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-59375 | MEDIUM5.3 | python3.12-libs 3.12.11-2.el8_10 fixed in 3.12.13-2.el8_10 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-1757 | MEDIUM5.27 | libxml2 2.9.7-21.el8_10.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid 2.32.1-46.el8 fixed in 2.32.1-48.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libfdisk 2.32.1-46.el8 fixed in 2.32.1-48.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount 2.32.1-46.el8 fixed in 2.32.1-48.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libsmartcols 2.32.1-46.el8 fixed in 2.32.1-48.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid 2.32.1-46.el8 fixed in 2.32.1-48.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | python3-libs 3.6.8-71.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | python3.12-libs 3.12.11-2.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5713 | MEDIUM5.1 | python3-libs 3.6.8-71.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5713 | MEDIUM5.1 | python3.12-libs 3.12.11-2.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | MEDIUM5.02 | expat 2.5.0-1.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc 2.28-251.el8_10.25 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | glibc 2.28-251.el8_10.25 fixed in 2.28-251.el8_10.31 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc-common 2.28-251.el8_10.25 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | glibc-common 2.28-251.el8_10.25 fixed in 2.28-251.el8_10.31 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | glibc-minimal-langpack 2.28-251.el8_10.25 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | glibc-minimal-langpack 2.28-251.el8_10.25 fixed in 2.28-251.el8_10.31 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM5.02 | krb5-libs 1.18.2-32.el8_10 fixed in 1.18.2-34.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | krb5-libs 1.18.2-32.el8_10 fixed in 1.18.2-34.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0990 | MEDIUM5.02 | libxml2 2.9.7-21.el8_10.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.02 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-15468 | MEDIUM5.02 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.02 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-2511 | MEDIUM4.81 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 54.0% Actively Exploited | Directly Exposed |
| CVE-2025-5916 | MEDIUM4.76 | libarchive 3.3.3-6.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-9077 | MEDIUM4.68 | binutils 2.30-127.el8_10 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2021-45078 | MEDIUM4.68 | binutils 2.30-127.el8_10 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3927 | MEDIUM4.68 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3974 | MEDIUM4.68 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1619 | MEDIUM4.68 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1720 | MEDIUM4.68 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2124 | MEDIUM4.68 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2125 | MEDIUM4.68 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2126 | MEDIUM4.68 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2129 | MEDIUM4.68 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2175 | MEDIUM4.68 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2182 | MEDIUM4.68 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2183 | MEDIUM4.68 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2206 | MEDIUM4.68 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2207 | MEDIUM4.68 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2210 | MEDIUM4.68 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2284 | MEDIUM4.68 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2285 | MEDIUM4.68 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2286 | MEDIUM4.68 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2343 | MEDIUM4.68 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2344 | MEDIUM4.68 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-32776 | MEDIUM4.67 | expat 2.5.0-1.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | MEDIUM4.67 | expat 2.5.0-1.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | MEDIUM4.67 | expat 2.5.0-1.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | expat 2.5.0-1.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-32611 | MEDIUM4.67 | glib2 2.56.4-167.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-32665 | MEDIUM4.67 | glib2 2.56.4-167.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-60753 | MEDIUM4.67 | libarchive 3.3.3-6.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5745 | MEDIUM4.67 | libarchive 3.3.3-6.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1632 | MEDIUM4.67 | libarchive 3.3.3-6.el8_10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libatomic 8.5.0-28.el8_10 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc 8.5.0-28.el8_10 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgomp 8.5.0-28.el8_10 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-24056 | MEDIUM4.67 | libpkgconf 1.4.2-1.el8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0967 | MEDIUM4.67 | libssh 0.9.6-16.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0967 | MEDIUM4.67 | libssh-config 0.9.6-16.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libstdc++ 8.5.0-28.el8_10 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-9714 | MEDIUM4.67 | libxml2 2.9.7-21.el8_10.3 fixed in 2.9.7-21.el8_10.4 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15469 | MEDIUM4.67 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM4.67 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM4.67 | python3-libs 3.6.8-71.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42308 | MEDIUM4.67 | python3-libs 3.6.8-71.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6075 | MEDIUM4.67 | python3-libs 3.6.8-71.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM4.67 | python3.12-libs 3.12.11-2.el8_10 fixed in 3.12.13-2.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42308 | MEDIUM4.67 | python3.12-libs 3.12.11-2.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6075 | MEDIUM4.67 | python3.12-libs 3.12.11-2.el8_10 fixed in 3.12.13-2.el8_10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-0232 | MEDIUM4.67 | sqlite-libs 3.26.0-20.el8_10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib 1.2.11-25.el8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1489 | MEDIUM4.59 | glib2 2.56.4-167.el8_10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-12697 | MEDIUM4.5 | binutils 2.30-127.el8_10 No fix yet | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2018-12698 | MEDIUM4.5 | binutils 2.30-127.el8_10 No fix yet | 5.3% Low-Moderate Risk | Post-Exploit |
| CVE-2018-12934 | MEDIUM4.5 | binutils 2.30-127.el8_10 No fix yet | 3.3% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20657 | MEDIUM4.5 | binutils 2.30-127.el8_10 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20657 | MEDIUM4.5 | cpp 8.5.0-28.el8_10 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20657 | MEDIUM4.5 | gcc 8.5.0-28.el8_10 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20657 | MEDIUM4.5 | gcc-c++ 8.5.0-28.el8_10 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2020-25645 | MEDIUM4.5 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0045 | MEDIUM4.5 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20657 | MEDIUM4.5 | libstdc++-devel 8.5.0-28.el8_10 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9674 | MEDIUM4.5 | platform-python 3.6.8-71.el8_10 No fix yet | 5.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-7592 | MEDIUM4.5 | platform-python 3.6.8-71.el8_10 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-13836 | MEDIUM4.5 | python3.12 3.12.11-2.el8_10 fixed in 3.12.12-2.el8_10 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-7592 | MEDIUM4.5 | python3.12 3.12.11-2.el8_10 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9923 | MEDIUM4.5 | tar 2:1.30-11.el8_10 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20786 | MEDIUM4.5 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-3705 | MEDIUM4.5 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5344 | MEDIUM4.5 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-0915 | MEDIUM4.5 | glibc 2.28-251.el8_10.25 fixed in 2.28-251.el8_10.31 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc 2.28-251.el8_10.25 fixed in 2.28-251.el8_10.37 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | glibc-common 2.28-251.el8_10.25 fixed in 2.28-251.el8_10.31 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-common 2.28-251.el8_10.25 fixed in 2.28-251.el8_10.37 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | glibc-minimal-langpack 2.28-251.el8_10.25 fixed in 2.28-251.el8_10.31 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | glibc-minimal-langpack 2.28-251.el8_10.25 fixed in 2.28-251.el8_10.37 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14831 | MEDIUM4.5 | gnutls 3.6.16-8.el8_10.4 fixed in 3.6.16-8.el8_10.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM4.5 | gnutls 3.6.16-8.el8_10.4 fixed in 3.6.16-8.el8_10.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-12084 | MEDIUM4.5 | python3-libs 3.6.8-71.el8_10 fixed in 3.6.8-72.el8_10 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | python3-libs 3.6.8-71.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | python3-libs 3.6.8-71.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-12084 | MEDIUM4.5 | python3.12-libs 3.12.11-2.el8_10 fixed in 3.12.12-1.el8_10 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | python3.12-libs 3.12.11-2.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | python3.12-libs 3.12.11-2.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | xz-libs 5.2.4-4.el8_6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23395 | MEDIUM4.49 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-7264 | MEDIUM4.48 | curl 7.61.1-34.el8_10.8 No fix yet | 16.2% High Exploitation Risk | Post-Exploit |
| CVE-2024-7264 | MEDIUM4.48 | libcurl 7.61.1-34.el8_10.8 No fix yet | 16.2% High Exploitation Risk | Post-Exploit |
| CVE-2025-4516 | MEDIUM4.33 | python3-libs 3.6.8-71.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4516 | MEDIUM4.33 | python3.12-libs 3.12.11-2.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-20839 | MEDIUM4.3 | systemd-libs 239-82.el8_10.8 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20839 | MEDIUM4.3 | systemd-pam 239-82.el8_10.8 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2025-10263 | MEDIUM4.28 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-4166 | MEDIUM4.26 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2287 | MEDIUM4.26 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42250 | MEDIUM4.25 | bzip2-libs 1.0.6-28.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc 2.28-251.el8_10.25 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc 2.28-251.el8_10.25 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-common 2.28-251.el8_10.25 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc-common 2.28-251.el8_10.25 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | glibc-minimal-langpack 2.28-251.el8_10.25 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | glibc-minimal-langpack 2.28-251.el8_10.25 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | krb5-libs 1.18.2-32.el8_10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5917 | MEDIUM4.25 | libarchive 3.3.3-6.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM4.25 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-0397 | MEDIUM4.25 | python3-libs 3.6.8-71.el8_10 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-0397 | MEDIUM4.25 | python3.12-libs 3.12.11-2.el8_10 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-1665 | MEDIUM4.18 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31788 | MEDIUM4.18 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-34982 | MEDIUM4.18 | vim-minimal 2:8.0.1763-21.el8_10 fixed in 2:8.0.1763-22.el8_10.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-52859 | MEDIUM4.18 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | curl 7.61.1-34.el8_10.8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl 7.61.1-34.el8_10.8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | MEDIUM4.13 | platform-python 3.6.8-71.el8_10 fixed in 3.6.8-76.el8_10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | MEDIUM4.13 | python3.12 3.12.11-2.el8_10 fixed in 3.12.13-2.el8_10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3534 | MEDIUM4.08 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-0938 | MEDIUM4.08 | platform-python 3.6.8-71.el8_10 fixed in 3.6.8-74.el8_10 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0938 | MEDIUM4.08 | python3.12 3.12.11-2.el8_10 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-54411 | MEDIUM4.08 | pam 1.3.1-38.el8_10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | MEDIUM4.08 | python3-libs 3.6.8-71.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.08 | python3-libs 3.6.8-71.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | MEDIUM4.08 | python3.12-libs 3.12.11-2.el8_10 fixed in 3.12.13-2.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.08 | python3.12-libs 3.12.11-2.el8_10 fixed in 3.12.13-2.el8_10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libblkid 2.32.1-46.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libfdisk 2.32.1-46.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount 2.32.1-46.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols 2.32.1-46.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8114 | MEDIUM4 | libssh 0.9.6-16.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8114 | MEDIUM4 | libssh-config 0.9.6-16.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid 2.32.1-46.el8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-24032 | MEDIUM4 | libzstd 1.4.4-1.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4598 | MEDIUM4 | systemd-libs 239-82.el8_10.8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4598 | MEDIUM4 | systemd-pam 239-82.el8_10.8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2018-1000876 | LOW3.98 | binutils 2.30-127.el8_10 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils 2.30-127.el8_10 fixed in 2.30-128.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils 2.30-127.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils 2.30-127.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-44840 | LOW3.98 | binutils 2.30-127.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2020-35512 | LOW3.98 | dbus-tools 1:1.12.8-27.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | gcc-toolset-14-binutils 2.41-4.el8_10 fixed in 2.41-4.el8_10.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21927 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38000 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31488 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46189 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46331 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-38166 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-46999 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47012 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47017 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47103 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2021-47194 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47251 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47254 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47506 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47565 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-20566 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-3424 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48637 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48686 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48744 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48778 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48783 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48787 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48788 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48789 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48796 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48805 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48834 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48837 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48848 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48913 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48943 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48950 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48951 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48990 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48991 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49006 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49014 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49017 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49022 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49029 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49205 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49377 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49384 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49410 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49455 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49471 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49478 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49508 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49548 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49581 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49612 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49720 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49779 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49789 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49826 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49840 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49842 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49892 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49900 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49921 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49990 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50021 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50051 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50168 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50179 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50220 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50241 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50305 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50320 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50328 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50329 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50401 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50411 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50419 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50422 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50552 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50630 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-3640 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-52482 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52664 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52741 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52760 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52854 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52885 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52906 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52921 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52927 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52988 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53019 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53037 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53052 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53053 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53065 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53075 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53111 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53116 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53123 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53145 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53184 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53235 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53252 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53282 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53285 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53286 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53338 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53340 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53395 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53427 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53432 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53446 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53454 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53473 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53484 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53487 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53500 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53506 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53515 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53516 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53543 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53560 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53587 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53619 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53626 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53676 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53680 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-0562 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-26598 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26689 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26930 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27008 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-35791 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35911 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-39494 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-40956 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41069 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41087 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42148 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-42159 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42271 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42280 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42285 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44932 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44934 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44964 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44967 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44974 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-44977 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-44987 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-44998 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46673 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46713 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46725 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46738 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46744 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46746 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46759 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46798 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46800 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46830 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46859 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46871 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47697 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-47698 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-47701 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47718 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47727 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47745 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-47748 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49882 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49883 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49884 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49889 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49930 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49950 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49960 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49991 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49996 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50007 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50055 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50063 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50067 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50073 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50074 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50125 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50143 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50150 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50186 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50203 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50209 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50262 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50267 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50274 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50282 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53057 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53103 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53156 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53168 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53173 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53179 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53208 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53237 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53239 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-54456 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56551 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56570 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56600 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56601 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56602 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56603 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56604 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56605 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56606 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56614 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-56615 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-56616 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56631 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-56633 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-56640 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56642 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56658 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56765 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57798 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57849 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58072 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58240 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21671 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21692 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-21704 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-21772 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21786 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21791 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21855 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21969 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23133 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23142 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37789 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37798 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37819 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37823 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37839 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-37861 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-37882 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37885 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-37913 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37923 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38117 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38118 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38146 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38157 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38198 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38201 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38212 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38245 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38280 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38323 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38346 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38369 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38375 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38443 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38494 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38574 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38584 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38593 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38618 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38676 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-38729 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39689 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39691 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39790 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39797 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39810 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39824 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39860 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39862 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39863 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39866 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-39880 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39911 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39945 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39967 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40149 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71068 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71089 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22980 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23078 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23208 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23216 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23223 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23447 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23448 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31399 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31452 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31455 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31485 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31493 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31500 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31527 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31583 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31686 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31688 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31729 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31759 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31776 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43049 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43120 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43150 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43328 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43440 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46004 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46047 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46180 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46234 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-4439 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47014 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47196 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47198 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47222 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47239 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47247 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47261 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47303 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47342 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47404 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47427 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47483 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47496 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47517 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47536 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47566 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47576 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47600 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47616 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48658 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48662 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48672 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48694 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48702 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48732 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48801 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49888 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49907 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49917 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49975 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50071 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50252 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50432 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52452 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52468 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52474 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52475 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52614 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52621 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52624 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-52642 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52731 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52818 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52851 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52867 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52987 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53000 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53142 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53153 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53179 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53215 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53307 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53596 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53604 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54207 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26589 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26742 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26782 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26882 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2024-26883 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-26928 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-27075 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-27398 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2024-35886 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-35979 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36012 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36015 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-36880 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-38556 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-38588 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-39479 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-39480 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-40940 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41000 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-42136 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46845 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53214 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-56708 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57917 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37928 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-38239 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38563 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-38565 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39835 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39913 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39957 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39958 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71082 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23089 | LOW3.98 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-39881 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-0351 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-2345 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-2522 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2819 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2845 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2849 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2946 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3037 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3234 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3235 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3256 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3296 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-3352 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-4292 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-0049 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-0054 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-0288 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-0433 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-0512 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-1127 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-2610 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-4733 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-4734 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4735 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4738 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4750 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-4751 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4752 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4781 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-5535 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-22667 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1215 | LOW3.98 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2018-17794 | LOW3.9 | binutils 2.30-127.el8_10 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3826 | LOW3.9 | binutils 2.30-127.el8_10 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3178 | LOW3.9 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2024-47692 | LOW3.9 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2021-38199 | LOW3.9 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils 2.30-127.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils 2.30-127.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils 2.30-127.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils 2.30-127.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-6176 | LOW3.82 | brotli 1.0.6-3.el8 fixed in 1.0.6-4.el8_10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | curl 7.61.1-34.el8_10.8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | curl 7.61.1-34.el8_10.8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-53827 | LOW3.82 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50083 | LOW3.82 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2024-57791 | LOW3.82 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl 7.61.1-34.el8_10.8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl 7.61.1-34.el8_10.8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3644 | LOW3.82 | platform-python 3.6.8-71.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW3.82 | platform-python 3.6.8-71.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW3.82 | platform-python 3.6.8-71.el8_10 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-3644 | LOW3.82 | python3.12 3.12.11-2.el8_10 fixed in 3.12.13-2.el8_10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW3.82 | python3.12 3.12.11-2.el8_10 fixed in 3.12.13-2.el8_10 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW3.82 | python3.12 3.12.11-2.el8_10 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-26269 | LOW3.82 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11468 | LOW3.82 | python3-libs 3.6.8-71.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0865 | LOW3.82 | python3-libs 3.6.8-71.el8_10 fixed in 3.6.8-73.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | python3-libs 3.6.8-71.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | LOW3.82 | python3.12-libs 3.12.11-2.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0865 | LOW3.82 | python3.12-libs 3.12.11-2.el8_10 fixed in 3.12.12-3.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | python3.12-libs 3.12.11-2.el8_10 fixed in 3.12.13-2.el8_10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-8905 | LOW3.74 | file-libs 5.33-27.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-8906 | LOW3.74 | file-libs 5.33-27.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43078 | LOW3.72 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-25749 | LOW3.72 | vim-minimal 2:8.0.1763-21.el8_10 fixed in 2:8.0.1763-22.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41411 | LOW3.72 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2020-35494 | LOW3.66 | binutils 2.30-127.el8_10 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-48748 | LOW3.66 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-9358 | LOW3.65 | python3-cloud-what 1.28.44-1.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6069 | LOW3.65 | python3-libs 3.6.8-71.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-8291 | LOW3.65 | python3-libs 3.6.8-71.el8_10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-9358 | LOW3.65 | python3-subscription-manager-rhsm 1.28.44-1.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9358 | LOW3.65 | python3-syspurpose 1.28.44-1.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6069 | LOW3.65 | python3.12-libs 3.12.11-2.el8_10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-8291 | LOW3.65 | python3.12-libs 3.12.11-2.el8_10 fixed in 3.12.12-1.el8_10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-25584 | LOW3.62 | binutils 2.30-127.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-4156 | LOW3.62 | gawk 4.2.1-4.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-46033 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2020-36791 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47138 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47219 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47277 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48827 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49094 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49407 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49416 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49503 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49518 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49556 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49687 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49696 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49740 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49865 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49870 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49883 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49948 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49961 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49970 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50103 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50366 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50394 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50490 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50551 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53024 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53034 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53057 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53117 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53259 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53272 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53321 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53333 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53600 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53659 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53668 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35963 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35965 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35966 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-35967 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36013 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-38635 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46722 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46723 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46724 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46743 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49860 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49928 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50033 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50035 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50115 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50278 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50279 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-52332 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53099 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53174 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53216 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56558 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56663 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57929 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57982 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58013 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58014 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21762 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21920 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21993 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22104 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22121 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37749 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37785 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38004 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38103 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38111 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38249 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38320 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38342 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38445 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38680 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39853 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39891 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39901 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71093 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23076 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23099 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23315 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23318 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23388 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31568 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31614 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31778 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43040 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43052 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43056 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43281 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43427 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43449 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43450 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43453 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46120 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46135 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-46150 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46191 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46209 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46259 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-47094 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47191 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47226 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47255 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48714 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49623 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-50497 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52519 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52697 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53265 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53357 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46774 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49861 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57838 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21719 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38502 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38728 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71133 | LOW3.62 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4786 | LOW3.62 | platform-python 3.6.8-71.el8_10 fixed in 3.6.8-76.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW3.62 | platform-python 3.6.8-71.el8_10 fixed in 3.6.8-73.el8_10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW3.62 | platform-python 3.6.8-71.el8_10 fixed in 3.6.8-73.el8_10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1299 | LOW3.62 | platform-python 3.6.8-71.el8_10 fixed in 3.6.8-73.el8_10 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-4786 | LOW3.62 | python3.12 3.12.11-2.el8_10 fixed in 3.12.13-2.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW3.62 | python3.12 3.12.11-2.el8_10 fixed in 3.12.12-3.el8_10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW3.62 | python3.12 3.12.11-2.el8_10 fixed in 3.12.12-3.el8_10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1299 | LOW3.62 | python3.12 3.12.11-2.el8_10 fixed in 3.12.12-3.el8_10 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2005-2541 | LOW3.6 | tar 2:1.30-11.el8_10 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gnupg2 2.2.20-3.el8_6 fixed in 2.2.20-4.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31419 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31663 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43198 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-45984 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46054 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46090 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46116 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46117 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46145 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46227 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46319 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46330 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-40490 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47280 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-45885 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48790 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48858 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48988 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49667 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49919 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50082 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-1077 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52935 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52974 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52983 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53833 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38561 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43882 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50036 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50106 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56664 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56672 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-21702 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-21726 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21761 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37915 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38102 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38107 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38108 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40259 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23050 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23454 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31586 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31694 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43050 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43116 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43233 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43304 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43334 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43339 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43491 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43493 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-45840 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45856 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45861 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45892 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45894 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45899 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45912 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45942 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45970 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46043 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-46052 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-46069 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46084 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46119 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-46132 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46133 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-46139 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46149 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46174 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46266 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-46275 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46294 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46306 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-46324 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53622 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23054 | LOW3.57 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-44604 | LOW3.57 | rpm 4.14.3-32.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-46483 | LOW3.57 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-1484 | LOW3.57 | glib2 2.56.4-167.el8_10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | LOW3.54 | binutils 2.30-127.el8_10 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-11053 | LOW3.54 | curl 7.61.1-34.el8_10.8 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | gdb-gdbserver 8.2-20.el8 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3714 | LOW3.54 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19076 | LOW3.54 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19080 | LOW3.54 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19081 | LOW3.54 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 3.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-11053 | LOW3.54 | libcurl 7.61.1-34.el8_10.8 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-1121 | LOW3.54 | procps-ng 3.3.15-14.el8 No fix yet | 4.2% Low-Moderate Risk | Post-Exploit |
| CVE-2020-20703 | LOW3.53 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-13034 | LOW3.47 | curl 7.61.1-34.el8_10.8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | curl 7.61.1-34.el8_10.8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-40345 | LOW3.47 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68346 | LOW3.47 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-13034 | LOW3.47 | libcurl 7.61.1-34.el8_10.8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl 7.61.1-34.el8_10.8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-28972 | LOW3.42 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2021-34981 | LOW3.42 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49388 | LOW3.42 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49524 | LOW3.42 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52975 | LOW3.42 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54110 | LOW3.42 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53095 | LOW3.42 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57795 | LOW3.42 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21714 | LOW3.42 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21731 | LOW3.42 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40257 | LOW3.42 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-3159 | LOW3.42 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52447 | LOW3.42 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26828 | LOW3.42 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-25260 | LOW3.4 | elfutils-libelf 0.190-2.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-25260 | LOW3.4 | elfutils-libs 0.190-2.el8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | glibc 2.28-251.el8_10.25 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | glibc-common 2.28-251.el8_10.25 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | glibc-minimal-langpack 2.28-251.el8_10.25 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9820 | LOW3.4 | gnutls 3.6.16-8.el8_10.4 fixed in 3.6.16-8.el8_10.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57970 | LOW3.4 | libarchive 3.3.3-6.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW3.4 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50783 | LOW3.37 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50851 | LOW3.37 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53729 | LOW3.37 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54168 | LOW3.37 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-0607 | LOW3.37 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40018 | LOW3.37 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40261 | LOW3.37 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31589 | LOW3.37 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-45991 | LOW3.37 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-28419 | LOW3.37 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-1170 | LOW3.37 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-1175 | LOW3.37 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils 2.30-127.el8_10 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | curl 7.61.1-34.el8_10.8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | curl 7.61.1-34.el8_10.8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | curl 7.61.1-34.el8_10.8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | curl 7.61.1-34.el8_10.8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-4437 | LOW3.31 | glibc-devel 2.28-251.el8_10.25 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW3.31 | glibc-devel 2.28-251.el8_10.25 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-4437 | LOW3.31 | glibc-headers 2.28-251.el8_10.25 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW3.31 | glibc-headers 2.28-251.el8_10.25 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-68284 | LOW3.31 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2020-3702 | LOW3.31 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-28711 | LOW3.31 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-28712 | LOW3.31 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-28713 | LOW3.31 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-50821 | LOW3.31 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53785 | LOW3.31 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54094 | LOW3.31 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54292 | LOW3.31 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36968 | LOW3.31 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47693 | LOW3.31 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2024-53135 | LOW3.31 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39969 | LOW3.31 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68380 | LOW3.31 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23179 | LOW3.31 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31470 | LOW3.31 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31588 | LOW3.31 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43239 | LOW3.31 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-0564 | LOW3.31 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl 7.61.1-34.el8_10.8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl 7.61.1-34.el8_10.8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl 7.61.1-34.el8_10.8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl 7.61.1-34.el8_10.8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-33056 | LOW3.31 | tar 2:1.30-11.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2018-20623 | LOW3.3 | binutils 2.30-127.el8_10 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20671 | LOW3.3 | binutils 2.30-127.el8_10 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-12641 | LOW3.3 | binutils 2.30-127.el8_10 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2018-17360 | LOW3.3 | binutils 2.30-127.el8_10 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2018-17985 | LOW3.3 | binutils 2.30-127.el8_10 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2018-18309 | LOW3.3 | binutils 2.30-127.el8_10 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2018-18484 | LOW3.3 | binutils 2.30-127.el8_10 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2018-18605 | LOW3.3 | binutils 2.30-127.el8_10 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2018-18606 | LOW3.3 | binutils 2.30-127.el8_10 No fix yet | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2018-18607 | LOW3.3 | binutils 2.30-127.el8_10 No fix yet | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2018-18700 | LOW3.3 | binutils 2.30-127.el8_10 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2018-18701 | LOW3.3 | binutils 2.30-127.el8_10 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2018-19932 | LOW3.3 | binutils 2.30-127.el8_10 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20002 | LOW3.3 | binutils 2.30-127.el8_10 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20651 | LOW3.3 | binutils 2.30-127.el8_10 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils 2.30-127.el8_10 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6872 | LOW3.3 | binutils 2.30-127.el8_10 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2019-12972 | LOW3.3 | binutils 2.30-127.el8_10 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-14250 | LOW3.3 | binutils 2.30-127.el8_10 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9071 | LOW3.3 | binutils 2.30-127.el8_10 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2020-35493 | LOW3.3 | binutils 2.30-127.el8_10 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2020-35495 | LOW3.3 | binutils 2.30-127.el8_10 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2020-35496 | LOW3.3 | binutils 2.30-127.el8_10 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2020-35507 | LOW3.3 | binutils 2.30-127.el8_10 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-14250 | LOW3.3 | cpp 8.5.0-28.el8_10 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2019-14250 | LOW3.3 | gcc 8.5.0-28.el8_10 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2019-14250 | LOW3.3 | gcc-c++ 8.5.0-28.el8_10 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-21760 | LOW3.3 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 6.9% Low-Moderate Risk | Post-Exploit |
| CVE-2018-7273 | LOW3.3 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-47241 | LOW3.3 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2021-47259 | LOW3.3 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-47295 | LOW3.3 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2019-14250 | LOW3.3 | libstdc++-devel 8.5.0-28.el8_10 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2208 | LOW3.3 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-47685 | LOW3.28 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2021-47634 | LOW3.26 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-20154 | LOW3.26 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49291 | LOW3.26 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49493 | LOW3.26 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50880 | LOW3.26 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54146 | LOW3.26 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54156 | LOW3.26 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54200 | LOW3.26 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21700 | LOW3.26 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40074 | LOW3.26 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40309 | LOW3.26 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40321 | LOW3.26 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68371 | LOW3.26 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23178 | LOW3.26 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23450 | LOW3.26 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-23456 | LOW3.26 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31516 | LOW3.26 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43070 | LOW3.26 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52886 | LOW3.26 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2020-10135 | LOW3.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3805 | LOW3.21 | curl 7.61.1-34.el8_10.8 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-38544 | LOW3.21 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-42161 | LOW3.21 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57893 | LOW3.21 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40000 | LOW3.21 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31504 | LOW3.21 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31631 | LOW3.21 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3805 | LOW3.21 | libcurl 7.61.1-34.el8_10.8 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-5958 | LOW3.21 | sed 4.5-5.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-9086 | LOW3.18 | curl 7.61.1-34.el8_10.8 fixed in 7.61.1-34.el8_10.9 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-9086 | LOW3.18 | libcurl 7.61.1-34.el8_10.8 fixed in 7.61.1-34.el8_10.9 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-59375 | LOW3.18 | python3.12 3.12.11-2.el8_10 fixed in 3.12.13-2.el8_10 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27534 | LOW3.17 | curl 7.61.1-34.el8_10.8 No fix yet | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27534 | LOW3.17 | libcurl 7.61.1-34.el8_10.8 No fix yet | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-50764 | LOW3.16 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50838 | LOW3.16 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54081 | LOW3.16 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54311 | LOW3.16 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50251 | LOW3.16 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-40048 | LOW3.16 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40146 | LOW3.16 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71066 | LOW3.16 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23253 | LOW3.16 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-41080 | LOW3.15 | expat 2.5.0-1.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-3360 | LOW3.15 | glib2 2.56.4-167.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-7039 | LOW3.15 | glib2 2.56.4-167.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0988 | LOW3.15 | glib2 2.56.4-167.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3832 | LOW3.15 | gnutls 3.6.16-8.el8_10.4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5419 | LOW3.15 | gnutls 3.6.16-8.el8_10.4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0989 | LOW3.15 | libxml2 2.9.7-21.el8_10.3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.11 | binutils 2.30-127.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50717 | LOW3.11 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49078 | LOW3.11 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53788 | LOW3.11 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53802 | LOW3.11 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53808 | LOW3.11 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53840 | LOW3.11 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53850 | LOW3.11 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40019 | LOW3.11 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-40071 | LOW3.11 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40080 | LOW3.11 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40190 | LOW3.11 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40355 | LOW3.11 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68245 | LOW3.11 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68764 | LOW3.11 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68815 | LOW3.11 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68819 | LOW3.11 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31449 | LOW3.11 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31464 | LOW3.11 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31505 | LOW3.11 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31511 | LOW3.11 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31513 | LOW3.11 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31570 | LOW3.11 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31700 | LOW3.11 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31708 | LOW3.11 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43134 | LOW3.11 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43321 | LOW3.11 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-47313 | LOW3.11 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.11 | platform-python 3.6.8-71.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-50181 | LOW3.11 | python3-pip-wheel 9.0.3-24.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-50182 | LOW3.11 | python3-pip-wheel 9.0.3-24.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.11 | python3.12 3.12.11-2.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-50181 | LOW3.11 | python3.12-pip-wheel 23.2.1-4.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-50182 | LOW3.11 | python3.12-pip-wheel 23.2.1-4.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.32.1-46.el8 fixed in 2.32.1-48.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2020-27171 | LOW3.06 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2021-47308 | LOW3.06 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-49053 | LOW3.06 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49129 | LOW3.06 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49385 | LOW3.06 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49465 | LOW3.06 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31649 | LOW3.06 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-52481 | LOW3.06 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-5713 | LOW3.06 | platform-python 3.6.8-71.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5713 | LOW3.06 | python3.12 3.12.11-2.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-4878 | LOW3.06 | libssh 0.9.6-16.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4878 | LOW3.06 | libssh-config 0.9.6-16.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | LOW3.01 | glibc-devel 2.28-251.el8_10.25 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-15281 | LOW3.01 | glibc-devel 2.28-251.el8_10.25 fixed in 2.28-251.el8_10.31 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5435 | LOW3.01 | glibc-headers 2.28-251.el8_10.25 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-15281 | LOW3.01 | glibc-headers 2.28-251.el8_10.25 fixed in 2.28-251.el8_10.31 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2020-28097 | LOW3.01 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-50666 | LOW3.01 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50756 | LOW3.01 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50849 | LOW3.01 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54048 | LOW3.01 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54302 | LOW3.01 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35870 | LOW3.01 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-2312 | LOW3.01 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40083 | LOW3.01 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40242 | LOW3.01 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40324 | LOW3.01 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-32284 | LOW3.01 | python3.12-pip-wheel 23.2.1-4.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14087 | LOW3 | glib2 2.56.4-167.el8_10 fixed in 2.56.4-169.el8_10 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-42010 | LOW3 | gnutls 3.6.16-8.el8_10.4 fixed in 3.6.16-8.el8_10.6 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-23112 | LOW3 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31789 | LOW3 | openssl-libs 1:1.1.1k-14.el8_6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49479 | LOW2.96 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50625 | LOW2.96 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50636 | LOW2.96 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53789 | LOW2.96 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54045 | LOW2.96 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54107 | LOW2.96 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54120 | LOW2.96 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54141 | LOW2.96 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54176 | LOW2.96 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54214 | LOW2.96 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54236 | LOW2.96 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54258 | LOW2.96 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39994 | LOW2.96 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39998 | LOW2.96 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40167 | LOW2.96 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40194 | LOW2.96 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40323 | LOW2.96 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40329 | LOW2.96 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68742 | LOW2.96 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23239 | LOW2.96 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23240 | LOW2.96 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-23271 | LOW2.96 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23317 | LOW2.96 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31392 | LOW2.96 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31414 | LOW2.96 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31426 | LOW2.96 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43279 | LOW2.96 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46065 | LOW2.96 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46113 | LOW2.96 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-48651 | LOW2.96 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-1380 | LOW2.94 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 16.8% High Exploitation Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl-libs 1:1.1.1k-14.el8_6 fixed in 1:1.1.1k-16.el8_6 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | curl 7.61.1-34.el8_10.8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49138 | LOW2.91 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-50651 | LOW2.91 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49569 | LOW2.91 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-53240 | LOW2.91 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-40319 | LOW2.91 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46024 | LOW2.91 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl 7.61.1-34.el8_10.8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-54193 | LOW2.86 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-28956 | LOW2.86 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-36350 | LOW2.86 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-36357 | LOW2.86 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-68801 | LOW2.86 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68816 | LOW2.86 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2020-14390 | LOW2.86 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-45582 | LOW2.86 | tar 2:1.30-11.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2018-18483 | LOW2.81 | binutils 2.30-127.el8_10 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9075 | LOW2.81 | binutils 2.30-127.el8_10 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20225 | LOW2.81 | python3-pip-wheel 9.0.3-24.el8 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils 2.30-127.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils 2.30-127.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-38533 | LOW2.8 | binutils 2.30-127.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-47007 | LOW2.8 | binutils 2.30-127.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47008 | LOW2.8 | binutils 2.30-127.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47010 | LOW2.8 | binutils 2.30-127.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47011 | LOW2.8 | binutils 2.30-127.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-25585 | LOW2.8 | binutils 2.30-127.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-25588 | LOW2.8 | binutils 2.30-127.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils 2.30-127.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils 2.30-127.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils 2.30-127.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils 2.30-127.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils 2.30-127.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils 2.30-127.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils 2.30-127.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils 2.30-127.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils 2.30-127.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | cpp 8.5.0-28.el8_10 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | gcc 8.5.0-28.el8_10 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | gcc-c++ 8.5.0-28.el8_10 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-47007 | LOW2.8 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47010 | LOW2.8 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47011 | LOW2.8 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-24883 | LOW2.8 | gnupg2 2.2.20-3.el8_6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-38001 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-40348 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68192 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68291 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68297 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2018-15594 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2018-16862 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2020-13844 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2020-36789 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2020-36790 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2020-8694 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-34556 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-34693 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2021-35477 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2021-38206 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-4135 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-4442 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-46908 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-46960 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-46961 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-46973 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-46976 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47011 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47036 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47038 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47041 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47045 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47092 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47141 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47167 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47168 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47218 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47223 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47225 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-47227 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47230 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47260 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47307 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47316 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47343 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47359 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47389 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47395 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47397 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47415 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47421 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47465 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47492 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47494 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47552 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47557 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47559 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47562 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47563 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47595 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47620 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47646 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47650 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47659 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47668 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-0171 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-36280 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-4543 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-48638 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48648 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48652 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48653 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48687 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48696 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48703 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48711 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48780 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48793 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48799 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48802 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48810 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48811 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48828 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48829 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48835 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48839 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48841 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48844 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48849 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48850 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48853 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48861 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48862 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48863 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48864 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48865 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48868 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48875 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48876 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48889 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48904 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48906 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48909 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48910 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48911 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48914 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48915 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48916 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48929 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48933 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48938 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48946 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48953 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48961 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48969 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48971 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48972 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48975 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48977 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48978 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48982 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48986 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48987 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48994 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49013 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49021 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49048 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49052 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49060 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49072 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49074 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49076 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49077 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49082 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49084 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49096 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49097 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49100 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49109 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49110 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49113 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49116 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49118 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49123 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49126 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49130 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49132 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49134 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49154 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49159 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49171 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49174 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49176 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49179 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49183 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49190 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49193 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49197 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49198 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49204 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49208 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49220 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49231 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49236 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49237 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49248 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49264 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49266 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49271 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49280 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49281 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49293 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49294 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49296 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49307 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49308 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49314 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49316 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49321 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49323 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49325 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49341 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49348 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49349 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49357 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49358 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49370 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49371 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49390 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49394 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49400 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49404 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49412 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49420 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49434 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49437 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49440 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49441 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49442 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49456 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49459 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49468 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49472 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49474 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49492 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49497 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49504 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49521 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49526 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49534 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49535 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49536 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49542 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49558 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49562 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49563 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49564 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49566 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49567 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49583 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49613 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49615 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49617 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49620 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49622 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49624 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49626 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49636 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49643 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49644 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49647 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49651 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49656 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49657 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49658 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49664 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49670 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49671 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49672 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49679 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49700 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49701 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49703 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49715 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49716 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49725 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49728 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49739 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49743 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49748 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49750 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49753 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49759 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49764 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49776 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49780 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49783 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49785 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49802 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49803 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49812 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49821 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49822 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49823 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49824 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49825 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49828 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49829 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49832 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49837 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49838 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49839 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49853 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49863 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49869 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49871 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49873 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49876 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49878 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49879 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49881 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49885 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49886 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49901 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49905 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49908 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49918 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49928 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49929 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49931 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49932 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49963 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49972 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49973 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49984 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49987 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49989 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49993 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50004 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50008 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50059 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50065 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50080 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50086 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50088 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50098 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50118 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50144 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50159 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50166 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50167 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50174 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50186 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50202 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50215 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50222 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50224 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50233 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50272 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50280 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50282 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50314 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50321 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50334 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50359 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50370 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50374 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50380 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50382 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50402 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50409 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50435 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50445 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50459 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50476 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50494 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50709 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50731 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50772 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50780 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50871 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50885 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-3006 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-3022 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-31082 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-31085 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-52450 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52454 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52583 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52587 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52646 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52698 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52702 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52739 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52831 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52901 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52908 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52910 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52912 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52915 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52918 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52920 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52923 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52924 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52925 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52931 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52932 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52973 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52989 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52992 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52996 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53006 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53008 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53016 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53026 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53032 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53038 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53041 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53062 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53066 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53068 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53073 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53080 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53097 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53100 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53101 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53109 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53114 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53118 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53121 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53133 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53143 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53146 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53149 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53171 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53176 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53189 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53198 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53199 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53200 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53201 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53209 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53220 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53221 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53251 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53270 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53277 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53292 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53295 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53302 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53315 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53317 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53326 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53347 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53352 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53382 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53384 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53433 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53438 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53444 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53450 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53457 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53458 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53463 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53470 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53477 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53480 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53481 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53488 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53491 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53499 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53503 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53509 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53529 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53540 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53567 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53574 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53589 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53601 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53612 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53627 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53635 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53639 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53655 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53663 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53667 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53682 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53684 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53747 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53756 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53765 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53800 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53822 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53856 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53987 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53989 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53999 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54012 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54028 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54040 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54052 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54137 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54238 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54271 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54299 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-7324 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-1151 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-22099 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-26688 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26771 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26816 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-26902 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26931 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-26999 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27413 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27417 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27435 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35803 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35808 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35840 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35875 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35885 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35895 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35907 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35933 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35950 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35957 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35969 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-35978 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-35983 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36021 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36882 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36884 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36903 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36970 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38543 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-39488 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-40923 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-40937 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-40966 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-40980 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-40990 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41010 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-41037 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41062 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41082 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41089 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41095 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42069 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42082 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42101 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-42106 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-42110 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42125 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42135 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42139 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42145 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42223 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42232 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42245 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42259 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-42268 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42274 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42281 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42286 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42288 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42289 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42291 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42304 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42305 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42309 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42310 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43819 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43821 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43834 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43835 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-43846 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43853 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43856 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-43861 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43884 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-43906 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43908 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43910 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43911 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43912 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43914 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44931 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-44944 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44957 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44958 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44961 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-45001 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-45005 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-45006 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-45008 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-45009 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-45010 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-45016 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-45025 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46678 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46689 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46715 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46717 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46719 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46737 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46739 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46745 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46750 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46754 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46755 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46760 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46761 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46762 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46770 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46771 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46777 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46783 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46805 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46807 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46819 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46822 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46834 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46835 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46842 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46855 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46857 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47141 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47408 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47673 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47678 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47684 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-47703 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47705 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47706 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47707 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47710 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47713 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-47737 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-47739 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47749 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-48873 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49568 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49571 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49851 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49856 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49881 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49886 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49888 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49891 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49925 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49927 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49929 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49937 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49938 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49939 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49940 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49944 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49948 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49952 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49955 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49959 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49962 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49971 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49973 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49974 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-49975 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49978 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49994 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50000 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50008 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50009 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50019 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50024 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50028 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50038 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50039 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50040 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50041 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50045 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50048 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50058 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50095 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50117 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50136 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50141 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50146 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50147 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50153 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50160 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50162 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50167 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50179 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50185 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50189 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50191 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50195 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50199 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50205 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50207 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50208 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50237 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50255 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50258 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50272 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50290 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50299 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50304 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53042 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53050 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53055 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53060 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53063 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53066 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53073 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53079 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53093 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53114 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53119 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53121 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53140 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53144 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53146 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53190 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53194 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53195 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53196 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53219 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53224 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53229 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53680 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-54683 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-55916 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56369 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56566 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56569 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56574 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56589 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56590 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56591 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56611 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56623 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56636 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-56647 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56667 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56688 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56690 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56703 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56716 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56718 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56739 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56757 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56763 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56769 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56770 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-56779 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57843 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57884 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57888 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57890 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57903 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57924 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57930 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57932 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57938 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57946 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57947 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57948 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57977 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57981 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57986 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57996 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58005 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58017 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58057 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58061 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58083 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58096 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58097 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58098 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58100 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58237 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58239 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21648 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21653 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21664 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21666 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21667 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21669 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21673 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21681 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21682 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21683 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21689 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21696 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21699 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21707 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21728 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21729 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21738 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21745 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21763 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21765 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21796 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21814 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21817 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21828 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21839 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21844 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21846 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21853 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21857 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21862 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21870 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21885 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21899 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21926 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21936 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21948 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21951 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21959 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21963 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21964 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21971 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21975 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21980 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21997 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22021 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22025 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22053 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22055 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22057 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22062 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22063 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22065 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22075 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22089 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22090 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22124 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22125 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23131 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23136 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23141 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23143 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23145 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23161 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23163 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37745 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37757 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37773 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37800 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37807 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37808 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37824 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37829 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37834 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37836 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37844 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37857 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37859 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37860 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37862 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37875 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37877 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37878 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37884 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37940 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37948 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37949 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37958 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37959 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37961 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37963 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37967 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37974 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37989 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37990 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37992 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37994 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37995 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37997 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37998 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38014 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38015 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38017 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38023 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38029 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38031 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38035 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38038 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38040 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38044 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38047 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38057 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38058 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38060 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38061 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38062 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38063 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38064 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38066 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38067 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-38071 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38075 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38084 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38099 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38105 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38113 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38115 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38122 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38126 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38127 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38147 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38161 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38162 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38166 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38177 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38181 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38184 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38190 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38192 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38214 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38215 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38222 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38229 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38285 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38293 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38303 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38307 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38311 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38312 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38324 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38334 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38337 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38344 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38359 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38386 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38387 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38391 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38399 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38412 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38424 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38430 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38436 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38439 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38444 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38457 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38458 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38465 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38466 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38468 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38470 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38473 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38474 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38495 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38516 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38539 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38540 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38553 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38560 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38601 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38602 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38614 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38622 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38644 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38645 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38646 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38659 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38664 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38691 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38692 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38694 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38695 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38700 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38701 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38706 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38709 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38710 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38725 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38735 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39677 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39678 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39732 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39742 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39746 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39756 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39763 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39764 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39773 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39782 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39794 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39798 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39808 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39838 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39847 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39857 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39889 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39902 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39931 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39932 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39940 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39947 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39949 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39953 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39965 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40020 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40026 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40030 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40044 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40053 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40070 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40075 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40078 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40102 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40104 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40115 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40140 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40153 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40160 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40171 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40195 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40211 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40231 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40264 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40280 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40283 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40297 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40362 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40363 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68185 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68188 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68209 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68211 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68223 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68229 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68231 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68261 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68262 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68265 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68283 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68309 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68310 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68313 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68337 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68372 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68379 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68756 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71064 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71077 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71083 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71087 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71094 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71098 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71104 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71114 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71120 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71127 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71131 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71132 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71135 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71160 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71202 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71229 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71236 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71273 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71286 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71295 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71297 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71305 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-22976 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22977 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22981 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22985 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22991 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-22992 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-22993 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22996 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-22999 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23000 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23011 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23017 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23021 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23023 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23038 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23047 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23058 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23059 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23060 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23061 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23069 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23084 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23086 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23103 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23105 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23108 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23120 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23121 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23125 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23128 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23133 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23138 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23164 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23200 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23241 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23242 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-23248 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23255 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23262 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23272 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23276 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23277 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23286 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23292 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23296 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23298 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23304 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23307 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23335 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23336 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23340 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23351 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23365 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23368 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23381 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23382 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23386 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23391 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23398 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23439 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23442 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23444 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23449 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23462 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-23472 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31394 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31400 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31403 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31407 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31411 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31415 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31416 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31421 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31422 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31423 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31424 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31427 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31435 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31436 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-31438 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31441 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31446 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31447 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31448 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31450 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-31451 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31453 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31454 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31468 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31469 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31473 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31480 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31482 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31483 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31487 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31492 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31495 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31496 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31498 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31499 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31503 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31507 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31510 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31512 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31515 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31518 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31519 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31521 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31526 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31528 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31533 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31542 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31543 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31546 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31548 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31551 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31554 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31555 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31557 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31574 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31575 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31590 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31591 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31592 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31593 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31600 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31609 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-31619 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31624 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31625 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31628 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31630 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31632 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31633 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-31637 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-31642 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31647 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31648 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31661 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31662 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31665 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31666 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31667 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31672 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31673 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31674 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31675 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31676 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31678 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31679 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31680 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31681 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31682 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31692 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31693 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31698 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31699 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31742 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31752 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31758 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31771 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31773 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31777 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31779 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31781 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43009 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43013 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43018 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43021 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43022 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43024 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43025 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43026 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43028 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43033 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43035 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43042 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43043 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43048 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43054 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43062 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43064 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43067 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43071 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43079 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43080 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43084 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43085 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43088 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43089 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43091 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43093 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43107 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43111 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43112 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43119 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43124 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43129 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43132 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43133 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43135 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43136 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43137 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43139 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43140 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43143 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43152 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43153 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43156 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43161 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43171 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43172 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43176 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43180 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43187 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43189 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43201 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43213 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43214 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43215 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43216 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43238 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43251 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43257 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43266 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43267 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43271 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43273 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43277 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43278 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43287 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43288 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43292 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43315 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43323 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43333 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43350 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43362 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43363 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43365 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43405 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43406 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43407 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43409 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43411 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43413 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43416 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43420 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43429 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43436 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43437 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43445 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43452 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43456 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43459 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43466 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43468 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43469 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43472 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43473 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43475 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45834 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45835 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45836 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45838 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45842 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45843 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-45844 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45846 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45855 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45857 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45862 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45944 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45983 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45985 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46021 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46023 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46027 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-46028 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46032 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46051 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46070 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46082 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46086 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46102 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-46107 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46137 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-46146 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46151 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46158 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46168 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46170 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46172 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46193 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46214 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46253 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46273 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-46280 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46304 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-46312 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46320 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46322 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-8043 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2019-12380 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2019-18806 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2019-19039 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2019-19462 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2019-20095 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2020-10781 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2020-12656 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2020-12768 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2020-12769 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2020-36311 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-20320 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-38198 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2021-4440 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-45402 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-46904 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-46910 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-46915 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-46917 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-46918 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-46920 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-46921 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-46926 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-46929 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-46932 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-46937 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-46963 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-46978 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-46988 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-46997 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47003 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47020 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47024 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47071 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47074 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47077 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47079 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47116 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47120 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47133 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47134 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47136 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47143 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47146 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47162 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47163 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47170 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47173 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47176 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47177 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47178 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47182 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47183 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47186 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47197 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47199 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47201 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47207 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47210 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47211 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47215 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47217 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47246 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47250 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47258 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47262 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47264 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47265 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47266 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47276 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47290 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47298 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47305 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47319 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47320 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47325 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47332 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47339 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47349 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47360 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47370 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47374 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47376 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47380 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47381 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47387 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47398 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47407 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47413 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47416 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47419 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47420 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47424 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47426 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47431 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47438 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47452 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47453 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47462 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47481 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47490 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47514 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47529 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47550 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47554 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47558 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47578 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47588 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47591 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47594 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47597 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47606 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47607 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47608 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47617 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47619 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47623 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47639 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47657 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-0264 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-2905 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3344 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-3606 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48628 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48631 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48633 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48635 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48639 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48640 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48641 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48643 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48647 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48659 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48673 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48690 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48691 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48697 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48704 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48705 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48709 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48710 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48713 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48715 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48721 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48724 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48725 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48728 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48729 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48730 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48731 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48746 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48752 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48755 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48758 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48763 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48764 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48767 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48769 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48770 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48772 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48800 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48806 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48807 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48809 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48823 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48825 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48890 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48896 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48905 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48979 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49005 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49027 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49065 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49070 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49103 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49107 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49124 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49139 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49155 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49157 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49177 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49178 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49206 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49207 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49209 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49225 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49235 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49287 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49297 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49322 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49345 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49350 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49352 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49353 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49374 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49402 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49413 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49422 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49432 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49436 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49447 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49476 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49498 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49516 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49520 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49531 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49532 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49538 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49549 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49552 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49565 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49653 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49731 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49749 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49766 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49769 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49772 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49782 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49784 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49813 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49817 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49835 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49874 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49880 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49889 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49906 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49915 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49927 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49937 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49938 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49949 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49979 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49981 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50012 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50025 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50045 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50104 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50107 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50123 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50134 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50143 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50170 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50176 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50197 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50201 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50203 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50218 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50244 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50253 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50278 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50285 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50304 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50311 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50312 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50332 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50349 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50352 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50395 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50424 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50434 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50460 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50481 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50500 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50504 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50505 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50511 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50521 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50550 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50561 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50562 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50566 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50577 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50580 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50615 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50617 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50619 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50626 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50643 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50645 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50646 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50650 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50655 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50664 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50667 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50669 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50679 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50702 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50719 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-50742 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50749 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50751 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50761 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50771 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50845 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50868 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50872 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-1076 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-3358 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-37454 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-4194 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52435 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52458 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52465 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52498 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52516 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52532 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52570 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52625 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52632 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52634 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52674 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52676 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52680 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52689 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52732 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52736 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52743 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52744 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52745 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52747 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52750 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52754 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52782 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52788 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52806 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52808 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52814 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52815 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52819 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52833 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52880 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52882 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52883 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-52928 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52936 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52937 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52938 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52939 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52942 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52976 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52984 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52986 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52993 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52994 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53005 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53007 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53011 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53013 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53015 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53031 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53048 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53049 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53074 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53091 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53093 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53098 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53115 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53127 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53128 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53131 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53165 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53174 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53208 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53234 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53271 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53279 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53309 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53313 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53332 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53341 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53344 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53351 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53369 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53378 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53383 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53391 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53408 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53411 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53431 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53456 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53460 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53467 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53474 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53482 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53489 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53548 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53588 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53593 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53603 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53606 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53671 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53685 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53709 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53711 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53712 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53716 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53719 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53728 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53731 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53754 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53818 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53826 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53830 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53836 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53844 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53847 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53859 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53863 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54006 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54019 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54021 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54033 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54046 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54051 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54056 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54062 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54066 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54084 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54087 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54093 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54095 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54099 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54134 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54173 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54223 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54237 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54242 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54254 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54288 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54305 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54306 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54314 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54318 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-7042 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-14027 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-25740 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26591 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26611 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26633 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-26641 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26646 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26647 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26663 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26668 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26680 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26687 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26695 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26700 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26715 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-26718 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26719 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26721 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26751 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26756 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26767 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26775 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26803 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26812 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26838 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26845 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26900 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-26903 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-26916 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26922 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-26926 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-26927 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-26938 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26962 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27004 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27023 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-27057 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27073 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-27403 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27431 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27436 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-27437 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35794 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35805 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35817 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35843 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35860 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35901 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35904 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35922 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35927 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35931 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35934 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35945 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35961 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35976 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-35995 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36478 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-36911 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36937 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36938 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36955 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36962 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38594 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38600 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38607 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38618 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-38663 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-39473 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-39509 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-40919 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-40945 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-40964 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-40999 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41047 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41063 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41072 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41077 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41079 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41098 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-42063 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42065 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42067 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42068 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42080 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42097 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42098 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42122 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42126 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42129 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42321 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43817 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43863 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43890 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-43893 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-44947 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2024-45012 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-45019 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46672 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46681 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46707 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46720 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46765 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46784 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46788 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46825 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46860 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46861 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46864 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47143 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47671 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47674 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47728 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47794 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47809 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49858 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49875 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50001 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50093 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50134 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50138 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50148 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50163 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50194 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50201 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53051 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53094 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53125 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53151 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53157 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53161 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53164 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53172 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53180 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53198 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53210 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53215 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53217 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53685 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-55881 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56531 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56532 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56533 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56583 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56587 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56588 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56592 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56593 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56617 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56629 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56641 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56657 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56659 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56681 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56701 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56715 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56720 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56745 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56747 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56748 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56752 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56756 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56782 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57804 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57883 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57931 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57933 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57952 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57973 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57993 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58012 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58077 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58078 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58079 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58090 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21634 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21636 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21637 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21638 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21639 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21640 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21690 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21694 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21708 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21712 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21723 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21733 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21744 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21750 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21766 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21776 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21779 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21806 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21829 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21831 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21833 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21847 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21866 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21872 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21875 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21877 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21881 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21886 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21888 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21890 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21891 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21909 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21910 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21916 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21918 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21922 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21931 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21970 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21976 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21981 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21992 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21995 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21996 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22086 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37756 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-37788 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37792 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37794 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37805 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37867 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37911 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37932 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37937 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37980 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37984 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38039 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38045 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38096 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38097 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38193 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38202 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38262 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38345 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38402 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38438 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38460 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38528 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38546 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38576 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38581 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38591 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38608 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38623 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38624 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38643 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38671 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38693 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38721 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39676 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39724 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39736 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39737 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39745 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39748 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39752 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39753 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39772 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39795 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39819 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39833 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39865 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39929 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39937 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39990 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40042 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40049 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40099 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40103 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40105 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40125 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40164 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40219 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40325 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40360 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68171 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68173 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68178 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68194 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68200 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68206 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68219 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68227 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68244 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68288 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68295 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68300 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68308 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68321 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68336 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68345 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68363 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68725 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68734 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68753 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68780 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68783 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68785 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68794 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68795 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68798 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68813 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68818 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68820 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68822 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71096 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71108 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71113 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71118 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71125 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71154 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71161 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71227 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71232 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71235 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71285 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71315 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-22979 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23005 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23085 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23119 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23154 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23190 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23237 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23247 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23256 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23257 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23258 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23290 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23303 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23312 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23313 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23352 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23367 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23374 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23379 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23389 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23399 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31428 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31486 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31497 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31520 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31522 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31524 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31664 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31670 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31671 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31677 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43030 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43036 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43041 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43068 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43073 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43123 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43148 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43167 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43194 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43223 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43253 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43262 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43309 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43313 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43314 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43344 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43425 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43428 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43432 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43451 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43483 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43484 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43488 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43496 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45870 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45871 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45872 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45877 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45905 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45915 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45917 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45919 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45920 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45923 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45941 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45948 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45961 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45963 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45964 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45968 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45982 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45987 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45997 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46003 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46014 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46018 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46026 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46038 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46040 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46046 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46049 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46059 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46068 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46071 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46088 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46092 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46103 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46126 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46144 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46153 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46161 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46167 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46178 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46184 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46196 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46235 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46302 | LOW2.8 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | libstdc++-devel 8.5.0-28.el8_10 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2023-24056 | LOW2.8 | pkgconf 1.4.2-1.el8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-13837 | LOW2.8 | platform-python 3.6.8-71.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42308 | LOW2.8 | platform-python 3.6.8-71.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-6075 | LOW2.8 | platform-python 3.6.8-71.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-25645 | LOW2.8 | python3-pip-wheel 9.0.3-24.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-13837 | LOW2.8 | python3.12 3.12.11-2.el8_10 fixed in 3.12.13-2.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42308 | LOW2.8 | python3.12 3.12.11-2.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-6075 | LOW2.8 | python3.12 3.12.11-2.el8_10 fixed in 3.12.13-2.el8_10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-25645 | LOW2.8 | python3.12-pip-wheel 23.2.1-4.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 2:1.30-11.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-28418 | LOW2.8 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45130 | LOW2.8 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-3236 | LOW2.8 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-2923 | LOW2.8 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-2980 | LOW2.8 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2022-3153 | LOW2.8 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-4293 | LOW2.8 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-1264 | LOW2.8 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-2609 | LOW2.8 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-46246 | LOW2.8 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-5441 | LOW2.8 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-45306 | LOW2.8 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-22134 | LOW2.8 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-24014 | LOW2.8 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41990 | LOW2.8 | libgcrypt 1.8.5-7.el8_6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0965 | LOW2.8 | libssh 0.9.6-16.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0965 | LOW2.8 | libssh-config 0.9.6-16.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | python3-libs 3.6.8-71.el8_10 fixed in 3.6.8-75.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | python3-libs 3.6.8-71.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | python3-libs 3.6.8-71.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | python3.12-libs 3.12.11-2.el8_10 fixed in 3.12.12-4.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | python3.12-libs 3.12.11-2.el8_10 fixed in 3.12.13-2.el8_10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | python3.12-libs 3.12.11-2.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | sqlite-libs 3.26.0-20.el8_10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-33845 | LOW2.78 | gnutls 3.6.16-8.el8_10.4 fixed in 3.6.16-8.el8_10.6 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2018-20657 | LOW2.7 | libatomic 8.5.0-28.el8_10 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20657 | LOW2.7 | libgcc 8.5.0-28.el8_10 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20657 | LOW2.7 | libgomp 8.5.0-28.el8_10 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20657 | LOW2.7 | libstdc++ 8.5.0-28.el8_10 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-27113 | LOW2.7 | libxml2 2.9.7-21.el8_10.3 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-4899 | LOW2.7 | libzstd 1.4.4-1.el8 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9674 | LOW2.7 | python3-libs 3.6.8-71.el8_10 No fix yet | 5.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-7592 | LOW2.7 | python3-libs 3.6.8-71.el8_10 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-7592 | LOW2.7 | python3.12-libs 3.12.11-2.el8_10 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19244 | LOW2.7 | sqlite-libs 3.26.0-20.el8_10 No fix yet | 3.3% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9936 | LOW2.7 | sqlite-libs 3.26.0-20.el8_10 No fix yet | 5.7% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9937 | LOW2.7 | sqlite-libs 3.26.0-20.el8_10 No fix yet | 6.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | curl 7.61.1-34.el8_10.8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | curl 7.61.1-34.el8_10.8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | curl 7.61.1-34.el8_10.8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-0915 | LOW2.7 | glibc-devel 2.28-251.el8_10.25 fixed in 2.28-251.el8_10.31 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-4046 | LOW2.7 | glibc-devel 2.28-251.el8_10.25 fixed in 2.28-251.el8_10.37 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-0915 | LOW2.7 | glibc-headers 2.28-251.el8_10.25 fixed in 2.28-251.el8_10.31 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-4046 | LOW2.7 | glibc-headers 2.28-251.el8_10.25 fixed in 2.28-251.el8_10.37 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-40204 | LOW2.7 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47238 | LOW2.7 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50774 | LOW2.7 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53713 | LOW2.7 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53726 | LOW2.7 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54092 | LOW2.7 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54243 | LOW2.7 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-24858 | LOW2.7 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-26886 | LOW2.7 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-36881 | LOW2.7 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39968 | LOW2.7 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39972 | LOW2.7 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40353 | LOW2.7 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68367 | LOW2.7 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71225 | LOW2.7 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23457 | LOW2.7 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-50755 | LOW2.7 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54181 | LOW2.7 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl 7.61.1-34.el8_10.8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl 7.61.1-34.el8_10.8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl 7.61.1-34.el8_10.8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-12084 | LOW2.7 | platform-python 3.6.8-71.el8_10 fixed in 3.6.8-72.el8_10 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW2.7 | platform-python 3.6.8-71.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW2.7 | platform-python 3.6.8-71.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-12084 | LOW2.7 | python3.12 3.12.11-2.el8_10 fixed in 3.12.12-1.el8_10 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW2.7 | python3.12 3.12.11-2.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW2.7 | python3.12 3.12.11-2.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-44656 | LOW2.7 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-39970 | LOW2.65 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40338 | LOW2.65 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40343 | LOW2.65 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52735 | LOW2.64 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-38605 | LOW2.64 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-8277 | LOW2.63 | libssh 0.9.6-16.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0968 | LOW2.63 | libssh 0.9.6-16.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-8277 | LOW2.63 | libssh-config 0.9.6-16.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0968 | LOW2.63 | libssh-config 0.9.6-16.el8_10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1795 | LOW2.63 | python3-libs 3.6.8-71.el8_10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1795 | LOW2.63 | python3.12-libs 3.12.11-2.el8_10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-50640 | LOW2.6 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50852 | LOW2.6 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54226 | LOW2.6 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40178 | LOW2.6 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23035 | LOW2.6 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47327 | LOW2.6 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-4516 | LOW2.6 | platform-python 3.6.8-71.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-4516 | LOW2.6 | python3.12 3.12.11-2.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils 2.30-127.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | binutils 2.30-127.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5450 | LOW2.55 | glibc-devel 2.28-251.el8_10.25 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-5928 | LOW2.55 | glibc-devel 2.28-251.el8_10.25 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5450 | LOW2.55 | glibc-headers 2.28-251.el8_10.25 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-5928 | LOW2.55 | glibc-headers 2.28-251.el8_10.25 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-50736 | LOW2.55 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40121 | LOW2.55 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-0397 | LOW2.55 | platform-python 3.6.8-71.el8_10 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2024-0397 | LOW2.55 | python3.12 3.12.11-2.el8_10 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-0992 | LOW2.46 | libxml2 2.9.7-21.el8_10.3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-14017 | LOW2.45 | curl 7.61.1-34.el8_10.8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-24859 | LOW2.45 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-3056 | LOW2.45 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl 7.61.1-34.el8_10.8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | LOW2.45 | platform-python 3.6.8-71.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.45 | platform-python 3.6.8-71.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | LOW2.45 | python3.12 3.12.11-2.el8_10 fixed in 3.12.13-2.el8_10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.45 | python3.12 3.12.11-2.el8_10 fixed in 3.12.13-2.el8_10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl 7.61.1-34.el8_10.8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gnupg2 2.2.20-3.el8_6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gnupg2 2.2.20-3.el8_6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2019-20794 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2020-27170 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2021-33624 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2021-46925 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47248 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47507 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48751 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48784 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48842 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48899 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48931 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48985 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49003 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49089 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49201 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49215 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49286 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49295 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49300 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49344 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49414 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49571 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49572 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49573 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49574 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49575 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49578 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49580 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49585 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49586 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49589 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49590 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49593 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49595 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49596 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49597 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49598 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49599 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49601 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49602 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49604 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49607 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49630 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49632 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49638 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49639 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49641 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49771 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49781 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49884 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49967 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50373 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52568 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52898 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53046 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53204 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53368 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53452 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53520 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53697 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53794 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53799 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53815 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53824 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53832 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53848 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53853 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27415 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-39293 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39500 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-40905 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41020 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42107 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43866 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44954 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-45003 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46787 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47660 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47679 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50006 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50135 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50183 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50277 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53100 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53124 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53136 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56637 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57974 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21732 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21892 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21938 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38048 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38078 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38083 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38112 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38232 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38462 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38617 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-39726 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39754 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39927 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39961 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39977 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39996 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40011 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40085 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40110 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40120 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40134 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40139 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40187 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40215 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40220 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40254 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40331 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40342 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68241 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68296 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68745 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23004 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23071 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23126 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23212 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23452 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31393 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31456 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31523 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31535 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31572 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31697 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43047 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43053 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43383 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43448 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45949 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46017 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2019-15807 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2019-16230 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2019-19054 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2019-19066 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2019-19082 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2019-19083 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2019-19965 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2021-47001 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-41850 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48745 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49443 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49554 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49576 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49577 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49579 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49587 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49603 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49640 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50259 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-50697 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50875 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52639 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52749 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53020 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54007 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54042 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-23196 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-24855 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26915 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38580 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38601 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42287 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46710 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49866 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56568 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21701 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22027 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37920 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39813 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68214 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68264 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71111 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23101 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23110 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23302 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31466 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43439 | LOW2.4 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl 7.61.1-34.el8_10.8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-64118 | LOW2.4 | tar 2:1.30-11.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.32.1-46.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-48706 | LOW2.4 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-43374 | LOW2.4 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-47814 | LOW2.4 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1485 | LOW2.38 | glib2 2.56.4-167.el8_10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-15213 | LOW2.35 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2019-19530 | LOW2.35 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-49934 | LOW2.35 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2019-15217 | LOW2.35 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2019-15218 | LOW2.35 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2019-15219 | LOW2.35 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2019-15291 | LOW2.35 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2022-3903 | LOW2.35 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-54113 | LOW2.29 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40308 | LOW2.29 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53831 | LOW2.29 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11468 | LOW2.29 | platform-python 3.6.8-71.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0865 | LOW2.29 | platform-python 3.6.8-71.el8_10 fixed in 3.6.8-73.el8_10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW2.29 | platform-python 3.6.8-71.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-11468 | LOW2.29 | python3.12 3.12.11-2.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0865 | LOW2.29 | python3.12 3.12.11-2.el8_10 fixed in 3.12.12-3.el8_10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW2.29 | python3.12 3.12.11-2.el8_10 fixed in 3.12.13-2.el8_10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-43802 | LOW2.29 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils-single 8.30-15.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2018-17977 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-4159 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47078 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47449 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-49196 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49288 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-49411 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-50579 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53733 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53811 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54155 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40081 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40281 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2020-11494 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2020-14304 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2020-25639 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-47010 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-47070 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47075 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2021-47140 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2021-47242 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47333 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47350 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47367 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47464 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47603 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48761 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50720 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52738 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2023-53718 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54086 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54160 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54247 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26648 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26672 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26747 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26757 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26758 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26857 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-36910 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36944 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38384 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38388 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40123 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40183 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40198 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40200 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23458 | LOW2.24 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-29768 | LOW2.24 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-28420 | LOW2.24 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42307 | LOW2.24 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2023-54213 | LOW2.19 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-39920 | LOW2.19 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2020-11609 | LOW2.19 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-47233 | LOW2.19 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-40275 | LOW2.19 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6069 | LOW2.19 | platform-python 3.6.8-71.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8291 | LOW2.19 | platform-python 3.6.8-71.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-6069 | LOW2.19 | python3.12 3.12.11-2.el8_10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8291 | LOW2.19 | python3.12 3.12.11-2.el8_10 fixed in 3.12.12-1.el8_10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-48231 | LOW2.19 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48232 | LOW2.19 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48233 | LOW2.19 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48234 | LOW2.19 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48235 | LOW2.19 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48236 | LOW2.19 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48237 | LOW2.19 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2020-14416 | LOW2.14 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2020-26558 | LOW2.14 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-50358 | LOW2.14 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-45803 | LOW2.14 | python3-pip-wheel 9.0.3-24.el8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-41965 | LOW2.14 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-26603 | LOW2.14 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-24515 | LOW2.12 | expat 2.5.0-1.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6170 | LOW2.12 | libxml2 2.9.7-21.el8_10.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48646 | LOW2.09 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50558 | LOW2.09 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52872 | LOW2.09 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53720 | LOW2.09 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42229 | LOW2.09 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40173 | LOW2.09 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2019-16089 | LOW2.09 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2019-16229 | LOW2.09 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-4001 | LOW2.09 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48634 | LOW2.09 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4438 | LOW2.04 | glibc-devel 2.28-251.el8_10.25 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4438 | LOW2.04 | glibc-headers 2.28-251.el8_10.25 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50853 | LOW2.04 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53695 | LOW2.04 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54229 | LOW2.04 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50777 | LOW2.04 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53708 | LOW2.04 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53994 | LOW2.04 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53715 | LOW1.99 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-20193 | LOW1.98 | tar 2:1.30-11.el8_10 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils 2.30-127.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2020-29374 | LOW1.84 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | shadow-utils 2:4.6-22.el8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2020-35501 | LOW1.73 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68740 | LOW1.73 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils 2.30-127.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils 2.30-127.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils 2.30-127.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils 2.30-127.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils 2.30-127.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils 2.30-127.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.30-127.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gnupg2 2.2.20-3.el8_6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-68191 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-3655 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-50628 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47738 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50057 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57898 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39964 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-47317 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-48939 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50575 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50712 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50820 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50827 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50835 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50839 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50850 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50859 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50883 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53992 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53998 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54116 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54119 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54172 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54177 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54198 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54211 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54218 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54227 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54230 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54252 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54260 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54282 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46794 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50044 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50211 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50280 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40035 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40268 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68782 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71224 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23261 | LOW1.68 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4519 | LOW1.68 | platform-python 3.6.8-71.el8_10 fixed in 3.6.8-75.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.68 | platform-python 3.6.8-71.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | platform-python 3.6.8-71.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4519 | LOW1.68 | python3.12 3.12.11-2.el8_10 fixed in 3.12.12-4.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.68 | python3.12 3.12.11-2.el8_10 fixed in 3.12.13-2.el8_10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3.12 3.12.11-2.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-39804 | LOW1.68 | tar 2:1.30-11.el8_10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils 2.30-127.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils 2.30-127.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1795 | LOW1.58 | platform-python 3.6.8-71.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1795 | LOW1.58 | python3.12 3.12.11-2.el8_10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils 2.30-127.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils 2.30-127.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils 2.30-127.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | gcc-toolset-14-binutils 2.41-4.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | gdb-gdbserver 8.2-20.el8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50665 | LOW1.27 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50870 | LOW1.27 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54267 | LOW1.27 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54268 | LOW1.27 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54283 | LOW1.27 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68788 | LOW1.27 | kernel-headers 4.18.0-553.87.1.el8_10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-28422 | LOW1.12 | vim-minimal 2:8.0.1763-21.el8_10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-39537 | NONE0 | ncurses-base 6.1-10.20180224.el8 No fix yet | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2021-39537 | NONE0 | ncurses-libs 6.1-10.20180224.el8 No fix yet | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2020-35512 | NONE0 | dbus 1:1.12.8-27.el8_10 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-35512 | NONE0 | dbus-common 1:1.12.8-27.el8_10 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-29111 | NONE0 | systemd 239-82.el8_10.8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4105 | NONE0 | systemd 239-82.el8_10.8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2020-19185 | NONE0 | ncurses-base 6.1-10.20180224.el8 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19186 | NONE0 | ncurses-base 6.1-10.20180224.el8 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2020-19187 | NONE0 | ncurses-base 6.1-10.20180224.el8 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19188 | NONE0 | ncurses-base 6.1-10.20180224.el8 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19189 | NONE0 | ncurses-base 6.1-10.20180224.el8 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2020-19190 | NONE0 | ncurses-base 6.1-10.20180224.el8 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.1-10.20180224.el8 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2020-19185 | NONE0 | ncurses-libs 6.1-10.20180224.el8 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19186 | NONE0 | ncurses-libs 6.1-10.20180224.el8 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2020-19187 | NONE0 | ncurses-libs 6.1-10.20180224.el8 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19188 | NONE0 | ncurses-libs 6.1-10.20180224.el8 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19189 | NONE0 | ncurses-libs 6.1-10.20180224.el8 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2020-19190 | NONE0 | ncurses-libs 6.1-10.20180224.el8 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-libs 6.1-10.20180224.el8 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-0235 | NONE0 | dnf-plugin-subscription-manager 1.28.44-1.el8_10 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-0235 | NONE0 | subscription-manager 1.28.44-1.el8_10 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-0235 | NONE0 | subscription-manager-rhsm-certificates 20220623-1.el8 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-19211 | NONE0 | ncurses-base 6.1-10.20180224.el8 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2018-19211 | NONE0 | ncurses-libs 6.1-10.20180224.el8 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-24056 | NONE0 | pkgconf-m4 1.4.2-1.el8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-24056 | NONE0 | pkgconf-pkg-config 1.4.2-1.el8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-3997 | NONE0 | systemd 239-82.el8_10.8 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-4598 | NONE0 | systemd 239-82.el8_10.8 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-9358 | NONE0 | dnf-plugin-subscription-manager 1.28.44-1.el8_10 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9358 | NONE0 | subscription-manager 1.28.44-1.el8_10 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9358 | NONE0 | subscription-manager-rhsm-certificates 20220623-1.el8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-20839 | NONE0 | systemd 239-82.el8_10.8 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-25260 | NONE0 | elfutils-default-yama-scope 0.190-2.el8 No fix yet | 0.3% Theoretical Threat | Not Applicable |