Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker could exploit these vulnerabilities to execute arbitrary code remotely, compromise sensitive data processed in Jupyter notebooks, or cause denial of service. For example, CVE-2025-15467 in OpenSSL and CVE-2024-2961 in glibc are remotely exploitable with maximum severity. While the image is widely used and maintained by the Jupyter community, the extreme vulnerability volume (over 7,000 exposed) means that even with compensating controls like network segmentation and minimal exposure, the residual risk remains high. Vendored packages like PyArrow (CVE-2023-47248) also introduce code execution risks via malicious data files, which are common in data-science workflows.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2024-47175 | CRITICAL10 | libcups2 2.4.1op1-1ubuntu4.7 fixed in 2.4.1op1-1ubuntu4.11 | 62.5% Actively Exploited | Directly Exposed |
| CVE-2025-15467 | CRITICAL10 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.21 | 47.6% High Exploitation Risk | Directly Exposed |
| CVE-2023-47248 | CRITICAL10 | pyarrow 13.0.0 fixed in 14.0.1 | 14.4% High Exploitation Risk | Directly Exposed |
| CVE-2024-3596 | CRITICAL10 | libgssapi-krb5-2 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.5 | 14.9% High Exploitation Risk | Directly Exposed |
| CVE-2024-3596 | CRITICAL10 | libk5crypto3 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.5 | 14.9% High Exploitation Risk | Directly Exposed |
| CVE-2024-3596 | CRITICAL10 | libkrb5-3 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.5 | 14.9% High Exploitation Risk | Directly Exposed |
| CVE-2024-3596 | CRITICAL10 | libkrb5support0 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.5 | 14.9% High Exploitation Risk | Directly Exposed |
| CVE-2024-2961 | CRITICAL10 | libc-bin 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.7 | 88.3% Actively Exploited | Directly Exposed |
| CVE-2024-2961 | CRITICAL10 | libc-dev-bin 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.7 | 88.3% Actively Exploited | Directly Exposed |
| CVE-2024-2961 | CRITICAL10 | libc6 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.7 | 88.3% Actively Exploited | Directly Exposed |
| CVE-2024-2961 | CRITICAL10 | libc6-dev 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.7 | 88.3% Actively Exploited | Directly Exposed |
| CVE-2026-31431 | CRITICAL10 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-179.189 | 96.3% Actively Exploited | Directly Exposed |
| CVE-2026-43284 | CRITICAL10 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-181.191 | 93.2% Actively Exploited | Directly Exposed |
| CVE-2026-43500 | CRITICAL10 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-181.191 | 92.8% Actively Exploited | Directly Exposed |
| CVE-2025-6965 | CRITICAL10 | libsqlite3-0 3.37.2-2ubuntu0.1 fixed in 3.37.2-2ubuntu0.5 | 73.5% Actively Exploited | Directly Exposed |
| CVE-2024-5171 | CRITICAL9.8 | libaom3 3.3.0-1 fixed in 3.3.0-1ubuntu0.1 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2016-1585 | CRITICAL9.8 | libapparmor1 3.0.4-2ubuntu2.2 fixed in 3.0.4-2ubuntu2.4 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-45491 | CRITICAL9.8 | libexpat1 2.4.7-1ubuntu0.2 fixed in 2.4.7-1ubuntu0.4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-45492 | CRITICAL9.8 | libexpat1 2.4.7-1ubuntu0.2 fixed in 2.4.7-1ubuntu0.4 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42010 | CRITICAL9.8 | libgnutls30 3.7.3-4ubuntu1.2 fixed in 3.7.3-4ubuntu1.9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48522 | CRITICAL9.8 | libperl5.34 5.34.0-3ubuntu1.2 fixed in 5.34.0-3ubuntu1.3 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-56171 | CRITICAL9.8 | libxml2 2.9.13+dfsg-1ubuntu0.3 fixed in 2.9.13+dfsg-1ubuntu0.6 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-38427 | CRITICAL9.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48522 | CRITICAL9.8 | perl-modules-5.34 5.34.0-3ubuntu1.2 fixed in 5.34.0-3ubuntu1.3 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-44487 | CRITICAL9.75 | libnghttp2-14 1.43.0-1build3 fixed in 1.43.0-1ubuntu0.1 | 100.0% Actively Exploited | Directly Exposed |
| CVE-2024-6119 | CRITICAL9.75 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.18 | 66.6% Actively Exploited | Directly Exposed |
| CVE-2025-27363 | CRITICAL9.31 | libfreetype6 2.11.1+dfsg-1ubuntu0.2 fixed in 2.11.1+dfsg-1ubuntu0.3 | 26.0% High Exploitation Risk | Directly Exposed |
| CVE-2024-26594 | CRITICAL9.23 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 78.4% Actively Exploited | Directly Exposed |
| CVE-2024-37371 | CRITICAL9.1 | libgssapi-krb5-2 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.4 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-37371 | CRITICAL9.1 | libk5crypto3 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.4 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-37371 | CRITICAL9.1 | libkrb5-3 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.4 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-37371 | CRITICAL9.1 | libkrb5support0 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.4 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-46848 | CRITICAL9.1 | libtasn1-6 4.18.0-4build1 fixed in 4.18.0-4ubuntu0.2 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-49796 | CRITICAL9.1 | libxml2 2.9.13+dfsg-1ubuntu0.3 fixed in 2.9.13+dfsg-1ubuntu0.8 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-47685 | CRITICAL9.1 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-38430 | CRITICAL9.1 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-38431 | CRITICAL9.1 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54058 | CRITICAL9.1 | Pillow 10.1.0 fixed in 12.3.0 | — | Directly Exposed |
| CVE-2023-2640 | HIGH8.97 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-177.187 | 15.8% High Exploitation Risk | Directly Exposed |
| CVE-2024-1086 | HIGH8.97 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-101.111 | 28.1% High Exploitation Risk | Directly Exposed |
| CVE-2023-52755 | HIGH8.97 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 26.9% High Exploitation Risk | Directly Exposed |
| CVE-2024-7055 | HIGH8.8 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-7055 | HIGH8.8 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-7055 | HIGH8.8 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-7055 | HIGH8.8 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-7055 | HIGH8.8 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-1580 | HIGH8.8 | libdav1d5 0.9.2-1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-29509 | HIGH8.8 | libgs9 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.9 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33871 | HIGH8.8 | libgs9 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.7 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-29509 | HIGH8.8 | libgs9-common 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.9 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33871 | HIGH8.8 | libgs9-common 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.7 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-7055 | HIGH8.8 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-7055 | HIGH8.8 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-7055 | HIGH8.8 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-12351 | HIGH8.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-130.140 | 7.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5178 | HIGH8.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 9.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-8805 | HIGH8.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-40962 | HIGH8.33 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40962 | HIGH8.33 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40962 | HIGH8.33 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40962 | HIGH8.33 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40962 | HIGH8.33 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40393 | HIGH8.33 | libgbm1 23.0.4-0ubuntu1~22.04.1 fixed in 23.2.1-1ubuntu3.1~22.04.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-40393 | HIGH8.33 | libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 fixed in 23.2.1-1ubuntu3.1~22.04.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-40393 | HIGH8.33 | libglapi-mesa 23.0.4-0ubuntu1~22.04.1 fixed in 23.2.1-1ubuntu3.1~22.04.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-14087 | HIGH8.33 | libglib2.0-0 2.72.4-0ubuntu2.2 fixed in 2.72.4-0ubuntu2.7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-40393 | HIGH8.33 | libglx-mesa0 23.0.4-0ubuntu1~22.04.1 fixed in 23.2.1-1ubuntu3.1~22.04.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8376 | HIGH8.33 | libperl5.34 5.34.0-3ubuntu1.2 fixed in 5.34.0-3ubuntu1.7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-40962 | HIGH8.33 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | HIGH8.33 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.23 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40962 | HIGH8.33 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40962 | HIGH8.33 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6653 | HIGH8.33 | libxml2 2.9.13+dfsg-1ubuntu0.3 fixed in 2.9.13+dfsg-1ubuntu0.12 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23112 | HIGH8.33 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-177.187 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-25775 | HIGH8.33 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-89.99 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-8376 | HIGH8.33 | perl-modules-5.34 5.34.0-3ubuntu1.2 fixed in 5.34.0-3ubuntu1.7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42284 | HIGH8.33 | GitPython 3.1.40 fixed in 3.1.47 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-66034 | HIGH8.33 | fonttools 4.43.1 fixed in 4.60.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-22415 | HIGH8.33 | jupyter-lsp 2.2.0 fixed in 2.2.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-27459 | HIGH8.33 | pyOpenSSL 23.2.0 fixed in 26.0.0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-32988 | HIGH8.2 | libgnutls30 3.7.3-4ubuntu1.2 fixed in 3.7.3-4ubuntu1.7 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-59197 | HIGH8.2 | Pillow 10.1.0 fixed in 12.3.0 | — | Directly Exposed |
| CVE-2026-42557 | HIGH8.16 | jupyterlab 4.0.7 fixed in 4.5.7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42557 | HIGH8.16 | notebook 7.0.6 fixed in 7.5.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-3964 | HIGH8.1 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48434 | HIGH8.1 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3964 | HIGH8.1 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48434 | HIGH8.1 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3964 | HIGH8.1 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48434 | HIGH8.1 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3964 | HIGH8.1 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48434 | HIGH8.1 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3964 | HIGH8.1 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48434 | HIGH8.1 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3964 | HIGH8.1 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48434 | HIGH8.1 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2025-5318 | HIGH8.1 | libssh-4 0.9.6-2ubuntu0.22.04.1 fixed in 0.9.6-2ubuntu0.22.04.4 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-5318 | HIGH8.1 | libssh-gcrypt-4 0.9.6-2ubuntu0.22.04.1 fixed in 0.9.6-2ubuntu0.22.04.4 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45447 | HIGH8.1 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.25 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3964 | HIGH8.1 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48434 | HIGH8.1 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3964 | HIGH8.1 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48434 | HIGH8.1 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-1194 | HIGH8.1 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-32250 | HIGH8.1 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-32254 | HIGH8.1 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-32257 | HIGH8.1 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-32258 | HIGH8.1 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-50447 | HIGH8.1 | Pillow 10.1.0 fixed in 10.2.0 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9587 | HIGH7.8 | libkpathsea6 2021.20210626.59705-1ubuntu0.1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9588 | HIGH7.8 | libkpathsea6 2021.20210626.59705-1ubuntu0.1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3575 | HIGH7.8 | libopenjp2-7 2.4.0-6 fixed in 2.4.0-6ubuntu0.2 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9587 | HIGH7.8 | libptexenc1 2021.20210626.59705-1ubuntu0.1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9588 | HIGH7.8 | libptexenc1 2021.20210626.59705-1ubuntu0.1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9587 | HIGH7.8 | libsynctex2 2021.20210626.59705-1ubuntu0.1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9588 | HIGH7.8 | libsynctex2 2021.20210626.59705-1ubuntu0.1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9587 | HIGH7.8 | libtexlua53 2021.20210626.59705-1ubuntu0.1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9588 | HIGH7.8 | libtexlua53 2021.20210626.59705-1ubuntu0.1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9587 | HIGH7.8 | libtexluajit2 2021.20210626.59705-1ubuntu0.1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9588 | HIGH7.8 | libtexluajit2 2021.20210626.59705-1ubuntu0.1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0995 | HIGH7.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-138.148 | 6.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-32629 | HIGH7.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-177.187 | 8.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26581 | HIGH7.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-105.115 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-36971 | HIGH7.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-53104 | HIGH7.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-37924 | HIGH7.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 9.8% Low-Moderate Risk | Directly Exposed |
| CVE-2025-38352 | HIGH7.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-46300 | HIGH7.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-181.191 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-46333 | HIGH7.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-181.191 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2013-7445 | HIGH7.8 | linux-libc-dev 5.15.0-87.97 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-36886 | HIGH7.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-64600 | HIGH7.8 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2019-19378 | HIGH7.8 | linux-libc-dev 5.15.0-87.97 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19814 | HIGH7.8 | linux-libc-dev 5.15.0-87.97 No fix yet | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33845 | HIGH7.73 | libgnutls30 3.7.3-4ubuntu1.2 fixed in 3.7.3-4ubuntu1.9 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | HIGH7.73 | libperl5.34 5.34.0-3ubuntu1.2 fixed in 5.34.0-3ubuntu1.7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | HIGH7.73 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.25 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-5197 | HIGH7.73 | libvpx7 1.11.0-2ubuntu2.2 fixed in 1.11.0-2ubuntu2.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-49794 | HIGH7.73 | libxml2 2.9.13+dfsg-1ubuntu0.3 fixed in 2.9.13+dfsg-1ubuntu0.8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | HIGH7.73 | perl-modules-5.34 5.34.0-3ubuntu1.2 fixed in 5.34.0-3ubuntu1.7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-48795 | HIGH7.67 | libssh-4 0.9.6-2ubuntu0.22.04.1 fixed in 0.9.6-2ubuntu0.22.04.2 | 93.3% Actively Exploited | Directly Exposed |
| CVE-2023-48795 | HIGH7.67 | libssh-gcrypt-4 0.9.6-2ubuntu0.22.04.1 fixed in 0.9.6-2ubuntu0.22.04.2 | 93.3% Actively Exploited | Directly Exposed |
| CVE-2026-54527 | HIGH7.65 | jupyterlab-git 0.41.0 fixed in 0.54.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | libc-bin 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.8 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | libc-dev-bin 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.8 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | libc6 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.8 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | libc6-dev 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.8 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3109 | HIGH7.5 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3109 | HIGH7.5 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3109 | HIGH7.5 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3109 | HIGH7.5 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3109 | HIGH7.5 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5156 | HIGH7.5 | libc-bin 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.5 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5156 | HIGH7.5 | libc-dev-bin 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.5 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5156 | HIGH7.5 | libc6 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.5 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5156 | HIGH7.5 | libc6-dev 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.5 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-9814 | HIGH7.5 | libcairo-gobject2 1.16.0-5ubuntu2 fixed in 1.16.0-5ubuntu2.1 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2017-9814 | HIGH7.5 | libcairo2 1.16.0-5ubuntu2 fixed in 1.16.0-5ubuntu2.1 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-22483 | HIGH7.5 | libcmark-gfm-extensions0.29.0.gfm.3 0.29.0.gfm.3-3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-22486 | HIGH7.5 | libcmark-gfm-extensions0.29.0.gfm.3 0.29.0.gfm.3-3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-26485 | HIGH7.5 | libcmark-gfm-extensions0.29.0.gfm.3 0.29.0.gfm.3-3 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-22483 | HIGH7.5 | libcmark-gfm0.29.0.gfm.3 0.29.0.gfm.3-3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-22486 | HIGH7.5 | libcmark-gfm0.29.0.gfm.3 0.29.0.gfm.3-3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-26485 | HIGH7.5 | libcmark-gfm0.29.0.gfm.3 0.29.0.gfm.3-3 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-52425 | HIGH7.5 | libexpat1 2.4.7-1ubuntu0.2 fixed in 2.4.7-1ubuntu0.3 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28757 | HIGH7.5 | libexpat1 2.4.7-1ubuntu0.2 fixed in 2.4.7-1ubuntu0.3 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-45490 | HIGH7.5 | libexpat1 2.4.7-1ubuntu0.2 fixed in 2.4.7-1ubuntu0.4 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-8176 | HIGH7.5 | libexpat1 2.4.7-1ubuntu0.2 fixed in 2.4.7-1ubuntu0.6 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-7345 | HIGH7.5 | libgdk-pixbuf-2.0-0 2.42.8+dfsg-1ubuntu0.2 fixed in 2.42.8+dfsg-1ubuntu0.4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5201 | HIGH7.5 | libgdk-pixbuf-2.0-0 2.42.8+dfsg-1ubuntu0.2 fixed in 2.42.8+dfsg-1ubuntu0.5 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-7345 | HIGH7.5 | libgdk-pixbuf2.0-common 2.42.8+dfsg-1ubuntu0.2 fixed in 2.42.8+dfsg-1ubuntu0.4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5201 | HIGH7.5 | libgdk-pixbuf2.0-common 2.42.8+dfsg-1ubuntu0.2 fixed in 2.42.8+dfsg-1ubuntu0.5 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0553 | HIGH7.5 | libgnutls30 3.7.3-4ubuntu1.2 fixed in 3.7.3-4ubuntu1.4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0567 | HIGH7.5 | libgnutls30 3.7.3-4ubuntu1.2 fixed in 3.7.3-4ubuntu1.4 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33846 | HIGH7.5 | libgnutls30 3.7.3-4ubuntu1.2 fixed in 3.7.3-4ubuntu1.9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42009 | HIGH7.5 | libgnutls30 3.7.3-4ubuntu1.2 fixed in 3.7.3-4ubuntu1.9 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-46751 | HIGH7.5 | libgs9 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.6 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-46751 | HIGH7.5 | libgs9-common 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.6 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-25193 | HIGH7.5 | libharfbuzz0b 2.7.4-1ubuntu3.1 fixed in 2.7.4-1ubuntu3.2 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2953 | HIGH7.5 | libldap-2.5-0 2.5.16+dfsg-0ubuntu0.22.04.1 fixed in 2.5.16+dfsg-0ubuntu0.22.04.2 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33416 | HIGH7.5 | libpng16-16 1.6.37-3build5 fixed in 1.6.37-3ubuntu0.5 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3109 | HIGH7.5 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-6232 | HIGH7.5 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.6 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13836 | HIGH7.5 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.13 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-7592 | HIGH7.5 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.6 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-6232 | HIGH7.5 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.6 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13836 | HIGH7.5 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.13 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-7592 | HIGH7.5 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.6 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-4743 | HIGH7.5 | libsdl2-2.0-0 2.0.20+dfsg-2ubuntu1.22.04.1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-40735 | HIGH7.5 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.16 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5363 | HIGH7.5 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.12 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3109 | HIGH7.5 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3109 | HIGH7.5 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-52356 | HIGH7.5 | libtiff5 4.3.0-6ubuntu0.6 fixed in 4.3.0-6ubuntu0.8 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-7006 | HIGH7.5 | libtiff5 4.3.0-6ubuntu0.6 fixed in 4.3.0-6ubuntu0.10 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-25062 | HIGH7.5 | libxml2 2.9.13+dfsg-1ubuntu0.3 fixed in 2.9.13+dfsg-1ubuntu0.4 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-27113 | HIGH7.5 | libxml2 2.9.13+dfsg-1ubuntu0.3 fixed in 2.9.13+dfsg-1ubuntu0.6 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-6021 | HIGH7.5 | libxml2 2.9.13+dfsg-1ubuntu0.3 fixed in 2.9.13+dfsg-1ubuntu0.8 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-4899 | HIGH7.5 | libzstd1 1.4.8+dfsg-3build1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0400 | HIGH7.5 | linux-libc-dev 5.15.0-87.97 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-32247 | HIGH7.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-101.111 | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-32252 | HIGH7.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 4.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-39179 | HIGH7.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-39180 | HIGH7.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-46838 | HIGH7.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6356 | HIGH7.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6535 | HIGH7.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6536 | HIGH7.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-49997 | HIGH7.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-38501 | HIGH7.5 | linux-libc-dev 5.15.0-87.97 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20426 | HIGH7.5 | linux-libc-dev 5.15.0-87.97 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-6232 | HIGH7.5 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.6 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13836 | HIGH7.5 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.13 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-7592 | HIGH7.5 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.6 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-6232 | HIGH7.5 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.6 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13836 | HIGH7.5 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.13 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-7592 | HIGH7.5 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.6 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-64756 | HIGH7.5 | glob 10.3.3 fixed in 11.1.0, 10.5.0 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-59199 | HIGH7.5 | Pillow 10.1.0 fixed in 12.3.0 | — | Directly Exposed |
| CVE-2026-59200 | HIGH7.5 | Pillow 10.1.0 fixed in 12.3.0 | — | Directly Exposed |
| CVE-2026-59204 | HIGH7.5 | Pillow 10.1.0 fixed in 12.3.0 | — | Directly Exposed |
| CVE-2026-59205 | HIGH7.5 | Pillow 10.1.0 fixed in 12.3.0 | — | Directly Exposed |
| CVE-2026-59198 | HIGH7.5 | Pillow 10.1.0 fixed in 12.3.0 | — | Directly Exposed |
| CVE-2024-39689 | HIGH7.5 | certifi 2023.7.22 fixed in 2024.7.4 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-50782 | HIGH7.5 | cryptography 41.0.4 fixed in 42.0.0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-3651 | HIGH7.5 | idna 3.4 fixed in 3.7 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-49477 | HIGH7.5 | soupsieve 2.5 fixed in 2.8.4 | — | Directly Exposed |
| CVE-2024-52804 | HIGH7.5 | tornado 6.3.3 fixed in 6.4.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-21441 | HIGH7.5 | urllib3 2.0.7 fixed in 2.6.3 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1594 | HIGH7.48 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1594 | HIGH7.48 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1594 | HIGH7.48 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1594 | HIGH7.48 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1594 | HIGH7.48 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-29506 | HIGH7.48 | libgs9 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.9 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-29506 | HIGH7.48 | libgs9-common 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.9 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-1594 | HIGH7.48 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-5372 | HIGH7.48 | libssh-4 0.9.6-2ubuntu0.22.04.1 fixed in 0.9.6-2ubuntu0.22.04.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-5372 | HIGH7.48 | libssh-gcrypt-4 0.9.6-2ubuntu0.22.04.1 fixed in 0.9.6-2ubuntu0.22.04.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1594 | HIGH7.48 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1594 | HIGH7.48 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-9900 | HIGH7.48 | libtiff5 4.3.0-6ubuntu0.6 fixed in 4.3.0-6ubuntu0.12 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-43037 | HIGH7.48 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-23395 | HIGH7.48 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-25744 | HIGH7.48 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47659 | HIGH7.48 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-56201 | HIGH7.48 | Jinja2 3.1.2 fixed in 3.1.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-27516 | HIGH7.48 | Jinja2 3.1.2 fixed in 3.1.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-35397 | HIGH7.48 | jupyter_server 2.8.0 fixed in 2.18.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6657 | HIGH7.48 | jupyter_server 2.8.0 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40171 | HIGH7.48 | jupyterlab 4.0.7 fixed in 4.5.7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42266 | HIGH7.48 | jupyterlab 4.0.7 fixed in 4.5.7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40171 | HIGH7.48 | notebook 7.0.6 fixed in 7.5.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-0565 | HIGH7.4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-97.107 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-7104 | HIGH7.3 | libsqlite3-0 3.37.2-2ubuntu0.1 fixed in 3.37.2-2ubuntu0.3 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-12360 | HIGH7.1 | libkpathsea6 2021.20210626.59705-1ubuntu0.1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-12493 | HIGH7.1 | libkpathsea6 2021.20210626.59705-1ubuntu0.1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-12360 | HIGH7.1 | libptexenc1 2021.20210626.59705-1ubuntu0.1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-12493 | HIGH7.1 | libptexenc1 2021.20210626.59705-1ubuntu0.1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-4156 | HIGH7.1 | libsndfile1 1.0.31-2build1 fixed in 1.0.31-2ubuntu0.2 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-12360 | HIGH7.1 | libsynctex2 2021.20210626.59705-1ubuntu0.1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-12493 | HIGH7.1 | libsynctex2 2021.20210626.59705-1ubuntu0.1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-12360 | HIGH7.1 | libtexlua53 2021.20210626.59705-1ubuntu0.1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-12493 | HIGH7.1 | libtexlua53 2021.20210626.59705-1ubuntu0.1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-12360 | HIGH7.1 | libtexluajit2 2021.20210626.59705-1ubuntu0.1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-12493 | HIGH7.1 | libtexluajit2 2021.20210626.59705-1ubuntu0.1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-53150 | HIGH7.1 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3867 | HIGH7.1 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-52533 | HIGH7 | libglib2.0-0 2.72.4-0ubuntu2.2 fixed in 2.72.4-0ubuntu2.4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-53381 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-53384 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-53388 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-53391 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-53392 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-53393 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-53397 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-53398 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-53399 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63794 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63800 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63801 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63807 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63808 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63809 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63823 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63824 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63826 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63829 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63830 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63831 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63875 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63887 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63888 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63889 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63891 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63898 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63899 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63901 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63912 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63913 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63914 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63916 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63917 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63919 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63920 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63921 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63922 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63924 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63925 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63928 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63940 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63947 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63956 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63957 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63958 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63962 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63971 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63975 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63984 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63992 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63993 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63994 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64001 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64002 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64007 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64009 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64011 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64015 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64018 | HIGH7 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64025 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64026 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64032 | HIGH7 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64034 | HIGH7 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64047 | HIGH7 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64048 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64098 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64102 | HIGH7 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64109 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64111 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64113 | HIGH7 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64114 | HIGH7 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64115 | HIGH7 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64137 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64174 | HIGH7 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64189 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64191 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64192 | HIGH7 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2025-32990 | MEDIUM6.97 | libgnutls30 3.7.3-4ubuntu1.2 fixed in 3.7.3-4ubuntu1.7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42013 | MEDIUM6.97 | libgnutls30 3.7.3-4ubuntu1.2 fixed in 3.7.3-4ubuntu1.9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM6.97 | libgnutls30 3.7.3-4ubuntu1.2 fixed in 3.7.3-4ubuntu1.9 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-52194 | MEDIUM6.97 | libsndfile1 1.0.31-2build1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-37555 | MEDIUM6.97 | libsndfile1 1.0.31-2build1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0966 | MEDIUM6.97 | libssh-4 0.9.6-2ubuntu0.22.04.1 fixed in 0.9.6-2ubuntu0.22.04.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-0966 | MEDIUM6.97 | libssh-gcrypt-4 0.9.6-2ubuntu0.22.04.1 fixed in 0.9.6-2ubuntu0.22.04.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-31788 | MEDIUM6.97 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-28182 | MEDIUM6.89 | libnghttp2-14 1.43.0-1build3 fixed in 1.43.0-1ubuntu0.2 | 85.0% Actively Exploited | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc-bin 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.13 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc-dev-bin 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.13 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc6 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.13 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc6-dev 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.13 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25646 | MEDIUM6.88 | libpng16-16 1.6.37-3build5 fixed in 1.6.37-3ubuntu0.4 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-6100 | MEDIUM6.88 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6100 | MEDIUM6.88 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.23 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-5283 | MEDIUM6.88 | libvpx7 1.11.0-2ubuntu2.2 fixed in 1.11.0-2ubuntu2.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-58087 | MEDIUM6.88 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43114 | MEDIUM6.88 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43112 | MEDIUM6.88 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6100 | MEDIUM6.88 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6100 | MEDIUM6.88 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-5422 | MEDIUM6.88 | jupyter_server 2.8.0 fixed in 2.18.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-58060 | MEDIUM6.8 | libcups2 2.4.1op1-1ubuntu4.7 fixed in 2.4.1op1-1ubuntu4.12 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-52434 | MEDIUM6.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-0938 | MEDIUM6.8 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2025-0938 | MEDIUM6.8 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24023 | MEDIUM6.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-105.115 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-0938 | MEDIUM6.8 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2025-0938 | MEDIUM6.8 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2025-15467 | MEDIUM6.76 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.21 | 47.6% High Exploitation Risk | Post-Exploit |
| CVE-2026-43133 | MEDIUM6.71 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-35235 | MEDIUM6.7 | libcups2 2.4.1op1-1ubuntu4.7 fixed in 2.4.1op1-1ubuntu4.9 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15794 | MEDIUM6.7 | linux-libc-dev 5.15.0-87.97 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-32230 | MEDIUM6.63 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-32230 | MEDIUM6.63 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-32230 | MEDIUM6.63 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-32230 | MEDIUM6.63 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-32230 | MEDIUM6.63 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-44840 | MEDIUM6.63 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-45703 | MEDIUM6.63 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-47695 | MEDIUM6.63 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-44840 | MEDIUM6.63 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-45703 | MEDIUM6.63 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-47695 | MEDIUM6.63 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-44840 | MEDIUM6.63 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-45703 | MEDIUM6.63 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-47695 | MEDIUM6.63 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1372 | MEDIUM6.63 | libelf1 0.186-1build1 fixed in 0.186-1ubuntu0.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25210 | MEDIUM6.63 | libexpat1 2.4.7-1ubuntu0.2 fixed in 2.4.7-1ubuntu0.7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48622 | MEDIUM6.63 | libgdk-pixbuf-2.0-0 2.42.8+dfsg-1ubuntu0.2 fixed in 2.42.8+dfsg-1ubuntu0.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-48622 | MEDIUM6.63 | libgdk-pixbuf2.0-common 2.42.8+dfsg-1ubuntu0.2 fixed in 2.42.8+dfsg-1ubuntu0.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-46951 | MEDIUM6.63 | libgs9 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-46952 | MEDIUM6.63 | libgs9 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46953 | MEDIUM6.63 | libgs9 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-46956 | MEDIUM6.63 | libgs9 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-46951 | MEDIUM6.63 | libgs9-common 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-46952 | MEDIUM6.63 | libgs9-common 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46953 | MEDIUM6.63 | libgs9-common 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-46956 | MEDIUM6.63 | libgs9-common 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-24106 | MEDIUM6.63 | libkpathsea6 2021.20210626.59705-1ubuntu0.1 fixed in 2021.20210626.59705-1ubuntu0.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-24107 | MEDIUM6.63 | libkpathsea6 2021.20210626.59705-1ubuntu0.1 fixed in 2021.20210626.59705-1ubuntu0.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-45221 | MEDIUM6.63 | libmfx1 22.3.0-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | MEDIUM6.63 | libncurses6 6.3-2ubuntu0.1 fixed in 6.3-2ubuntu0.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | MEDIUM6.63 | libncursesw6 6.3-2ubuntu0.1 fixed in 6.3-2ubuntu0.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6020 | MEDIUM6.63 | libpam-modules 1.4.0-11ubuntu2.3 fixed in 1.4.0-11ubuntu2.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6020 | MEDIUM6.63 | libpam-modules-bin 1.4.0-11ubuntu2.3 fixed in 1.4.0-11ubuntu2.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6020 | MEDIUM6.63 | libpam-runtime 1.4.0-11ubuntu2.3 fixed in 1.4.0-11ubuntu2.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6020 | MEDIUM6.63 | libpam0g 1.4.0-11ubuntu2.3 fixed in 1.4.0-11ubuntu2.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-47038 | MEDIUM6.63 | libperl5.34 5.34.0-3ubuntu1.2 fixed in 5.34.0-3ubuntu1.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22801 | MEDIUM6.63 | libpng16-16 1.6.37-3build5 fixed in 1.6.37-3ubuntu0.3 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-32230 | MEDIUM6.63 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-24106 | MEDIUM6.63 | libptexenc1 2021.20210626.59705-1ubuntu0.1 fixed in 2021.20210626.59705-1ubuntu0.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-24107 | MEDIUM6.63 | libptexenc1 2021.20210626.59705-1ubuntu0.1 fixed in 2021.20210626.59705-1ubuntu0.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6597 | MEDIUM6.63 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-9287 | MEDIUM6.63 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-6597 | MEDIUM6.63 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-9287 | MEDIUM6.63 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-33065 | MEDIUM6.63 | libsndfile1 1.0.31-2build1 fixed in 1.0.31-2ubuntu0.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-32230 | MEDIUM6.63 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-32230 | MEDIUM6.63 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-24106 | MEDIUM6.63 | libsynctex2 2021.20210626.59705-1ubuntu0.1 fixed in 2021.20210626.59705-1ubuntu0.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-24107 | MEDIUM6.63 | libsynctex2 2021.20210626.59705-1ubuntu0.1 fixed in 2021.20210626.59705-1ubuntu0.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | libsystemd0 249.11-0ubuntu3.10 fixed in 249.11-0ubuntu3.19 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-24106 | MEDIUM6.63 | libtexlua53 2021.20210626.59705-1ubuntu0.1 fixed in 2021.20210626.59705-1ubuntu0.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-24107 | MEDIUM6.63 | libtexlua53 2021.20210626.59705-1ubuntu0.1 fixed in 2021.20210626.59705-1ubuntu0.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-24106 | MEDIUM6.63 | libtexluajit2 2021.20210626.59705-1ubuntu0.1 fixed in 2021.20210626.59705-1ubuntu0.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-24107 | MEDIUM6.63 | libtexluajit2 2021.20210626.59705-1ubuntu0.1 fixed in 2021.20210626.59705-1ubuntu0.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8176 | MEDIUM6.63 | libtiff5 4.3.0-6ubuntu0.6 fixed in 4.3.0-6ubuntu0.11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | MEDIUM6.63 | libtinfo6 6.3-2ubuntu0.1 fixed in 6.3-2ubuntu0.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | libudev1 249.11-0ubuntu3.10 fixed in 249.11-0ubuntu3.19 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49043 | MEDIUM6.63 | libxml2 2.9.13+dfsg-1ubuntu0.3 fixed in 2.9.13+dfsg-1ubuntu0.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7425 | MEDIUM6.63 | libxml2 2.9.13+dfsg-1ubuntu0.3 fixed in 2.9.13+dfsg-1ubuntu0.10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37777 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38724 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71068 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23216 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31402 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-21546 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49359 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49910 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49935 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50095 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50212 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50213 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50234 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52664 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-139.149 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52927 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-139.149 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-53305 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53338 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53485 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53554 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53629 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53673 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-6817 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-92.102 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-0646 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-97.107 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-1085 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-101.111 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26689 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26800 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26928 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-136.147 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27398 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-35864 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-136.147 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38630 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-124.134 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49883 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50047 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-143.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50264 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-130.140 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-53103 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-131.141 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53168 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-141.151 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53171 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53179 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56551 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-141.151 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56581 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56595 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56596 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56598 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56608 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-141.151 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56616 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56619 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56640 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56658 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-136.147 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56759 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57798 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-136.147 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57850 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57900 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-58055 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21692 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-21704 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-21715 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21735 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21772 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21780 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-171.181 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21791 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21812 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21858 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21968 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22040 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-22041 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-22056 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23142 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37738 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37778 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-37823 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37839 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37849 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-174.184 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37899 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-37913 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37914 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37926 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37952 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38024 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38068 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-152.162 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38079 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-152.162 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38129 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38146 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38180 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38211 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38212 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38226 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38230 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38236 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38248 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38257 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38323 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38348 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38349 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38377 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38401 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38416 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38437 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38464 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38494 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38550 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38552 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38563 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-38572 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38666 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38685 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38697 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38707 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39730 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39743 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39790 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39824 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39828 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39841 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39860 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39863 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39864 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39866 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-39952 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39967 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40149 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68817 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71073 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71082 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71089 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71162 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23001 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23074 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-174.184 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23111 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-174.184 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23171 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23208 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23209 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23226 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23227 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23378 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23410 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23411 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23428 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31532 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31709 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31720 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31729 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31759 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43049 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43329 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43378 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43499 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45891 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46274 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53148 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53262 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53359 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2020-14356 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-3238 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48744 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48771 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48990 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48998 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49471 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49635 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-50070 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50071 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50090 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50163 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50240 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50303 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-0030 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-2007 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-26242 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-51042 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52436 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52438 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52439 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52441 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-52444 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52445 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52451 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52452 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52457 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52464 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52475 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52482 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52483 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52491 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52494 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52509 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52510 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52515 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52524 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52530 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-107.117 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52531 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52572 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52594 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52599 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52600 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-105.115 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52603 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-105.115 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52604 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52612 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52614 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52621 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52624 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-52637 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52667 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52669 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52679 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52691 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52748 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52751 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52752 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-117.127 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52757 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52760 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-119.129 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52764 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52772 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52775 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52796 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52799 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52804 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52816 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52818 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52835 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52836 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52837 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52840 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52846 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52852 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52854 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52859 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52864 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52867 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52868 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52916 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52921 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53037 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53072 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53148 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53187 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53192 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53215 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53218 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53257 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53386 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53395 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53426 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53454 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53487 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53495 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53500 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53559 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-54207 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-5717 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-6040 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-92.102 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-22705 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26589 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26592 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26598 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26610 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26622 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-107.117 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26625 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26699 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26704 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26736 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26739 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26742 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26748 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26749 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26754 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26782 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26792 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26793 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26842 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26856 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26882 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26883 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26884 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26885 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26898 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26907 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26934 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26936 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26951 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26952 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-117.127 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26955 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26956 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26957 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26958 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26961 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26965 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26981 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26988 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26989 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26996 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27000 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27008 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27018 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27024 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27043 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27045 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27065 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27075 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27395 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27396 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35789 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35791 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35847 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35855 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35862 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-179.189 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35866 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35867 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35886 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35905 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35932 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35949 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36012 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36015 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36880 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36898 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36904 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-36906 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36914 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36921 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36934 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36940 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36974 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36978 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38545 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38552 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38555 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38556 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38570 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-122.132 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38577 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38578 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38583 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38586 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38588 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38610 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38627 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38667 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39277 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39463 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-39494 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-122.132 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-39495 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-39496 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-122.132 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-39502 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40900 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40901 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40902 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40927 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40954 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40956 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40958 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40974 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40989 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40994 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41011 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41042 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41045 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41046 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41050 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41069 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41070 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41073 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41074 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41087 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41092 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42086 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42092 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42105 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42117 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42118 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42119 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42120 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42121 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42147 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42148 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42160 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-122.132 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42271 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42280 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42284 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42285 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42301 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42302 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42313 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43830 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43839 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-43842 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43858 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43873 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43900 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44934 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44940 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44942 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44974 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-44985 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-44986 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44987 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-44998 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-45026 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46673 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46713 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46725 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46729 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46738 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46740 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46744 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46746 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46759 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46782 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46798 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46800 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46804 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46811 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46812 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46813 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46814 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46815 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46818 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46820 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46821 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46828 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46830 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46833 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46836 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46844 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46849 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46852 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46853 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46859 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46871 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47670 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47695 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47696 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47697 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47698 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47701 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47718 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47730 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47742 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47745 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47748 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49852 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49880 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49882 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49884 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49889 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49894 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49895 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49924 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49930 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49931 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49936 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49950 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49960 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49966 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49969 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49982 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49983 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49989 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49991 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49992 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49996 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50007 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50051 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50055 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50063 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50067 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-164.174 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50073 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-151.161 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50074 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50112 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50121 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50125 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50127 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50131 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50143 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50150 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50151 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50180 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50186 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50209 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50230 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50242 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50246 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50257 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50262 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50267 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50269 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50282 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50283 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53057 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-130.140 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53059 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53061 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53068 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53096 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53098 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53133 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53141 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-131.141 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-53142 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53156 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53165 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53173 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53203 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53206 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53227 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53237 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53239 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56538 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56548 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56570 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56600 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56604 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56606 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56614 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56615 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56626 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56631 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56642 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56651 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-138.148 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57792 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57917 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57951 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57980 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58002 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58069 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58240 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21631 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21680 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21687 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21756 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-138.148 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-21855 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-164.174 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21914 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21919 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21927 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21945 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21967 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22020 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22022 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37752 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-153.163 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37789 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37796 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37797 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37798 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-143.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37890 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-143.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37903 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37928 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-37947 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38000 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-143.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38022 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38052 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-152.162 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38157 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38201 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38227 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38350 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-153.163 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38369 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38389 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38403 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38476 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38574 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38579 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38618 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-157.167 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38718 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38729 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38734 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39691 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39766 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39776 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39873 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39955 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40258 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40277 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-71078 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71091 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71238 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23078 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23083 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23089 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23098 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23193 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23281 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23408 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23447 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23448 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31452 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31578 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31581 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31696 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43196 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43250 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45839 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45902 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45916 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45920 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45936 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45946 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45984 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46004 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46047 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46068 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46069 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46075 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46122 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46163 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46180 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46189 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46219 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46234 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46241 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46243 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52943 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52962 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52969 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52992 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53004 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53136 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53137 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53294 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53296 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-13165 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-12930 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-12931 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-26934 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49722 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49980 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50256 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50406 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50492 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50518 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50552 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-22995 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-33053 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52469 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52642 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52805 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52922 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-53052 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53145 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53286 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53311 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53320 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53331 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53432 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53510 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53515 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53541 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53544 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53556 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53577 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53596 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53616 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53676 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-0841 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-23307 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-26895 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26983 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35868 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35887 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39480 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41000 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42104 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47691 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-164.174 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50217 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53214 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53218 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-164.174 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56601 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56602 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56603 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56605 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56609 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56633 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56704 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56708 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57849 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57887 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57892 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57896 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57904 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58034 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58072 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58093 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21734 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21785 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-21811 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21863 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21915 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21928 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21934 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21991 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22083 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23133 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23158 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37786 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37803 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37810 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37817 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37819 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37822 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37840 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37861 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37885 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37892 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37923 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37927 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37957 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37991 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38069 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38077 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-152.162 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38117 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38118 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38131 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38154 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38206 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38239 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38245 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38250 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38259 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38280 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38298 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38313 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38346 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38361 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38375 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38415 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38422 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38428 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38443 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38459 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38485 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38488 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-38527 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38535 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38538 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38548 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38555 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38565 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38584 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38595 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38676 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-38699 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38702 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38708 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39686 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39689 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39738 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39783 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39788 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39797 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39810 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39823 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39835 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39859 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39880 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39911 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39913 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39945 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39951 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71075 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71086 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71137 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71152 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71220 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22980 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23068 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23073 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23221 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23234 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23262 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23359 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23361 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31399 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31455 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31485 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31489 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31493 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31500 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31527 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31576 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31580 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31583 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31686 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31702 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31715 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31747 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31748 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43015 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43020 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43027 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43205 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43328 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43426 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43458 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45866 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45867 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45879 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45885 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46267 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46285 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46294 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46301 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53059 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53089 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53112 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53115 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53117 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53120 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53129 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53156 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53157 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53195 | MEDIUM6.63 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | MEDIUM6.63 | ncurses-base 6.3-2ubuntu0.1 fixed in 6.3-2ubuntu0.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-47038 | MEDIUM6.63 | perl-modules-5.34 5.34.0-3ubuntu1.2 fixed in 5.34.0-3ubuntu1.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-6597 | MEDIUM6.63 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-9287 | MEDIUM6.63 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-6597 | MEDIUM6.63 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-9287 | MEDIUM6.63 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-22190 | MEDIUM6.63 | GitPython 3.1.40 fixed in 3.1.41 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-21759 | MEDIUM6.6 | linux-libc-dev 5.15.0-87.97 No fix yet | 7.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13601 | MEDIUM6.54 | libglib2.0-0 2.72.4-0ubuntu2.2 fixed in 2.72.4-0ubuntu2.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-24928 | MEDIUM6.54 | libxml2 2.9.13+dfsg-1ubuntu0.3 fixed in 2.9.13+dfsg-1ubuntu0.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-3826 | MEDIUM6.5 | gcc-11-base 11.4.0-1ubuntu1~22.04 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3826 | MEDIUM6.5 | libasan6 11.4.0-1ubuntu1~22.04 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0856 | MEDIUM6.5 | libcaca0 0.99.beta19-2.2ubuntu4 fixed in 0.99.beta19-2.2ubuntu4.1 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | MEDIUM6.5 | libcairo-gobject2 1.16.0-5ubuntu2 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6461 | MEDIUM6.5 | libcairo-gobject2 1.16.0-5ubuntu2 fixed in 1.16.0-5ubuntu2.1 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6462 | MEDIUM6.5 | libcairo-gobject2 1.16.0-5ubuntu2 fixed in 1.16.0-5ubuntu2.1 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | MEDIUM6.5 | libcairo2 1.16.0-5ubuntu2 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6461 | MEDIUM6.5 | libcairo2 1.16.0-5ubuntu2 fixed in 1.16.0-5ubuntu2.1 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6462 | MEDIUM6.5 | libcairo2 1.16.0-5ubuntu2 fixed in 1.16.0-5ubuntu2.1 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-39209 | MEDIUM6.5 | libcmark-gfm-extensions0.29.0.gfm.3 0.29.0.gfm.3-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-39209 | MEDIUM6.5 | libcmark-gfm0.29.0.gfm.3 0.29.0.gfm.3-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-58364 | MEDIUM6.5 | libcups2 2.4.1op1-1ubuntu4.7 fixed in 2.4.1op1-1ubuntu4.12 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-34969 | MEDIUM6.5 | libdbus-1-3 1.12.20-2ubuntu4.1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3826 | MEDIUM6.5 | libgcc-11-dev 11.4.0-1ubuntu1~22.04 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-40812 | MEDIUM6.5 | libgd3 2.3.0-2ubuntu2 fixed in 2.3.0-2ubuntu2.3 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libgssapi-krb5-2 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.3 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libk5crypto3 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.3 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libkrb5-3 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.3 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libkrb5support0 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.3 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6988 | MEDIUM6.5 | libopenjp2-7 2.4.0-6 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6129 | MEDIUM6.5 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.14 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3826 | MEDIUM6.5 | libstdc++-11-dev 11.4.0-1ubuntu1~22.04 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6277 | MEDIUM6.5 | libtiff5 4.3.0-6ubuntu0.6 fixed in 4.3.0-6ubuntu0.8 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3826 | MEDIUM6.5 | libtsan0 11.4.0-1ubuntu1~22.04 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-12352 | MEDIUM6.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-130.140 | 5.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-24490 | MEDIUM6.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-130.140 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-1193 | MEDIUM6.5 | linux-libc-dev 5.15.0-87.97 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-47692 | MEDIUM6.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28849 | MEDIUM6.5 | follow-redirects 1.15.2 fixed in 1.15.6 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-37891 | MEDIUM6.5 | urllib3 2.0.7 fixed in 1.26.19, 2.2.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33636 | MEDIUM6.46 | libpng16-16 1.6.37-3build5 fixed in 1.6.37-3ubuntu0.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-39971 | MEDIUM6.46 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-6603 | MEDIUM6.38 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-63757 | MEDIUM6.38 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6603 | MEDIUM6.38 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-63757 | MEDIUM6.38 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6603 | MEDIUM6.38 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-63757 | MEDIUM6.38 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6603 | MEDIUM6.38 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-63757 | MEDIUM6.38 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6603 | MEDIUM6.38 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-63757 | MEDIUM6.38 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-34980 | MEDIUM6.38 | libcups2 2.4.1op1-1ubuntu4.7 fixed in 2.4.1op1-1ubuntu4.20 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1352 | MEDIUM6.38 | libelf1 0.186-1build1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-41989 | MEDIUM6.38 | libgcrypt20 1.9.4-3ubuntu3 fixed in 1.9.4-3ubuntu3.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | libgssapi-krb5-2 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libgssapi-krb5-2 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libgssapi-krb5-2 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | libk5crypto3 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libk5crypto3 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libk5crypto3 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | libkrb5-3 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkrb5-3 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkrb5-3 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | libkrb5support0 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkrb5support0 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkrb5support0 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-27135 | MEDIUM6.38 | libnghttp2-14 1.43.0-1build3 fixed in 1.43.0-1ubuntu0.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-41409 | MEDIUM6.38 | libpcre2-8-0 10.39-3ubuntu0.1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-6603 | MEDIUM6.38 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-63757 | MEDIUM6.38 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69534 | MEDIUM6.38 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-8194 | MEDIUM6.38 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.11 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.38 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69534 | MEDIUM6.38 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-8194 | MEDIUM6.38 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.11 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.38 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3731 | MEDIUM6.38 | libssh-4 0.9.6-2ubuntu0.22.04.1 fixed in 0.9.6-2ubuntu0.22.04.7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3731 | MEDIUM6.38 | libssh-gcrypt-4 0.9.6-2ubuntu0.22.04.1 fixed in 0.9.6-2ubuntu0.22.04.7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.21 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM6.38 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.23 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM6.38 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.23 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.38 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.23 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-6603 | MEDIUM6.38 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-63757 | MEDIUM6.38 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6603 | MEDIUM6.38 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-63757 | MEDIUM6.38 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-2447 | MEDIUM6.38 | libvpx7 1.11.0-2ubuntu2.2 fixed in 1.11.0-2ubuntu2.5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-32414 | MEDIUM6.38 | libxml2 2.9.13+dfsg-1ubuntu0.3 fixed in 2.9.13+dfsg-1ubuntu0.7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-32415 | MEDIUM6.38 | libxml2 2.9.13+dfsg-1ubuntu0.3 fixed in 2.9.13+dfsg-1ubuntu0.7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-2173 | MEDIUM6.38 | libzvbi-common 0.2.35-19 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-2174 | MEDIUM6.38 | libzvbi-common 0.2.35-19 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-2176 | MEDIUM6.38 | libzvbi-common 0.2.35-19 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-2173 | MEDIUM6.38 | libzvbi0 0.2.35-19 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-2174 | MEDIUM6.38 | libzvbi0 0.2.35-19 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-2176 | MEDIUM6.38 | libzvbi0 0.2.35-19 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-43501 | MEDIUM6.38 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31669 | MEDIUM6.38 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43186 | MEDIUM6.38 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-46195 | MEDIUM6.38 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-53071 | MEDIUM6.38 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53266 | MEDIUM6.38 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-25836 | MEDIUM6.38 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-32256 | MEDIUM6.38 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-39176 | MEDIUM6.38 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4458 | MEDIUM6.38 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-45871 | MEDIUM6.38 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-89.99 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-52340 | MEDIUM6.38 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-36347 | MEDIUM6.38 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-42225 | MEDIUM6.38 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-50083 | MEDIUM6.38 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-57791 | MEDIUM6.38 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-39973 | MEDIUM6.38 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40210 | MEDIUM6.38 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40240 | MEDIUM6.38 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68349 | MEDIUM6.38 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22998 | MEDIUM6.38 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-43110 | MEDIUM6.38 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43190 | MEDIUM6.38 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69534 | MEDIUM6.38 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-8194 | MEDIUM6.38 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.11 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.38 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69534 | MEDIUM6.38 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-8194 | MEDIUM6.38 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.11 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.38 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-13149 | MEDIUM6.38 | brace-expansion 1.1.11 fixed in 5.0.7, 1.1.16, 2.1.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33750 | MEDIUM6.38 | brace-expansion 1.1.11 fixed in 5.0.5, 3.0.2, 2.0.3, 1.1.13 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13149 | MEDIUM6.38 | brace-expansion 2.0.1 fixed in 5.0.7, 1.1.16, 2.1.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33750 | MEDIUM6.38 | brace-expansion 2.0.1 fixed in 5.0.5, 3.0.2, 2.0.3, 1.1.13 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-26996 | MEDIUM6.38 | minimatch 3.1.2 fixed in 10.2.1, 9.0.6, 8.0.5, 7.4.7, 6.2.1, 5.1.7, 4.2.4, 3.1.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-26996 | MEDIUM6.38 | minimatch 9.0.3 fixed in 10.2.1, 9.0.6, 8.0.5, 7.4.7, 6.2.1, 5.1.7, 4.2.4, 3.1.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-6176 | MEDIUM6.38 | Brotli 1.1.0 fixed in 1.2.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-41205 | MEDIUM6.38 | Mako 1.2.4 fixed in 1.3.11 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54059 | MEDIUM6.38 | Pillow 10.1.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54060 | MEDIUM6.38 | Pillow 10.1.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-55379 | MEDIUM6.38 | Pillow 10.1.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-55380 | MEDIUM6.38 | Pillow 10.1.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32597 | MEDIUM6.38 | PyJWT 2.8.0 fixed in 2.12.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26130 | MEDIUM6.38 | cryptography 41.0.4 fixed in 42.0.4 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-49083 | MEDIUM6.38 | cryptography 41.0.4 fixed in 41.0.6 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-35178 | MEDIUM6.38 | jupyter_server 2.8.0 fixed in 2.14.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-33079 | MEDIUM6.38 | mistune 3.0.1 fixed in 3.2.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-49851 | MEDIUM6.38 | mistune 3.0.1 fixed in 3.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0994 | MEDIUM6.38 | protobuf 4.24.3 fixed in 6.33.5, 5.29.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-47287 | MEDIUM6.38 | tornado 6.3.3 fixed in 6.5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-31958 | MEDIUM6.38 | tornado 6.3.3 fixed in 6.5.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66418 | MEDIUM6.38 | urllib3 2.0.7 fixed in 2.6.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-66471 | MEDIUM6.38 | urllib3 2.0.7 fixed in 2.6.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-6387 | MEDIUM6.32 | openssh-client 1:8.9p1-3ubuntu0.4 fixed in 1:8.9p1-3ubuntu0.10 | 99.5% Actively Exploited | Post-Exploit |
| CVE-2024-29510 | MEDIUM6.32 | libgs9 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.7 | 28.0% High Exploitation Risk | Directly Exposed |
| CVE-2024-29510 | MEDIUM6.32 | libgs9-common 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.7 | 28.0% High Exploitation Risk | Directly Exposed |
| CVE-2025-21758 | MEDIUM6.32 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 13.0% High Exploitation Risk | Directly Exposed |
| CVE-2025-22037 | MEDIUM6.32 | linux-libc-dev 5.15.0-87.97 No fix yet | 28.2% High Exploitation Risk | Directly Exposed |
| CVE-2026-3833 | MEDIUM6.29 | libgnutls30 3.7.3-4ubuntu1.2 fixed in 3.7.3-4ubuntu1.9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM6.29 | libgnutls30 3.7.3-4ubuntu1.2 fixed in 3.7.3-4ubuntu1.9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.25 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.21 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40170 | MEDIUM6.29 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-14899 | MEDIUM6.29 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-48526 | MEDIUM6.29 | PyJWT 2.8.0 fixed in 2.13.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-30370 | MEDIUM6.29 | jupyterlab-git 0.41.0 fixed in 0.51.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-32002 | MEDIUM6.21 | git 1:2.34.1-1ubuntu1.10 fixed in 1:2.34.1-1ubuntu1.11 | 25.3% High Exploitation Risk | Post-Exploit |
| CVE-2024-36600 | MEDIUM6.21 | libcdio19 2.1.0-3build1 fixed in 2.1.0-3ubuntu0.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-56406 | MEDIUM6.21 | libperl5.34 5.34.0-3ubuntu1.2 fixed in 5.34.0-3ubuntu1.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-46908 | MEDIUM6.21 | libsqlite3-0 3.37.2-2ubuntu0.1 fixed in 3.37.2-2ubuntu0.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61144 | MEDIUM6.21 | libtiff5 4.3.0-6ubuntu0.6 fixed in 4.3.0-6ubuntu0.13 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43038 | MEDIUM6.21 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31607 | MEDIUM6.21 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43074 | MEDIUM6.21 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43078 | MEDIUM6.21 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-179.189 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53781 | MEDIUM6.21 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42093 | MEDIUM6.21 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40269 | MEDIUM6.21 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40304 | MEDIUM6.21 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68800 | MEDIUM6.21 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23243 | MEDIUM6.21 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56406 | MEDIUM6.21 | perl-modules-5.34 5.34.0-3ubuntu1.2 fixed in 5.34.0-3ubuntu1.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40110 | MEDIUM6.21 | jupyter_server 2.8.0 fixed in 2.18.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-34062 | MEDIUM6.21 | tqdm 4.66.1 fixed in 4.66.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-41942 | MEDIUM6.12 | jupyterhub 4.0.2 fixed in 4.1.6, 5.1.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM6.03 | libgnutls30 3.7.3-4ubuntu1.2 fixed in 3.7.3-4ubuntu1.9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-64720 | MEDIUM6.03 | libpng16-16 1.6.37-3build5 fixed in 1.6.37-3ubuntu0.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-65018 | MEDIUM6.03 | libpng16-16 1.6.37-3build5 fixed in 1.6.37-3ubuntu0.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66293 | MEDIUM6.03 | libpng16-16 1.6.37-3build5 fixed in 1.6.37-3ubuntu0.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22695 | MEDIUM6.03 | libpng16-16 1.6.37-3build5 fixed in 1.6.37-3ubuntu0.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1299 | MEDIUM6.03 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4786 | MEDIUM6.03 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1299 | MEDIUM6.03 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4786 | MEDIUM6.03 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46135 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26597 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-21647 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-21762 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21887 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39735 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22984 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23455 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46259 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49172 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49218 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49234 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49401 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49518 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49961 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50551 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52501 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52502 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52504 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52507 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52519 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52588 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52598 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52640 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52682 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52701 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53034 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53238 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53254 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53321 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53376 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53575 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53600 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53659 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53751 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-6606 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-92.102 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-6610 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-25742 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-117.127 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26593 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26664 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26665 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26669 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26673 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26763 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26791 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26954 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27401 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-34777 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35785 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35849 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35871 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35896 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35937 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35939 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35963 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-130.140 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35965 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-130.140 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35966 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-130.140 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35967 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-130.140 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36013 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-36032 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36883 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36915 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36916 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-36931 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36960 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-37078 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38381 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38538 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38560 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38599 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38621 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38635 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38659 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39467 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39469 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39471 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39487 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39499 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40929 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40978 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41013 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41090 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41091 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41935 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42094 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42292 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44983 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-44999 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46722 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46723 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46724 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46731 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46743 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46747 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46774 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46854 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46865 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47723 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47757 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49860 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49861 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49900 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49928 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50033 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50035 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50115 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50128 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50164 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50193 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50247 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50268 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50278 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50279 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50301 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-52332 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53099 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53147 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53155 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53216 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56597 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56627 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56650 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56721 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57838 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57906 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57907 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57908 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57910 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57911 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57912 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57925 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57929 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57945 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57982 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58007 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58014 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58015 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58054 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21719 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21753 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21920 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21946 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21985 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22038 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22039 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-22079 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22104 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22107 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22121 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23156 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23157 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37739 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37749 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37780 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37785 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37879 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38004 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-152.162 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38081 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38088 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38103 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38111 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38153 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38159 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38204 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38249 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38286 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38320 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38329 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38330 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38340 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38342 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38395 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38445 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38482 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38483 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38497 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38502 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38529 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38530 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38556 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38652 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38670 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38677 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38679 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38680 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38713 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38714 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38715 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38728 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39683 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39685 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39687 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39710 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39744 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39750 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39757 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39760 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39761 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39806 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39817 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39839 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39853 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39869 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39883 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39891 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39901 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39943 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40064 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40082 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40322 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40349 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40351 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68168 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68183 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68324 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68366 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68724 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71093 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71112 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71116 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71133 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71136 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23076 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23099 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23204 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23235 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23315 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23318 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23388 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23397 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31568 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31614 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31685 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31778 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43040 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43051 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43052 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43141 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43241 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43281 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43386 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43427 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43449 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43450 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43453 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45893 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45957 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45994 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46022 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46033 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46053 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46056 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46064 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46120 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46150 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46191 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46209 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52968 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53138 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53149 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53179 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53303 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53309 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53330 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52766 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26982 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41014 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41059 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53174 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56558 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21782 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21905 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21950 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21993 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-138.148 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43126 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43380 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43414 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53255 | MEDIUM6.03 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1299 | MEDIUM6.03 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4786 | MEDIUM6.03 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1299 | MEDIUM6.03 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4786 | MEDIUM6.03 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-44243 | MEDIUM6.03 | GitPython 3.1.40 fixed in 3.1.48 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc-bin 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc-dev-bin 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc6 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc6-dev 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4878 | MEDIUM5.95 | libcap2 1:2.44-1ubuntu0.22.04.1 fixed in 1:2.44-1ubuntu0.22.04.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5222 | MEDIUM5.95 | libicu70 70.1-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43304 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46043 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52989 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52993 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53002 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-51781 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-97.107 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52935 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-6270 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-6931 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-92.102 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-6932 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-92.102 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-27397 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-124.134 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-43882 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56672 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-134.145 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-21703 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-138.148 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-21718 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21726 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21727 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21761 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21764 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-54518 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23191 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23392 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31419 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-179.189 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31586 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31663 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31694 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43116 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43198 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43341 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43493 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-43494 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-181.191 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43503 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-181.191 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45852 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46119 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46275 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46319 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52924 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53006 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53036 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53072 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53185 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53212 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53224 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53239 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53254 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53256 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53264 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53270 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53275 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-3864 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-1247 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-2961 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-46813 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-51779 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-51780 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-97.107 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-51782 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52503 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52517 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52578 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52581 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52586 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52847 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53358 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53622 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53821 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-6546 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26654 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26852 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26974 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27020 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36899 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39503 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41040 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41049 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42228 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-122.132 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43883 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46858 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47747 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49855 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49981 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50036 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50059 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50061 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50086 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50106 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50234 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50275 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50286 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56664 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57876 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21702 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-138.148 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-22004 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37776 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37915 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38051 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-152.162 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38102 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38107 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38108 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39702 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39749 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39759 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39826 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39905 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39993 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-164.174 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40135 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40154 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40158 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40168 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40248 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40259 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40271 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-68285 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68287 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68301 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71203 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71221 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23050 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23054 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23270 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23454 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31408 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43050 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43158 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43226 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43233 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43334 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43339 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45856 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45859 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45860 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45942 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45970 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46015 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46052 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46054 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46090 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46099 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46116 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46123 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46133 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-46149 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46174 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46181 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46227 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46266 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46324 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52912 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52917 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52918 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52920 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52933 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52935 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52942 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52945 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52947 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52956 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52957 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52986 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-52991 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52998 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53000 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53005 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53009 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53011 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53016 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53049 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53075 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53091 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53131 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53133 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53223 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53228 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-53246 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53268 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53354 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53355 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53357 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-45885 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-1989 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-35827 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26872 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49903 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50154 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21739 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31508 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45894 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53053 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53062 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53078 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53189 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53230 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53253 | MEDIUM5.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc-bin 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc-bin 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.5 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc-dev-bin 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc-dev-bin 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.5 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc6 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc6 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.5 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc6-dev 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc6-dev 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.5 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-50602 | MEDIUM5.9 | libexpat1 2.4.7-1ubuntu0.2 fixed in 2.4.7-1ubuntu0.5 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt20 1.9.4-3ubuntu3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5981 | MEDIUM5.9 | libgnutls30 3.7.3-4ubuntu1.2 fixed in 3.7.3-4ubuntu1.3 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libgssapi-krb5-2 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.6 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libk5crypto3 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.6 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5-3 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.6 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5support0 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.6 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6237 | MEDIUM5.9 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.14 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-5535 | MEDIUM5.9 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.17 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1-6 4.18.0-4build1 fixed in 4.18.0-4ubuntu0.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3714 | MEDIUM5.9 | linux-libc-dev 5.15.0-87.97 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-1121 | MEDIUM5.9 | linux-libc-dev 5.15.0-87.97 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-48815 | MEDIUM5.9 | sigstore 2.1.0 fixed in 4.1.1 | — | Directly Exposed |
| CVE-2026-49476 | MEDIUM5.9 | soupsieve 2.5 fixed in 2.8.4 | — | Directly Exposed |
| CVE-2023-28531 | MEDIUM5.88 | openssh-client 1:8.9p1-3ubuntu0.4 fixed in 1:8.9p1-3ubuntu0.5 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-48522 | MEDIUM5.88 | perl 5.34.0-3ubuntu1.2 fixed in 5.34.0-3ubuntu1.3 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-48522 | MEDIUM5.88 | perl-base 5.34.0-3ubuntu1.2 fixed in 5.34.0-3ubuntu1.3 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2024-29415 | MEDIUM5.88 | ip 2.0.0 No fix yet | 8.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-42282 | MEDIUM5.88 | ip 2.0.0 fixed in 2.0.1, 1.1.9 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2024-6119 | MEDIUM5.85 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.18 | 66.6% Actively Exploited | Post-Exploit |
| CVE-2024-53197 | MEDIUM5.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33870 | MEDIUM5.78 | libgs9 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-33870 | MEDIUM5.78 | libgs9-common 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-6923 | MEDIUM5.78 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-6923 | MEDIUM5.78 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-53196 | MEDIUM5.78 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-40345 | MEDIUM5.78 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68346 | MEDIUM5.78 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-24857 | MEDIUM5.78 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-6923 | MEDIUM5.78 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-6923 | MEDIUM5.78 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-40934 | MEDIUM5.78 | jupyter_server 2.8.0 fixed in 2.18.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-61915 | MEDIUM5.7 | libcups2 2.4.1op1-1ubuntu4.7 fixed in 2.4.1op1-1ubuntu4.15 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-10573 | MEDIUM5.7 | libmpg123-0 1.29.3-1build1 fixed in 1.29.3-1ubuntu0.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52447 | MEDIUM5.7 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-0193 | MEDIUM5.7 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-92.102 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26828 | MEDIUM5.7 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46331 | MEDIUM5.7 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49063 | MEDIUM5.7 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-50616 | MEDIUM5.7 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26586 | MEDIUM5.7 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53095 | MEDIUM5.7 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56678 | MEDIUM5.7 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56693 | MEDIUM5.7 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40257 | MEDIUM5.7 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57795 | MEDIUM5.7 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21714 | MEDIUM5.7 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21731 | MEDIUM5.7 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22035 | MEDIUM5.7 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22097 | MEDIUM5.7 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.61 | libgnutls30 3.7.3-4ubuntu1.2 fixed in 3.7.3-4ubuntu1.9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50851 | MEDIUM5.61 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53729 | MEDIUM5.61 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-0607 | MEDIUM5.61 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40018 | MEDIUM5.61 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-164.174 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40261 | MEDIUM5.61 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45991 | MEDIUM5.61 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53267 | MEDIUM5.61 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.20 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4741 | MEDIUM5.6 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.17 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-68468 | MEDIUM5.52 | libavahi-client3 0.8-5ubuntu5.1 fixed in 0.8-5ubuntu5.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68471 | MEDIUM5.52 | libavahi-client3 0.8-5ubuntu5.1 fixed in 0.8-5ubuntu5.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-24401 | MEDIUM5.52 | libavahi-client3 0.8-5ubuntu5.1 fixed in 0.8-5ubuntu5.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68468 | MEDIUM5.52 | libavahi-common-data 0.8-5ubuntu5.1 fixed in 0.8-5ubuntu5.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68471 | MEDIUM5.52 | libavahi-common-data 0.8-5ubuntu5.1 fixed in 0.8-5ubuntu5.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-24401 | MEDIUM5.52 | libavahi-common-data 0.8-5ubuntu5.1 fixed in 0.8-5ubuntu5.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68468 | MEDIUM5.52 | libavahi-common3 0.8-5ubuntu5.1 fixed in 0.8-5ubuntu5.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68471 | MEDIUM5.52 | libavahi-common3 0.8-5ubuntu5.1 fixed in 0.8-5ubuntu5.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-24401 | MEDIUM5.52 | libavahi-common3 0.8-5ubuntu5.1 fixed in 0.8-5ubuntu5.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-59728 | MEDIUM5.52 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59732 | MEDIUM5.52 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59733 | MEDIUM5.52 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59728 | MEDIUM5.52 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59732 | MEDIUM5.52 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59733 | MEDIUM5.52 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59728 | MEDIUM5.52 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59732 | MEDIUM5.52 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59733 | MEDIUM5.52 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59728 | MEDIUM5.52 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59732 | MEDIUM5.52 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59733 | MEDIUM5.52 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59728 | MEDIUM5.52 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59732 | MEDIUM5.52 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59733 | MEDIUM5.52 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.35-0ubuntu3.4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-dev-bin 2.35-0ubuntu3.4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.35-0ubuntu3.4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6-dev 2.35-0ubuntu3.4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34978 | MEDIUM5.52 | libcups2 2.4.1op1-1ubuntu4.7 fixed in 2.4.1op1-1ubuntu4.20 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14512 | MEDIUM5.52 | libglib2.0-0 2.72.4-0ubuntu2.2 fixed in 2.72.4-0ubuntu2.7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-6395 | MEDIUM5.52 | libgnutls30 3.7.3-4ubuntu1.2 fixed in 3.7.3-4ubuntu1.7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libgssapi-krb5-2 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-38076 | MEDIUM5.52 | libjbig2dec0 0.19-3build2 fixed in 0.19-3ubuntu0.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-46361 | MEDIUM5.52 | libjbig2dec0 0.19-3build2 fixed in 0.19-3ubuntu0.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libk5crypto3 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libkrb5-3 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libkrb5support0 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | MEDIUM5.52 | libncurses6 6.3-2ubuntu0.1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | MEDIUM5.52 | libncursesw6 6.3-2ubuntu0.1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-39329 | MEDIUM5.52 | libopenjp2-7 2.4.0-6 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-37769 | MEDIUM5.52 | libpixman-1-0 0.40.0-1ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-59728 | MEDIUM5.52 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59732 | MEDIUM5.52 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59733 | MEDIUM5.52 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50613 | MEDIUM5.52 | libsndfile1 1.0.31-2build1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-59728 | MEDIUM5.52 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59732 | MEDIUM5.52 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59733 | MEDIUM5.52 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59728 | MEDIUM5.52 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59732 | MEDIUM5.52 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59733 | MEDIUM5.52 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-40090 | MEDIUM5.52 | libtiff5 4.3.0-6ubuntu0.6 fixed in 4.3.0-6ubuntu0.7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | MEDIUM5.52 | libtinfo6 6.3-2ubuntu0.1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-2175 | MEDIUM5.52 | libzvbi-common 0.2.35-19 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-2177 | MEDIUM5.52 | libzvbi-common 0.2.35-19 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-2175 | MEDIUM5.52 | libzvbi0 0.2.35-19 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-2177 | MEDIUM5.52 | libzvbi0 0.2.35-19 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-26808 | MEDIUM5.52 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53176 | MEDIUM5.52 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2015-8553 | MEDIUM5.52 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-49168 | MEDIUM5.52 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-53785 | MEDIUM5.52 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54292 | MEDIUM5.52 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36968 | MEDIUM5.52 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47693 | MEDIUM5.52 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-47726 | MEDIUM5.52 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-53135 | MEDIUM5.52 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39969 | MEDIUM5.52 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40273 | MEDIUM5.52 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40336 | MEDIUM5.52 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68284 | MEDIUM5.52 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68354 | MEDIUM5.52 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68362 | MEDIUM5.52 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23179 | MEDIUM5.52 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31588 | MEDIUM5.52 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-0564 | MEDIUM5.52 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | MEDIUM5.52 | ncurses-base 6.3-2ubuntu0.1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-27904 | MEDIUM5.52 | minimatch 3.1.2 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-27904 | MEDIUM5.52 | minimatch 9.0.3 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-26007 | MEDIUM5.52 | cryptography 41.0.4 fixed in 46.0.5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-22421 | MEDIUM5.52 | jupyterlab 4.0.7 fixed in 4.0.11, 3.6.7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-54528 | MEDIUM5.52 | jupyterlab-git 0.41.0 fixed in 0.54.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59925 | MEDIUM5.52 | mistune 3.0.1 fixed in 3.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59928 | MEDIUM5.52 | mistune 3.0.1 fixed in 3.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-22421 | MEDIUM5.52 | notebook 7.0.6 fixed in 7.0.7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libbinutils 2.38-4ubuntu2.3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010204 | MEDIUM5.5 | libbinutils 2.38-4ubuntu2.3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | MEDIUM5.5 | libcairo-gobject2 1.16.0-5ubuntu2 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | MEDIUM5.5 | libcairo2 1.16.0-5ubuntu2 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf-nobfd0 2.38-4ubuntu2.3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010204 | MEDIUM5.5 | libctf-nobfd0 2.38-4ubuntu2.3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf0 2.38-4ubuntu2.3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010204 | MEDIUM5.5 | libctf0 2.38-4ubuntu2.3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-29338 | MEDIUM5.5 | libopenjp2-7 2.4.0-6 fixed in 2.4.0-6ubuntu0.2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1122 | MEDIUM5.5 | libopenjp2-7 2.4.0-6 fixed in 2.4.0-6ubuntu0.2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.14 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-34459 | MEDIUM5.5 | libxml2 2.9.13+dfsg-1ubuntu0.3 fixed in 2.9.13+dfsg-1ubuntu0.5 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-17828 | MEDIUM5.5 | libzzip-0-13 0.13.72+dfsg.1-1.1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26924 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-113.123 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-21760 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 9.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-27028 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-27053 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-27405 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-35955 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-35960 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-38573 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-38587 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-38562 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 7.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-53369 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-53379 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-53385 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-53400 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-53402 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-53403 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63803 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63810 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63822 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63832 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63858 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63860 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-63865 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-63867 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63868 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63870 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63872 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63890 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63892 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63893 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63897 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63900 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63902 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63903 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63904 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63926 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63927 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63942 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63948 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63961 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63963 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63964 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63973 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63976 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63983 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63985 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63990 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63991 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-63999 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64004 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64005 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64006 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64012 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64014 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64039 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64046 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64076 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64077 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64078 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64079 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64103 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64106 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64112 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64116 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64118 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64123 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64125 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64126 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64133 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64144 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64153 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64155 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64170 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64173 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64176 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64177 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64178 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64179 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64185 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Directly Exposed |
| CVE-2026-64187 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64190 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2026-64206 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Directly Exposed |
| CVE-2023-52832 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-38612 | MEDIUM5.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | cryptography 41.0.4 fixed in 42.0.2 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-40225 | MEDIUM5.44 | libsystemd0 249.11-0ubuntu3.10 fixed in 249.11-0ubuntu3.19 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | MEDIUM5.44 | libsystemd0 249.11-0ubuntu3.10 fixed in 249.11-0ubuntu3.21 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40225 | MEDIUM5.44 | libudev1 249.11-0ubuntu3.10 fixed in 249.11-0ubuntu3.19 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | MEDIUM5.44 | libudev1 249.11-0ubuntu3.10 fixed in 249.11-0ubuntu3.21 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-36016 | MEDIUM5.44 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-117.127 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23450 | MEDIUM5.44 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31502 | MEDIUM5.44 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31516 | MEDIUM5.44 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52910 | MEDIUM5.44 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53033 | MEDIUM5.44 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53090 | MEDIUM5.44 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-39198 | MEDIUM5.44 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-52886 | MEDIUM5.44 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-21823 | MEDIUM5.44 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21700 | MEDIUM5.44 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-138.148 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39978 | MEDIUM5.44 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40074 | MEDIUM5.44 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40309 | MEDIUM5.44 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40321 | MEDIUM5.44 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68371 | MEDIUM5.44 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23456 | MEDIUM5.44 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-44032 | MEDIUM5.44 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-44033 | MEDIUM5.44 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-44034 | MEDIUM5.44 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-45888 | MEDIUM5.44 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-57979 | MEDIUM5.44 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21999 | MEDIUM5.44 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-6485 | MEDIUM5.44 | bootstrap 3.4.1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-27447 | MEDIUM5.35 | libcups2 2.4.1op1-1ubuntu4.7 fixed in 2.4.1op1-1ubuntu4.20 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0964 | MEDIUM5.35 | libssh-4 0.9.6-2ubuntu0.22.04.1 fixed in 0.9.6-2ubuntu0.22.04.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0964 | MEDIUM5.35 | libssh-gcrypt-4 0.9.6-2ubuntu0.22.04.1 fixed in 0.9.6-2ubuntu0.22.04.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31504 | MEDIUM5.35 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-179.189 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52644 | MEDIUM5.35 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54072 | MEDIUM5.35 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-24861 | MEDIUM5.35 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26830 | MEDIUM5.35 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-119.129 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27030 | MEDIUM5.35 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38544 | MEDIUM5.35 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40918 | MEDIUM5.35 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41012 | MEDIUM5.35 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42161 | MEDIUM5.35 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57893 | MEDIUM5.35 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40307 | MEDIUM5.35 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68282 | MEDIUM5.35 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56326 | MEDIUM5.35 | Jinja2 3.1.2 fixed in 3.1.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | libc-bin 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.8 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | libc-dev-bin 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.8 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | libc6 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.8 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | libc6-dev 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.8 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-12243 | MEDIUM5.3 | libgnutls30 3.7.3-4ubuntu1.2 fixed in 3.7.3-4ubuntu1.6 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-32989 | MEDIUM5.3 | libgnutls30 3.7.3-4ubuntu1.2 fixed in 3.7.3-4ubuntu1.7 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-27043 | MEDIUM5.3 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.6 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-8088 | MEDIUM5.3 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.6 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-27043 | MEDIUM5.3 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.6 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-8088 | MEDIUM5.3 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.6 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6918 | MEDIUM5.3 | libssh-4 0.9.6-2ubuntu0.22.04.1 fixed in 0.9.6-2ubuntu0.22.04.3 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6918 | MEDIUM5.3 | libssh-gcrypt-4 0.9.6-2ubuntu0.22.04.1 fixed in 0.9.6-2ubuntu0.22.04.3 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3446 | MEDIUM5.3 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.12 | 5.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3817 | MEDIUM5.3 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.12 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5678 | MEDIUM5.3 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.14 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4603 | MEDIUM5.3 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.17 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-12133 | MEDIUM5.3 | libtasn1-6 4.18.0-4build1 fixed in 4.18.0-4ubuntu0.1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-27043 | MEDIUM5.3 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.6 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-8088 | MEDIUM5.3 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.6 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-27043 | MEDIUM5.3 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.6 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-8088 | MEDIUM5.3 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.6 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-49854 | MEDIUM5.3 | tornado 6.3.3 fixed in 6.5.6 | — | Directly Exposed |
| CVE-2024-7055 | MEDIUM5.28 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-29509 | MEDIUM5.28 | ghostscript 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.9 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2024-33871 | MEDIUM5.28 | ghostscript 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.7 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-32462 | MEDIUM5.28 | sudo 1.9.9-1ubuntu2.4 fixed in 1.9.9-1ubuntu2.5 | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2017-17513 | MEDIUM5.28 | texlive-base 2021.20220204-1 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-17513 | MEDIUM5.28 | texlive-fonts-recommended 2021.20220204-1 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-17513 | MEDIUM5.28 | texlive-latex-base 2021.20220204-1 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-17513 | MEDIUM5.28 | texlive-latex-recommended 2021.20220204-1 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-17513 | MEDIUM5.28 | texlive-pictures 2021.20220204-1 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-17513 | MEDIUM5.28 | texlive-xetex 2021.20220204-1 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-6345 | MEDIUM5.28 | setuptools 68.2.2 fixed in 70.0.0 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2025-47273 | MEDIUM5.28 | setuptools 68.2.2 fixed in 78.1.1 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-39314 | MEDIUM5.27 | libcups2 2.4.1op1-1ubuntu4.7 fixed in 2.4.1op1-1ubuntu4.20 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39316 | MEDIUM5.27 | libcups2 2.4.1op1-1ubuntu4.7 fixed in 2.4.1op1-1ubuntu4.20 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | libp11-kit0 0.24.0-6build1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-0450 | MEDIUM5.27 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-0450 | MEDIUM5.27 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23253 | MEDIUM5.27 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-54081 | MEDIUM5.27 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50251 | MEDIUM5.27 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-21722 | MEDIUM5.27 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40048 | MEDIUM5.27 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40146 | MEDIUM5.27 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68757 | MEDIUM5.27 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71066 | MEDIUM5.27 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-0450 | MEDIUM5.27 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-0450 | MEDIUM5.27 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-5569 | MEDIUM5.27 | zipp 3.17.0 fixed in 3.19.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1390 | MEDIUM5.18 | libcap2 1:2.44-1ubuntu0.22.04.1 fixed in 1:2.44-1ubuntu0.22.04.2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-64506 | MEDIUM5.18 | libpng16-16 1.6.37-3build5 fixed in 1.6.37-3ubuntu0.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40190 | MEDIUM5.18 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31449 | MEDIUM5.18 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31700 | MEDIUM5.18 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31708 | MEDIUM5.18 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52497 | MEDIUM5.18 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52810 | MEDIUM5.18 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52829 | MEDIUM5.18 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-53808 | MEDIUM5.18 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53850 | MEDIUM5.18 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54096 | MEDIUM5.18 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42224 | MEDIUM5.18 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57874 | MEDIUM5.18 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40019 | MEDIUM5.18 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-168.178 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-40071 | MEDIUM5.18 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40080 | MEDIUM5.18 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40279 | MEDIUM5.18 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40355 | MEDIUM5.18 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68245 | MEDIUM5.18 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68342 | MEDIUM5.18 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68343 | MEDIUM5.18 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68736 | MEDIUM5.18 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68764 | MEDIUM5.18 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68815 | MEDIUM5.18 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68819 | MEDIUM5.18 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43134 | MEDIUM5.18 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31464 | MEDIUM5.18 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31570 | MEDIUM5.18 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-26159 | MEDIUM5.18 | follow-redirects 1.15.2 fixed in 1.15.4 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-22195 | MEDIUM5.18 | Jinja2 3.1.2 fixed in 3.1.3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-23528 | MEDIUM5.18 | distributed 2023.10.0 fixed in 2026.1.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-61669 | MEDIUM5.18 | jupyter_server 2.8.0 fixed in 2.18.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-28233 | MEDIUM5.18 | jupyterhub 4.0.2 fixed in 4.1.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-33709 | MEDIUM5.18 | jupyterhub 4.0.2 fixed in 5.4.4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43805 | MEDIUM5.18 | jupyterlab 4.0.7 fixed in 3.6.8, 4.2.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-22420 | MEDIUM5.18 | jupyterlab 4.0.7 fixed in 4.0.11 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44708 | MEDIUM5.18 | mistune 3.0.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44896 | MEDIUM5.18 | mistune 3.0.1 fixed in 3.2.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44897 | MEDIUM5.18 | mistune 3.0.1 fixed in 3.2.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59923 | MEDIUM5.18 | mistune 3.0.1 fixed in 3.3.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59926 | MEDIUM5.18 | mistune 3.0.1 fixed in 3.3.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59929 | MEDIUM5.18 | mistune 3.0.1 fixed in 3.3.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43805 | MEDIUM5.18 | notebook 7.0.6 fixed in 7.2.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-22420 | MEDIUM5.18 | notebook 7.0.6 fixed in 7.0.7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-67724 | MEDIUM5.18 | tornado 6.3.3 fixed in 6.5.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-50181 | MEDIUM5.18 | urllib3 2.0.7 fixed in 2.5.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-2398 | MEDIUM5.17 | curl 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.16 | 36.1% High Exploitation Risk | Post-Exploit |
| CVE-2024-2398 | MEDIUM5.17 | libcurl3-gnutls 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.16 | 36.1% High Exploitation Risk | Post-Exploit |
| CVE-2024-2398 | MEDIUM5.17 | libcurl4 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.16 | 36.1% High Exploitation Risk | Post-Exploit |
| CVE-2022-49465 | MEDIUM5.1 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-39189 | MEDIUM5.1 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-39192 | MEDIUM5.1 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-39193 | MEDIUM5.1 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-52481 | MEDIUM5.1 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-52511 | MEDIUM5.1 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-52529 | MEDIUM5.1 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26702 | MEDIUM5.1 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26843 | MEDIUM5.1 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56662 | MEDIUM5.1 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31649 | MEDIUM5.1 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26894 | MEDIUM5.1 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc-bin 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.13 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.35-0ubuntu3.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc-dev-bin 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.13 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-dev-bin 2.35-0ubuntu3.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc6 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.13 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.35-0ubuntu3.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc6-dev 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.13 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6-dev 2.35-0ubuntu3.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-32570 | MEDIUM5.02 | libdav1d5 0.9.2-1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libgssapi-krb5-2 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssapi-krb5-2 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libk5crypto3 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libk5crypto3 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libkrb5-3 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-3 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libkrb5support0 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5support0 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-40909 | MEDIUM5.02 | libperl5.34 5.34.0-3ubuntu1.2 fixed in 5.34.0-3ubuntu1.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.02 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.23 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.21 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.21 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.25 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.25 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-7008 | MEDIUM5.02 | libsystemd0 249.11-0ubuntu3.10 fixed in 249.11-0ubuntu3.21 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-7008 | MEDIUM5.02 | libudev1 249.11-0ubuntu3.10 fixed in 249.11-0ubuntu3.21 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-0990 | MEDIUM5.02 | libxml2 2.9.13+dfsg-1ubuntu0.3 fixed in 2.9.13+dfsg-1ubuntu0.11 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-53764 | MEDIUM5.02 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-54048 | MEDIUM5.02 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54302 | MEDIUM5.02 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2312 | MEDIUM5.02 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40083 | MEDIUM5.02 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40242 | MEDIUM5.02 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40324 | MEDIUM5.02 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35870 | MEDIUM5.02 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40909 | MEDIUM5.02 | perl-modules-5.34 5.34.0-3ubuntu1.2 fixed in 5.34.0-3ubuntu1.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27903 | MEDIUM5.02 | minimatch 3.1.2 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-27903 | MEDIUM5.02 | minimatch 9.0.3 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44307 | MEDIUM5.02 | Mako 1.2.4 fixed in 1.3.12 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-28219 | MEDIUM5.02 | Pillow 10.1.0 fixed in 10.3.0 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-48524 | MEDIUM5.02 | PyJWT 2.8.0 fixed in 2.13.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40962 | MEDIUM5 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31789 | MEDIUM5 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.23 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | MEDIUM5 | perl 5.34.0-3ubuntu1.2 fixed in 5.34.0-3ubuntu1.7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | MEDIUM5 | perl-base 5.34.0-3ubuntu1.2 fixed in 5.34.0-3ubuntu1.7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-23240 | MEDIUM4.93 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-23271 | MEDIUM4.93 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31414 | MEDIUM4.93 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-53789 | MEDIUM4.93 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54045 | MEDIUM4.93 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54107 | MEDIUM4.93 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54136 | MEDIUM4.93 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54258 | MEDIUM4.93 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35910 | MEDIUM4.93 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39994 | MEDIUM4.93 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39998 | MEDIUM4.93 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40111 | MEDIUM4.93 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40118 | MEDIUM4.93 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40167 | MEDIUM4.93 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40194 | MEDIUM4.93 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40237 | MEDIUM4.93 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40272 | MEDIUM4.93 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40323 | MEDIUM4.93 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40340 | MEDIUM4.93 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68742 | MEDIUM4.93 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23239 | MEDIUM4.93 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31426 | MEDIUM4.93 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43279 | MEDIUM4.93 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46065 | MEDIUM4.93 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46113 | MEDIUM4.93 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52923 | MEDIUM4.93 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31392 | MEDIUM4.93 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-8925 | MEDIUM4.86 | curl 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.25 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-3964 | MEDIUM4.86 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 3.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-48434 | MEDIUM4.86 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-8925 | MEDIUM4.86 | libcurl3-gnutls 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.25 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-8925 | MEDIUM4.86 | libcurl4 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.25 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | MEDIUM4.86 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.25 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-49138 | MEDIUM4.84 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49569 | MEDIUM4.84 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40319 | MEDIUM4.84 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46024 | MEDIUM4.84 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-2511 | MEDIUM4.81 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.17 | 54.0% Actively Exploited | Directly Exposed |
| CVE-2025-48384 | MEDIUM4.8 | git 1:2.34.1-1ubuntu1.10 fixed in 1:2.34.1-1ubuntu1.13 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-60002 | MEDIUM4.79 | openssh-client 1:8.9p1-3ubuntu0.4 fixed in 1:8.9p1-3ubuntu0.16 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | MEDIUM4.76 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-56826 | MEDIUM4.76 | libopenjp2-7 2.4.0-6 fixed in 2.4.0-6ubuntu0.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56827 | MEDIUM4.76 | libopenjp2-7 2.4.0-6 fixed in 2.4.0-6ubuntu0.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54251 | MEDIUM4.76 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-28956 | MEDIUM4.76 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-36350 | MEDIUM4.76 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-36357 | MEDIUM4.76 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68801 | MEDIUM4.76 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68816 | MEDIUM4.76 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1647 | MEDIUM4.76 | bootstrap 3.4.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35195 | MEDIUM4.76 | requests 2.31.0 fixed in 2.32.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-20569 | MEDIUM4.7 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 6.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2201 | MEDIUM4.7 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 8.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-0537 | MEDIUM4.7 | linux-libc-dev 5.15.0-87.97 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-32004 | MEDIUM4.68 | git 1:2.34.1-1ubuntu1.10 fixed in 1:2.34.1-1ubuntu1.11 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-48624 | MEDIUM4.68 | less 590-1ubuntu0.22.04.1 fixed in 590-1ubuntu0.22.04.2 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9587 | MEDIUM4.68 | texlive-binaries 2021.20210626.59705-1ubuntu0.1 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9588 | MEDIUM4.68 | texlive-binaries 2021.20210626.59705-1ubuntu0.1 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2000 | MEDIUM4.68 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2042 | MEDIUM4.68 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28417 | MEDIUM4.68 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.26 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1886 | MEDIUM4.68 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1897 | MEDIUM4.68 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2000 | MEDIUM4.68 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2042 | MEDIUM4.68 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28417 | MEDIUM4.68 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.26 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1886 | MEDIUM4.68 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1897 | MEDIUM4.68 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2000 | MEDIUM4.68 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2042 | MEDIUM4.68 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28417 | MEDIUM4.68 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.26 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1886 | MEDIUM4.68 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1897 | MEDIUM4.68 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2021-46195 | MEDIUM4.67 | gcc-11-base 11.4.0-1ubuntu1~22.04 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | gcc-11-base 11.4.0-1ubuntu1~22.04 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | gcc-12-base 12.3.0-1ubuntu1~22.04 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | MEDIUM4.67 | libasan6 11.4.0-1ubuntu1~22.04 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libasan6 11.4.0-1ubuntu1~22.04 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libatomic1 12.3.0-1ubuntu1~22.04 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-38469 | MEDIUM4.67 | libavahi-client3 0.8-5ubuntu5.1 fixed in 0.8-5ubuntu5.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-38470 | MEDIUM4.67 | libavahi-client3 0.8-5ubuntu5.1 fixed in 0.8-5ubuntu5.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-38471 | MEDIUM4.67 | libavahi-client3 0.8-5ubuntu5.1 fixed in 0.8-5ubuntu5.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-38472 | MEDIUM4.67 | libavahi-client3 0.8-5ubuntu5.1 fixed in 0.8-5ubuntu5.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-38473 | MEDIUM4.67 | libavahi-client3 0.8-5ubuntu5.1 fixed in 0.8-5ubuntu5.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-59529 | MEDIUM4.67 | libavahi-client3 0.8-5ubuntu5.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68276 | MEDIUM4.67 | libavahi-client3 0.8-5ubuntu5.1 fixed in 0.8-5ubuntu5.4 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34933 | MEDIUM4.67 | libavahi-client3 0.8-5ubuntu5.1 fixed in 0.8-5ubuntu5.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-38469 | MEDIUM4.67 | libavahi-common-data 0.8-5ubuntu5.1 fixed in 0.8-5ubuntu5.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-38470 | MEDIUM4.67 | libavahi-common-data 0.8-5ubuntu5.1 fixed in 0.8-5ubuntu5.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-38471 | MEDIUM4.67 | libavahi-common-data 0.8-5ubuntu5.1 fixed in 0.8-5ubuntu5.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-38472 | MEDIUM4.67 | libavahi-common-data 0.8-5ubuntu5.1 fixed in 0.8-5ubuntu5.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-38473 | MEDIUM4.67 | libavahi-common-data 0.8-5ubuntu5.1 fixed in 0.8-5ubuntu5.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-59529 | MEDIUM4.67 | libavahi-common-data 0.8-5ubuntu5.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68276 | MEDIUM4.67 | libavahi-common-data 0.8-5ubuntu5.1 fixed in 0.8-5ubuntu5.4 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34933 | MEDIUM4.67 | libavahi-common-data 0.8-5ubuntu5.1 fixed in 0.8-5ubuntu5.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-38469 | MEDIUM4.67 | libavahi-common3 0.8-5ubuntu5.1 fixed in 0.8-5ubuntu5.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-38470 | MEDIUM4.67 | libavahi-common3 0.8-5ubuntu5.1 fixed in 0.8-5ubuntu5.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-38471 | MEDIUM4.67 | libavahi-common3 0.8-5ubuntu5.1 fixed in 0.8-5ubuntu5.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-38472 | MEDIUM4.67 | libavahi-common3 0.8-5ubuntu5.1 fixed in 0.8-5ubuntu5.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-38473 | MEDIUM4.67 | libavahi-common3 0.8-5ubuntu5.1 fixed in 0.8-5ubuntu5.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-59529 | MEDIUM4.67 | libavahi-common3 0.8-5ubuntu5.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68276 | MEDIUM4.67 | libavahi-common3 0.8-5ubuntu5.1 fixed in 0.8-5ubuntu5.4 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34933 | MEDIUM4.67 | libavahi-common3 0.8-5ubuntu5.1 fixed in 0.8-5ubuntu5.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-10256 | MEDIUM4.67 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-10256 | MEDIUM4.67 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-10256 | MEDIUM4.67 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-10256 | MEDIUM4.67 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-10256 | MEDIUM4.67 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-35205 | MEDIUM4.67 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-47007 | MEDIUM4.67 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-47008 | MEDIUM4.67 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-47010 | MEDIUM4.67 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-47011 | MEDIUM4.67 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-48063 | MEDIUM4.67 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-48065 | MEDIUM4.67 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.12 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.12 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.12 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.12 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libbinutils 2.38-4ubuntu2.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libbinutils 2.38-4ubuntu2.3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-4285 | MEDIUM4.67 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-48064 | MEDIUM4.67 | libbinutils 2.38-4ubuntu2.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc-bin 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc-dev-bin 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc6 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc6-dev 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libcc1-0 12.3.0-1ubuntu1~22.04 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-35205 | MEDIUM4.67 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-47007 | MEDIUM4.67 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-47008 | MEDIUM4.67 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-47010 | MEDIUM4.67 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-47011 | MEDIUM4.67 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-48063 | MEDIUM4.67 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-48065 | MEDIUM4.67 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.12 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.12 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.12 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.12 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf-nobfd0 2.38-4ubuntu2.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libctf-nobfd0 2.38-4ubuntu2.3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-4285 | MEDIUM4.67 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-48064 | MEDIUM4.67 | libctf-nobfd0 2.38-4ubuntu2.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-35205 | MEDIUM4.67 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-47007 | MEDIUM4.67 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-47008 | MEDIUM4.67 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-47010 | MEDIUM4.67 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-47011 | MEDIUM4.67 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-48063 | MEDIUM4.67 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-48065 | MEDIUM4.67 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.12 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.12 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.12 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.12 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf0 2.38-4ubuntu2.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libctf0 2.38-4ubuntu2.3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-4285 | MEDIUM4.67 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-48064 | MEDIUM4.67 | libctf0 2.38-4ubuntu2.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-58436 | MEDIUM4.67 | libcups2 2.4.1op1-1ubuntu4.7 fixed in 2.4.1op1-1ubuntu4.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1377 | MEDIUM4.67 | libelf1 0.186-1build1 fixed in 0.186-1ubuntu0.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1 2.4.7-1ubuntu0.2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | MEDIUM4.67 | libgcc-11-dev 11.4.0-1ubuntu1~22.04 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc-11-dev 11.4.0-1ubuntu1~22.04 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc-s1 12.3.0-1ubuntu1~22.04 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgfortran5 12.3.0-1ubuntu1~22.04 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgomp1 12.3.0-1ubuntu1~22.04 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-46955 | MEDIUM4.67 | libgs9 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-27830 | MEDIUM4.67 | libgs9 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-27831 | MEDIUM4.67 | libgs9 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.11 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-27832 | MEDIUM4.67 | libgs9 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.11 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-27834 | MEDIUM4.67 | libgs9 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-27835 | MEDIUM4.67 | libgs9 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-27836 | MEDIUM4.67 | libgs9 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.11 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-59798 | MEDIUM4.67 | libgs9 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.13 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59799 | MEDIUM4.67 | libgs9 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.13 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59800 | MEDIUM4.67 | libgs9 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.13 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46955 | MEDIUM4.67 | libgs9-common 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-27830 | MEDIUM4.67 | libgs9-common 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-27831 | MEDIUM4.67 | libgs9-common 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.11 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-27832 | MEDIUM4.67 | libgs9-common 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.11 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-27834 | MEDIUM4.67 | libgs9-common 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-27835 | MEDIUM4.67 | libgs9-common 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-27836 | MEDIUM4.67 | libgs9-common 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.11 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-59798 | MEDIUM4.67 | libgs9-common 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.13 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59799 | MEDIUM4.67 | libgs9-common 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.13 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59800 | MEDIUM4.67 | libgs9-common 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.13 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libitm1 12.3.0-1ubuntu1~22.04 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-32668 | MEDIUM4.67 | libkpathsea6 2021.20210626.59705-1ubuntu0.1 fixed in 2021.20210626.59705-1ubuntu0.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | liblsan0 12.3.0-1ubuntu1~22.04 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-47169 | MEDIUM4.67 | libmfx1 22.3.0-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-48368 | MEDIUM4.67 | libmfx1 22.3.0-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-39328 | MEDIUM4.67 | libopenjp2-7 2.4.0-6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-22365 | MEDIUM4.67 | libpam-modules 1.4.0-11ubuntu2.3 fixed in 1.4.0-11ubuntu2.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-22365 | MEDIUM4.67 | libpam-modules-bin 1.4.0-11ubuntu2.3 fixed in 1.4.0-11ubuntu2.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-22365 | MEDIUM4.67 | libpam-runtime 1.4.0-11ubuntu2.3 fixed in 1.4.0-11ubuntu2.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-22365 | MEDIUM4.67 | libpam0g 1.4.0-11ubuntu2.3 fixed in 1.4.0-11ubuntu2.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-10256 | MEDIUM4.67 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-32668 | MEDIUM4.67 | libptexenc1 2021.20210626.59705-1ubuntu0.1 fixed in 2021.20210626.59705-1ubuntu0.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM4.67 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6075 | MEDIUM4.67 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.12 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM4.67 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6075 | MEDIUM4.67 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.12 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libquadmath0 12.3.0-1ubuntu1~22.04 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-35789 | MEDIUM4.67 | librabbitmq4 0.10.0-1ubuntu2 fixed in 0.10.0-1ubuntu2.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50612 | MEDIUM4.67 | libsndfile1 1.0.31-2build1 fixed in 1.0.31-2ubuntu0.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-29088 | MEDIUM4.67 | libsqlite3-0 3.37.2-2ubuntu0.1 fixed in 3.37.2-2ubuntu0.4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0967 | MEDIUM4.67 | libssh-4 0.9.6-2ubuntu0.22.04.1 fixed in 0.9.6-2ubuntu0.22.04.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0967 | MEDIUM4.67 | libssh-gcrypt-4 0.9.6-2ubuntu0.22.04.1 fixed in 0.9.6-2ubuntu0.22.04.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM4.67 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.21 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.25 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | MEDIUM4.67 | libstdc++-11-dev 11.4.0-1ubuntu1~22.04 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libstdc++-11-dev 11.4.0-1ubuntu1~22.04 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libstdc++6 12.3.0-1ubuntu1~22.04 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-10256 | MEDIUM4.67 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-10256 | MEDIUM4.67 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-32668 | MEDIUM4.67 | libsynctex2 2021.20210626.59705-1ubuntu0.1 fixed in 2021.20210626.59705-1ubuntu0.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-32668 | MEDIUM4.67 | libtexlua53 2021.20210626.59705-1ubuntu0.1 fixed in 2021.20210626.59705-1ubuntu0.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-32668 | MEDIUM4.67 | libtexluajit2 2021.20210626.59705-1ubuntu0.1 fixed in 2021.20210626.59705-1ubuntu0.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-3164 | MEDIUM4.67 | libtiff5 4.3.0-6ubuntu0.6 fixed in 4.3.0-6ubuntu0.9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-3576 | MEDIUM4.67 | libtiff5 4.3.0-6ubuntu0.6 fixed in 4.3.0-6ubuntu0.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6228 | MEDIUM4.67 | libtiff5 4.3.0-6ubuntu0.6 fixed in 4.3.0-6ubuntu0.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61143 | MEDIUM4.67 | libtiff5 4.3.0-6ubuntu0.6 fixed in 4.3.0-6ubuntu0.13 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | MEDIUM4.67 | libtsan0 11.4.0-1ubuntu1~22.04 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libtsan0 11.4.0-1ubuntu1~22.04 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libubsan1 12.3.0-1ubuntu1~22.04 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-9714 | MEDIUM4.67 | libxml2 2.9.13+dfsg-1ubuntu0.3 fixed in 2.9.13+dfsg-1ubuntu0.9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4367 | MEDIUM4.67 | libxpm4 1:3.5.12-1ubuntu0.22.04.2 fixed in 1:3.5.12-1ubuntu0.22.04.3 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31637 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45988 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-36402 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-49390 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-164.174 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52880 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26584 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26642 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26643 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-113.123 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26809 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26921 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-119.129 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26925 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26960 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27407 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-153.163 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36972 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-38558 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49958 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50299 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50302 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-53063 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53140 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53217 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56593 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56692 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58083 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21763 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21926 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37964 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38273 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40300 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-161.171 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-71315 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23066 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23105 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23222 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23273 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-177.187 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23340 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23351 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-179.189 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23391 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23449 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31403 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31447 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31454 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31469 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31473 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31507 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31548 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31665 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31673 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31678 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31680 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31758 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43009 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43016 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43030 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43033 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-179.189 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43060 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43091 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43093 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43111 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43153 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43214 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43365 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43406 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43407 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43437 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43456 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43502 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45850 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45864 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45899 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46273 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46304 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46320 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52909 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52958 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53050 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53086 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53159 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53269 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2015-7837 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-8660 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-4095 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-47432 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47658 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-0480 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-38096 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-38457 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-40133 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-4543 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-48628 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48633 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48673 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48703 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48706 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48766 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48772 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48808 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-48887 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48893 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48929 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48976 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48979 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49034 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49069 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49108 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49123 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49124 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49125 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49133 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49134 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49161 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49167 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49173 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49177 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49178 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49203 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49245 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49296 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49303 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49306 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49317 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49333 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49342 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49393 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49420 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49469 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49476 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49484 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49496 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49504 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49516 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49528 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49529 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49531 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49533 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49534 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49539 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49543 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49547 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49552 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49562 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49622 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49636 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49699 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49728 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49742 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49750 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49759 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49764 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49766 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49773 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49783 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49803 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49810 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49829 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49833 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49858 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49901 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49932 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49940 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49943 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49955 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49965 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49971 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49974 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49997 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50002 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50009 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50015 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50016 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50073 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50116 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50166 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50167 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50178 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50195 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50224 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50230 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50232 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50236 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50260 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50266 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50284 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50304 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50316 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50322 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50327 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50332 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50354 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50357 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50380 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50383 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50390 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50393 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50407 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50418 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50425 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50461 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50464 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50467 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50479 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50500 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50527 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50539 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50550 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50554 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50571 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50627 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50704 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50746 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50748 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50772 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50815 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50862 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50863 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50871 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-0160 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-23000 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-101.111 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31082 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-4130 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-42754 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-4515 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-46343 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-5158 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52435 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52443 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52448 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52449 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52454 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52456 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52458 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52462 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52463 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52476 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52477 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52479 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52484 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52485 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52486 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52488 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52493 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52498 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52499 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52500 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52513 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52520 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52522 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52523 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52527 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52528 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52532 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52559 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52563 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52564 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52566 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52567 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52569 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52573 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52574 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52576 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52580 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52582 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52587 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52590 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52591 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52593 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-160.170 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52595 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52601 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52606 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52610 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52615 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52616 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52619 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52622 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52623 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52625 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52629 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-119.129 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52631 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52632 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52634 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52635 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52638 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52641 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52648 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52650 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52652 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52653 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52655 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52656 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52657 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52660 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52662 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52670 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52671 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52672 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52673 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52674 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52675 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52676 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52677 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52680 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52683 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52686 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52690 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52692 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52693 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52694 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52696 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-52698 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52699 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-52700 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52732 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52737 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52750 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52753 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52754 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52761 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52762 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52763 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52774 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52781 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52784 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52788 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52789 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52791 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52803 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52806 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52808 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52809 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52811 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52813 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52815 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52817 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52819 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52821 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52825 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52826 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52828 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52831 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52833 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52834 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52841 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52843 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52845 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52849 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52853 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52856 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52857 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52863 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52865 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52869 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52871 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52873 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52875 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52876 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52877 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52878 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52879 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52881 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52882 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52887 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52888 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52889 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52904 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52905 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52913 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52915 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52918 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52919 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52920 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52939 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52981 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53002 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53008 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53009 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53010 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53036 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53042 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53068 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53093 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53105 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53115 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53146 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53147 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53149 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53151 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53152 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53165 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53168 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53174 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53180 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53198 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53209 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53220 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53221 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53226 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53230 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53231 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53240 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53241 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53245 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53247 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53248 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53258 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53261 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53275 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53287 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53288 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53292 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53309 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53314 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53323 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53324 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53325 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53328 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53332 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53339 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53347 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53348 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53353 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53354 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53355 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53362 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53365 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53366 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53367 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53369 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53370 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53371 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53381 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53382 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53383 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53384 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53385 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53387 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53410 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53421 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53424 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53425 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53429 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53434 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53436 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53438 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53456 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53457 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53460 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53462 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53466 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53472 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53480 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53483 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53488 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53491 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53509 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53518 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53519 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53526 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53529 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53530 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53538 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53539 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53540 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53545 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53546 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53547 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53548 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53558 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53561 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53562 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53568 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53574 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53579 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53584 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53585 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53588 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53593 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53602 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53606 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53609 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53611 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53617 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53618 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53620 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53627 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53628 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53631 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53635 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53647 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53649 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53651 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53657 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53660 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53662 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53666 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53671 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53672 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53682 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53685 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53694 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53698 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53702 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53711 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53712 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53721 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53728 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53743 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53753 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53765 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53767 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53780 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53806 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53822 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53825 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53829 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53836 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53842 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53846 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53847 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53849 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53856 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53867 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53989 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53995 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54001 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54002 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54006 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54013 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54016 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54019 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54023 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54028 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54051 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54052 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54064 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54066 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54067 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54069 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54088 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54091 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54093 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54095 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54099 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54121 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54129 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54134 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54137 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54170 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54173 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54190 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54224 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54234 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54237 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54242 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54254 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54259 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54264 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54271 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54280 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54281 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54299 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54314 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54318 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54324 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-6622 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6915 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-97.107 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-7042 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-0641 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-1151 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-14027 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-22099 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-23848 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-23850 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-25739 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-25741 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26591 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26595 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26600 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26601 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26602 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26603 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26605 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26606 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26608 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26615 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26627 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26629 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26633 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26635 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26636 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26640 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26641 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26644 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26645 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26647 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26651 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26656 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26658 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26659 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26660 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26663 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26668 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26675 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26676 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26677 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-122.132 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26679 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26680 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-119.129 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26684 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26685 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26686 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26687 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26688 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26691 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26695 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26696 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26697 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26700 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-160.170 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26707 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26714 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26715 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26717 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26718 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26719 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26722 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26726 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26727 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26733 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26735 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26737 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26740 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26743 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26744 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26750 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26751 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26752 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26756 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26759 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26766 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26767 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26770 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26771 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26772 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26773 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26774 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26775 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26776 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26777 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26778 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26779 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26787 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26788 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26790 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26795 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26798 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26801 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26802 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26803 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26804 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-26805 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26807 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26811 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26812 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26814 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26816 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26817 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26822 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-130.140 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26825 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26826 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26829 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26833 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26835 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26838 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26839 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26840 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26844 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26845 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26851 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26853 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26855 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26863 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26866 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26870 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26876 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26877 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26880 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-26881 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26889 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26891 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26893 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26900 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26901 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26903 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26916 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26917 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26922 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26926 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26931 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26935 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26937 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26938 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26947 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26948 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26950 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26953 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26964 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26966 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26969 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26970 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26976 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26977 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26980 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26984 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26994 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26999 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27001 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27002 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27004 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27005 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27012 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-122.132 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27013 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27014 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27015 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27016 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27017 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-117.127 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27025 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27032 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27034 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27035 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27037 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27038 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27039 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27041 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27044 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27046 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27047 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27051 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27052 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27054 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27056 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27057 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27059 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27062 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27072 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27074 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27076 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27077 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27078 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27388 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27389 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27390 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27393 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27399 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27400 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27402 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27403 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27410 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27412 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27413 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27414 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27416 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27417 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27418 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27431 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27432 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27435 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27436 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-27437 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-31076 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-33621 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-33847 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-34027 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35247 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35784 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35790 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35794 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35796 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35799 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35801 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35803 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35804 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35805 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35806 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35807 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35808 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35811 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-107.117 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35813 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35815 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35817 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35819 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35821 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-35822 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35823 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-35825 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35826 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35828 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35829 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35830 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35832 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35833 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35835 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-35837 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35839 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35840 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35843 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35844 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35851 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35852 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35853 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-35854 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-35865 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35872 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35875 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35877 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35878 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-35879 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35884 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-35885 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35888 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35890 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35893 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35895 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35897 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35898 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35899 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35900 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35902 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35904 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35907 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35908 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35912 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35915 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35922 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35924 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35925 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35926 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35927 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35930 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35931 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35933 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35934 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35936 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35938 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35940 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35942 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35943 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35944 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35945 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35946 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35947 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35950 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35951 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35956 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35958 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35959 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35969 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35970 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-35971 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35973 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35976 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35978 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35982 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35984 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35988 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35989 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35990 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35995 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35997 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35998 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35999 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36000 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36004 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36005 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36006 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36007 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36008 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36009 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36014 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36017 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36020 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36021 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36025 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36026 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36029 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36244 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36270 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36286 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36476 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36478 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36479 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36484 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36489 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36889 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36893 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36900 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36901 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-119.129 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36902 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36903 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36905 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36908 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36909 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36911 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36917 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36918 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36919 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36920 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36922 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36924 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36929 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36933 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36937 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36938 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36939 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36941 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36945 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36946 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36947 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-36948 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36951 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36953 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36954 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36955 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36957 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36959 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36964 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36965 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36966 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36967 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36969 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36975 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-37021 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-37356 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38543 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38546 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38547 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38549 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38553 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-130.140 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38554 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38557 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38564 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38565 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-38567 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38571 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38579 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38582 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-38589 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38590 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38591 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38594 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38597 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38598 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38600 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38602 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38607 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38608 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38611 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38615 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38618 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-38619 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38623 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-38624 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38625 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38632 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38633 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38634 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38637 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38661 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38780 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39276 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39282 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39292 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-119.129 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39298 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39301 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39466 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39468 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39472 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39475 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39476 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39484 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-119.129 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39488 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39489 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39490 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39493 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39497 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-39505 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-39506 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-39507 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-39509 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40904 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40908 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40910 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-130.140 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40911 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40912 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40914 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40915 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40916 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40931 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40932 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40934 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40937 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40941 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40942 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40945 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40957 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40959 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40960 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40961 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40963 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40965 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40966 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40967 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40968 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40970 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40971 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40972 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40973 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-130.140 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40975 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40976 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40977 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40979 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40980 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40981 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40983 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40984 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40987 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40988 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40990 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40995 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40998 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40999 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41001 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41002 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41006 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41008 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41009 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-122.132 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41015 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41016 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41017 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41019 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41022 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41023 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41030 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41031 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41034 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41035 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41036 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41041 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41044 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41047 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41048 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41055 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41060 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41062 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41063 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41064 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41065 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41066 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41067 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41068 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41072 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41075 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41077 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41078 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41079 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41080 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41081 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41082 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41088 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41089 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41093 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41095 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41097 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41098 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42067 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42068 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42070 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42076 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42077 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42079 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42080 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42082 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42084 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42085 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42087 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42089 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42090 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42091 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42095 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42096 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42097 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42098 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42101 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42106 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42109 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42110 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42115 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42122 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42124 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42125 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42126 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42127 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42128 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42129 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42137 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42139 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42140 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42145 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42153 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42223 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42232 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42236 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42239 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42240 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42244 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42246 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42247 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42252 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42259 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42265 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42267 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42269 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42270 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42272 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42273 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42274 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42276 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42277 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42281 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42283 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42286 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42288 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42289 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42290 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42291 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42295 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42296 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42297 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42299 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42304 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42305 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42306 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42309 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42310 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42311 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42312 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42315 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42318 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42319 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42320 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42321 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42322 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43098 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43817 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43823 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43824 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43828 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43829 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43831 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43832 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43835 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-43844 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43846 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43849 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43853 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43854 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43856 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-43860 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43861 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43863 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43867 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43869 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43870 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43871 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43872 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-43875 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43879 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43880 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43884 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-43889 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43890 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-43893 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-43894 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43899 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43902 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43904 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-130.140 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43905 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43907 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43908 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43909 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43911 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43912 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43914 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44931 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44935 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44938 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44939 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44944 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44946 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-44947 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-44948 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44950 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44958 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44960 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44961 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44962 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44963 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44965 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44966 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44969 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44970 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44971 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44982 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44988 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44989 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44990 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44995 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45006 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-45007 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45008 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45009 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45010 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45011 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45015 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45016 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-124.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45018 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45021 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45025 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45028 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45828 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46675 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46676 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46677 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46678 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46681 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46685 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46689 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46702 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46705 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46707 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46714 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46715 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46716 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46717 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46718 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46719 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46720 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46721 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46726 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46727 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46728 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46730 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46732 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46733 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46737 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46739 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46742 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46745 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46748 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46749 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46750 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46751 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46752 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46753 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46754 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46755 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46761 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46762 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46763 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46765 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46770 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46771 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46775 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46777 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46780 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46781 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46783 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46784 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46791 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46795 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46802 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46803 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46805 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46806 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46807 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46808 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46809 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46810 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46816 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46817 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46819 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46822 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46823 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46829 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46832 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46834 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46835 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46840 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46841 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46842 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46843 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46848 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46855 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46857 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46860 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46861 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47141 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47143 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47408 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47658 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47661 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47662 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47663 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47664 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47665 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47666 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47667 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47669 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47671 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47673 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47674 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47678 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47683 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47684 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47690 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47699 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47703 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47704 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47705 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47706 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47707 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47709 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47710 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47712 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47713 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47720 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47728 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47734 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47735 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47736 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47737 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47739 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47740 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47749 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47756 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47794 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47809 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-48873 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-48881 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49568 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49571 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49851 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49856 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49858 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49863 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49867 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49868 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49870 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49871 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49875 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49877 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49878 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49879 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49881 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49886 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49888 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49890 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49891 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49892 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49893 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49896 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49898 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49899 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49901 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49902 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49904 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49905 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49906 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49907 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49908 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49909 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49910 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49911 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49912 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49913 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49914 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49915 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49916 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49917 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49918 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49919 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49920 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49921 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49922 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49923 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49925 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49927 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49929 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49932 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49933 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49935 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49938 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49939 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49940 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49944 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49945 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49946 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49948 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49949 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49952 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49954 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49955 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49957 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49959 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49962 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49963 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49970 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49973 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49974 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49975 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49977 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49978 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49985 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49987 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49988 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49990 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49994 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50000 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50001 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50002 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50003 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50008 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50012 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50013 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50014 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50015 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50017 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50019 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50024 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50028 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50031 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50034 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50038 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50039 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50040 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50041 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50045 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50046 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50048 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50049 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50056 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50058 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50060 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-179.189 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50062 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50072 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50085 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50093 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50095 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50096 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50098 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50099 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50101 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50103 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50110 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50116 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50117 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50134 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50138 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50141 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50142 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50146 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50148 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50153 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50156 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50160 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50162 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50163 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50166 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50167 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50168 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50171 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50179 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50182 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50184 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50185 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50187 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50188 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50189 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50191 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50194 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50195 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50196 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50198 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50199 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50201 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50202 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50205 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50208 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50218 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50229 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50232 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50233 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50236 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50237 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50244 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50245 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50248 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-138.148 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50249 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50256 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-138.148 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50258 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50259 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50265 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50271 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50272 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50273 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50284 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50285 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50287 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50289 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50290 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50292 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50295 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50296 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50298 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50304 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-52559 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-52560 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53042 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53051 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-143.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53055 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53056 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53058 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53066 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53079 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53090 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-164.174 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53091 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53097 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53112 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53113 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53114 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53119 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53120 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53121 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53122 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53125 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53127 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53129 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53130 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53131 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53138 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53144 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53145 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53146 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53148 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53151 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53157 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53158 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53161 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53164 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-131.141 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53172 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53175 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53180 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53181 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53183 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53184 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53187 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53190 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53195 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53196 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53198 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53210 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53215 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53219 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53220 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53221 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53224 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53226 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53234 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53680 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53685 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53687 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53690 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-54683 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-55881 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-55916 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56368 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56369 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56531 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56532 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56533 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56539 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56544 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56557 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56562 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56565 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56566 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56567 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56569 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56572 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56574 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56575 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56578 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56583 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56584 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56586 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56587 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56588 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56589 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56590 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56591 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56592 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56594 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56607 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56610 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56611 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56622 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56623 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56625 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56629 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56630 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56634 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56636 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56639 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56641 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56643 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56644 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56645 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56647 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56648 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56657 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56659 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56660 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56665 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56670 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56671 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56677 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56679 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56681 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56688 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56690 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56691 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56694 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56698 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56700 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56701 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56703 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56705 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56707 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56709 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56712 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56715 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56716 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56717 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56718 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56719 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56720 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56722 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56723 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56724 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56726 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56727 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56728 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56739 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56745 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56746 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56747 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56748 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56754 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56756 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56767 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56769 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56770 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56774 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56776 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56777 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56778 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56779 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56780 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56782 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56785 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56787 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57802 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57804 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57807 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57809 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57834 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57841 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57843 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57852 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57872 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57875 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57882 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57883 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57884 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57888 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57889 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57890 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57895 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57897 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57901 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57902 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57903 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57922 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57924 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57931 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57938 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57939 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57940 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57946 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57947 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57948 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57950 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57952 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57973 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57975 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57976 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57977 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57978 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57981 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57986 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57993 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57996 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-153.163 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57999 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58001 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58005 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58010 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58011 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58012 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58016 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58017 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58018 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58019 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58020 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58051 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58052 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58053 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58058 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58063 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58071 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58076 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58077 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58079 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58085 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58086 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58089 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58090 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58094 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58095 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58096 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58097 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58098 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58100 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58238 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58239 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58241 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21629 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21634 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21635 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21636 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21637 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21638 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21639 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21640 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21646 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21648 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21649 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21653 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21656 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21658 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21664 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21665 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21666 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21667 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21669 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21672 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21673 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21678 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21682 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21683 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21684 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21689 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21690 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21694 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21696 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21697 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21699 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21707 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21708 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21711 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21712 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21721 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21723 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21728 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21730 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21736 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21738 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21744 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21745 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21748 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21749 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21750 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21752 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21765 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21766 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21767 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21768 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21776 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21779 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21781 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21787 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21792 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21795 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21796 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21799 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21801 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21802 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21804 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21806 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21814 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21816 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21817 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21819 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21820 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21821 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21823 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21826 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21830 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21831 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21832 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21833 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21835 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21838 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21844 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21846 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21853 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21859 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21861 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21862 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21865 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21866 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21871 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21872 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21875 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21877 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21881 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21885 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21888 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21891 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21894 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21898 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21899 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21904 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21908 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21909 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21910 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21912 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21916 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21917 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21918 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21922 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21925 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21931 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21935 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21941 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21944 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21948 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21955 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21956 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21957 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21959 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21971 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21972 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21976 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21986 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21992 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21994 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21996 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22007 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22008 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22010 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22018 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22019 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22021 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22025 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22026 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22028 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22042 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22043 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22045 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22053 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22055 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22057 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22058 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22062 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22063 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22071 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22072 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22073 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22081 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22086 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22089 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22090 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22103 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22105 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22109 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22111 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22113 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22124 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22125 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22127 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23130 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23131 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23132 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23136 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23138 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23140 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23141 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23143 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23144 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23145 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23146 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23147 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23148 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23150 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23155 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23159 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23160 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23161 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23162 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23163 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37740 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37741 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37742 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37743 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37744 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37745 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37746 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37747 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37756 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37757 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37758 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37765 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37766 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37767 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37768 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37770 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37771 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37773 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37775 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37781 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37787 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37788 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37790 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37792 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37794 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37805 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37806 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37807 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37808 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37811 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37812 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37820 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37824 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37829 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37830 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37833 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37834 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37836 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37841 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37842 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37844 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37850 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37851 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37852 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37853 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37855 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37856 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37857 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37858 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37859 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37862 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37867 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37870 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37871 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37875 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37876 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37877 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37878 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37880 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37881 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37883 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37884 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37889 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37905 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37907 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37909 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37911 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37912 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37925 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37930 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37931 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37932 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-143.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37937 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37938 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37940 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37945 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37948 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37949 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37951 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37954 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37956 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37958 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37959 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37961 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37963 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37967 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37968 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37969 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37970 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37980 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37982 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37983 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37984 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37989 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37990 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37992 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37994 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37995 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37997 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-143.153 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37998 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38001 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-143.153 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-38003 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-152.162 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38005 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38006 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38009 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38011 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38014 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38015 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38020 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38023 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38029 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38031 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-152.162 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38033 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38034 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-152.162 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38035 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-152.162 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38036 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38037 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-152.162 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38038 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38039 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38040 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38041 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38042 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38043 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-152.162 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38044 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-152.162 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38045 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38047 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38057 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38058 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-152.162 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38059 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38060 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38061 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-152.162 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38062 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38063 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38064 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38065 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-152.162 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38066 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-152.162 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38067 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-38070 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38071 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38072 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-152.162 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38074 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38075 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-152.162 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38080 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38084 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38086 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38090 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38092 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38094 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38095 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38096 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38097 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38098 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38099 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38100 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38105 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38115 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38119 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38120 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38122 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38125 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38126 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38127 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38135 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38136 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38138 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38140 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38143 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38145 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38147 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38148 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38160 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38161 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38162 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38163 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38165 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38166 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38167 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38168 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38173 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38174 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38177 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-143.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38181 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38184 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38185 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38189 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38190 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38191 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-38192 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38193 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38194 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38197 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38199 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38200 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38202 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38203 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38205 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38207 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38208 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38214 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38215 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38218 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38219 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38222 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38225 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38229 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38231 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38237 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38244 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38251 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38261 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38262 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38263 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38264 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38269 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38272 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38275 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38285 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38293 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38300 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38305 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38310 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38312 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38319 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38321 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38324 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38326 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38328 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38331 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38332 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38333 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38334 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38335 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38336 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38337 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38343 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38344 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38345 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38347 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38353 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38359 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38360 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38362 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38363 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38368 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38371 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38373 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38384 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38386 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38387 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38391 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38399 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38400 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38406 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38408 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38409 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38410 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38412 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38418 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38419 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38420 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38424 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38426 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38430 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38436 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38438 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38439 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38441 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38444 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38449 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38457 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38458 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38460 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38465 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38466 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38467 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38468 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38470 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38473 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38474 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38478 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38480 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38481 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38487 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38491 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38495 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38498 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38499 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38503 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38507 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38513 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38514 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38516 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38520 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38528 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38531 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38539 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38540 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38542 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38544 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38546 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38560 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38569 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38576 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38577 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38578 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38581 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38583 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38590 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38591 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38601 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38602 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38604 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38608 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38609 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38612 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38614 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38615 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38621 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38622 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38623 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38624 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38626 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38630 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38634 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38635 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38637 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-38639 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38643 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38644 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38645 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38650 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38659 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38663 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38664 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38665 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38668 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38671 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38678 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38683 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38684 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38691 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38692 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38693 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38694 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38695 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38696 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38698 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38700 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38701 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38705 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38706 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38709 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38710 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38711 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38712 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38716 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38721 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38725 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38727 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-160.170 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38732 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39675 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39676 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39677 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39681 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39684 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39692 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39693 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39703 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39705 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39706 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39707 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39709 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39714 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39715 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39716 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39720 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39724 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39732 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39734 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39736 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39737 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39742 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39745 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39746 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39747 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39748 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39752 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39753 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39756 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39762 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39763 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39764 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39770 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39771 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39772 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39773 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39779 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39781 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39782 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39787 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39789 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39794 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39795 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39798 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39800 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39801 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39808 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39812 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39819 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39827 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39829 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39833 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39838 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39844 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39845 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39846 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39847 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39848 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39850 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39851 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39865 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39876 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39885 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39886 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39889 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39894 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39902 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39907 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39908 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39920 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39923 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39925 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39929 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39931 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39932 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39933 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39934 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39937 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39940 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39942 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39947 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39949 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39953 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39989 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39990 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40005 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40020 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40026 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40027 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40029 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40030 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40040 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-40042 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40044 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40049 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40053 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40057 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40070 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40075 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40078 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40088 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40092 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40094 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40099 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40100 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40102 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40103 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40104 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40105 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40109 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40115 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40125 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40140 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40153 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40160 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40164 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40171 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40195 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40196 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40205 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40211 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40219 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40231 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40251 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40253 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40264 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40280 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40283 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40284 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40287 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40305 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40325 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40334 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40339 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40346 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40347 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40360 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40362 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40363 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68171 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68173 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68176 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68178 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68185 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68188 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68192 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68193 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68194 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68200 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68204 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68206 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68211 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68219 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68223 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68227 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68229 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68231 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68236 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68244 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68261 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68265 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68281 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68283 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68288 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68295 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68297 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68307 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68308 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68309 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68310 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68313 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68317 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68321 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68331 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68333 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68334 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68336 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68337 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68340 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68345 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68358 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68363 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68365 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68372 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68378 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68379 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68725 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68732 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68734 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68758 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68774 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68776 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68778 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68780 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68783 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68785 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68794 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68795 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68798 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68802 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68803 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68813 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68814 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68818 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68820 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68821 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68822 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71064 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71077 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71079 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71081 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71083 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71084 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71085 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71087 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71094 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71095 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71096 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71097 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71098 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71102 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71104 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71105 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71107 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71108 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71109 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71113 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71114 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71115 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71118 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71120 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71121 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71125 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71127 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71131 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71132 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71147 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71150 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71154 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71158 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71160 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71161 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71163 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71180 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71182 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71183 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71184 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71185 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71186 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71188 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71190 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71191 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71194 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71202 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71204 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71222 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71223 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71227 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71229 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71232 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71233 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71235 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71236 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71237 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71239 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71265 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71266 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71267 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71268 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71269 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71272 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71273 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71285 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71287 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71289 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71290 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71291 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71292 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71293 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71294 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71295 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71297 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71299 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71300 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71302 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22976 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22977 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22979 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22982 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22990 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22991 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-22992 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22996 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22997 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-22999 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23000 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23003 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-23011 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23019 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23020 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23021 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23026 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23031 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23038 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23047 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23058 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23060 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-174.184 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23061 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23063 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23064 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23069 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23075 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23080 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23084 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23085 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23086 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23087 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23088 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23090 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23091 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23093 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23095 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23096 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23097 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23100 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23108 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23113 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23119 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23120 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23121 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23124 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23125 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23128 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23133 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23137 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23138 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23141 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23145 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23146 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23150 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23154 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23157 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23164 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23170 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23190 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23196 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23202 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23206 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23213 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23214 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23215 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23217 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23220 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23228 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23229 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23236 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23237 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23238 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23241 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23242 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23247 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23255 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23256 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23257 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23258 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23259 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23260 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23261 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23264 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23265 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23266 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23267 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23272 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23274 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-179.189 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23276 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23277 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23278 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23279 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23285 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23286 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23287 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23289 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23290 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23291 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23292 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23293 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23296 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23298 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23300 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23303 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23304 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23307 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23310 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23312 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23324 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23330 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23334 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23335 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23339 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23347 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23352 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23356 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23357 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23362 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23365 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23367 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23368 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23370 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23371 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23374 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23379 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23381 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23382 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23389 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23396 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23398 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23399 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23401 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23403 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23404 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23405 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23409 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23420 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23434 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23438 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23439 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23442 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23446 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23460 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23462 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23465 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23468 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23472 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23474 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31391 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31394 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31400 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31407 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31410 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31411 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31412 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31415 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31416 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31418 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31420 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31421 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31422 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31423 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31424 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31425 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31427 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31428 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31441 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31450 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31451 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31461 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31462 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31467 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31480 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31483 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31486 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31487 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31492 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31495 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31496 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31497 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31498 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31503 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31509 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31510 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31512 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31515 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31518 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31519 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31520 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31521 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31522 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31524 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31531 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31533 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-179.189 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31537 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31540 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31545 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31546 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31549 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31550 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31551 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31552 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31555 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31557 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31560 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31565 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31577 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31579 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31585 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31590 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31592 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31594 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31595 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31596 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31599 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31603 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31605 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31606 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31610 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31615 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31616 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31617 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31618 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31619 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31623 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31624 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31625 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31628 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31630 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31634 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31642 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31651 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31658 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31660 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31661 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31662 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31664 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31670 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31671 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31672 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31674 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31675 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31676 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31677 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31679 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31681 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31682 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31684 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31687 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31692 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31698 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31699 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31701 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31704 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31721 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31722 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31723 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31724 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31725 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31726 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31737 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31738 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31749 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31752 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31754 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31755 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31756 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31762 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31763 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31767 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31770 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31773 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31777 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31781 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43014 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43021 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43022 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43024 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43025 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43026 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43028 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43032 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43035 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43036 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43041 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43042 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43043 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43045 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43046 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43048 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43054 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43058 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43061 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43062 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43064 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43065 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43066 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43068 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43069 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43072 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43073 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43077 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-179.189 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43079 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43080 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43085 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43088 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43089 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43098 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43099 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43101 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43103 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43104 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43105 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43107 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43109 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43113 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43115 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43118 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43119 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43123 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43124 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43127 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43129 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43130 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43131 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43132 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43135 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43136 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43137 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43139 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43140 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43143 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43145 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43147 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43148 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43149 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43152 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43156 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43159 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43161 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43162 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43165 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43167 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43168 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43170 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43171 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43172 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43173 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43182 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43183 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43187 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43189 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43191 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43194 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43195 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43200 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43201 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43202 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43204 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43209 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43213 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43216 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43218 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43219 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43220 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43223 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43225 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43227 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43228 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43230 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43231 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43234 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43242 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43243 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43244 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43246 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43251 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43253 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43255 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43257 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43261 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43262 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43264 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43266 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43267 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43268 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43269 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43270 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43271 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43273 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43277 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43287 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43288 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43289 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43292 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43294 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43295 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43296 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43298 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43299 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43300 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43302 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43305 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43306 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43308 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43309 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43310 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43311 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43312 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43313 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43314 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43315 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43316 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43317 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43318 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43319 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43320 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43327 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43333 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43338 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43340 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43343 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43344 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43350 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43355 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43357 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43359 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43361 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43362 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43363 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43381 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43382 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43387 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43398 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43400 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43405 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43409 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43410 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43411 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43413 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43416 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43419 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43421 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43424 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43425 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43428 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43429 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43432 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43436 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43445 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43451 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43452 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43459 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43466 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43469 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43471 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43472 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43473 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43474 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43475 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43483 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43491 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43492 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43496 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45834 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45835 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45836 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45840 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45842 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45843 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45846 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45847 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45848 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45855 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45857 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45873 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45890 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45904 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45912 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45915 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45917 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45919 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45923 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45924 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45930 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45934 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45940 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45941 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45944 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45948 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45954 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45960 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45961 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45964 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45965 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45968 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45969 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45974 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45978 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45981 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45983 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45985 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45986 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45987 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45997 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45999 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46000 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46002 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46003 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46009 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46012 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46014 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46018 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46019 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46021 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46023 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46026 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46027 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46028 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-179.189 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46032 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46037 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46038 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46040 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46044 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46046 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46049 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46050 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46051 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46059 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46070 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46072 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46077 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46078 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46080 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46082 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46083 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46086 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46088 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46091 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46092 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46098 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46101 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46102 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46103 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46107 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46108 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46127 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46128 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46132 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46137 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46146 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46151 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46153 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46157 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46158 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46160 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46161 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46167 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46168 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46169 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46170 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46172 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46178 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46184 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46186 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46193 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46196 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46200 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46214 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46220 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46225 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46226 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46229 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46231 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46233 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46235 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46236 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46247 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46302 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46303 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46321 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46322 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52913 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52915 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52916 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52921 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52925 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52926 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52927 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52928 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52929 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52930 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52936 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52937 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52939 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52944 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52946 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-52948 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52954 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52960 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52963 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52970 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52972 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52975 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52977 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52981 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52984 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52985 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52988 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52990 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52995 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52999 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53001 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53003 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53012 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53015 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53017 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53018 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53021 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53022 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53023 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53034 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53037 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53039 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53056 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53064 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53066 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53069 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53074 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53076 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53077 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53080 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53083 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53088 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53107 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53122 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53128 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53134 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53139 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53150 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53167 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53168 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53181 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53199 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53208 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53218 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53219 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53220 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53221 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-53227 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53245 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53252 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53263 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53284 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53287 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53289 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53291 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53292 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53295 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53304 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53306 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53313 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53314 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53317 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53320 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53325 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53327 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53331 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53332 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53337 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53339 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53345 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53349 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53353 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53358 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-13693 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-12928 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-12929 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-3114 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49535 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49651 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31085 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-89.99 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-4133 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4134 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52429 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52467 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52470 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52516 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52583 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52607 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52643 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53074 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-6039 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-0340 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-23849 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-23851 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26813 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26820 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26879 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26896 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-160.170 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26906 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26920 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26973 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26993 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27010 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27011 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27073 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41004 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-43834 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46826 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-138.148 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49965 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49968 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50009 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53093 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53101 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53128 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53194 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-54458 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56599 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56751 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56763 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58237 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21645 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21693 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21839 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21848 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21878 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21924 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21951 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21962 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21963 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21964 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21970 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21975 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21981 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22005 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22014 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22044 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22054 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22066 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22075 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37800 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38152 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38575 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39728 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71304 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71313 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23103 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23198 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23336 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23444 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31446 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31448 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31453 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31667 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31771 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43071 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43180 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43211 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43352 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43353 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43480 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43484 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45838 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45841 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45844 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45858 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45862 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45868 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45869 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45870 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45871 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45872 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45875 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45877 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45883 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45911 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46147 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46245 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46249 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46252 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46253 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46254 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46280 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46291 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46292 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46299 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46307 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46312 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52982 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53035 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53047 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53048 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53060 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53061 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53063 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53065 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53070 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53073 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53082 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53093 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53096 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53106 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53111 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53135 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53146 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53147 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53158 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53177 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53207 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53213 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53225 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53226 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53229 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53232 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53236 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53237 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53238 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53249 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53258 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53265 | MEDIUM4.67 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM4.67 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6075 | MEDIUM4.67 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.12 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM4.67 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6075 | MEDIUM4.67 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.12 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42308 | MEDIUM4.67 | Pillow 10.1.0 fixed in 12.2.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42310 | MEDIUM4.67 | Pillow 10.1.0 fixed in 12.2.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-25645 | MEDIUM4.67 | requests 2.31.0 fixed in 2.33.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | MEDIUM4.64 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.25 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl 5.34.0-3ubuntu1.2 fixed in 5.34.0-3ubuntu1.7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl-base 5.34.0-3ubuntu1.2 fixed in 5.34.0-3ubuntu1.7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-38428 | MEDIUM4.64 | wget 1.21.2-2ubuntu1 fixed in 1.21.2-2ubuntu1.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48795 | MEDIUM4.6 | openssh-client 1:8.9p1-3ubuntu0.4 fixed in 1:8.9p1-3ubuntu0.5 | 93.3% Actively Exploited | Post-Exploit |
| CVE-2026-41079 | MEDIUM4.59 | libcups2 2.4.1op1-1ubuntu4.7 fixed in 2.4.1op1-1ubuntu4.20 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-1489 | MEDIUM4.59 | libglib2.0-0 2.72.4-0ubuntu2.2 fixed in 2.72.4-0ubuntu2.9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58055 | MEDIUM4.59 | libnghttp2-14 1.43.0-1build3 fixed in 1.43.0-1ubuntu0.4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-34064 | MEDIUM4.59 | Jinja2 3.1.2 fixed in 3.1.4 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-21883 | MEDIUM4.59 | bokeh 3.3.0 fixed in 3.8.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44727 | MEDIUM4.59 | jupyter_server 2.8.0 fixed in 2.20.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-3109 | MEDIUM4.5 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2023-46751 | MEDIUM4.5 | ghostscript 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.6 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-52006 | MEDIUM4.5 | git 1:2.34.1-1ubuntu1.10 fixed in 1:2.34.1-1ubuntu1.12 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3497 | MEDIUM4.5 | openssh-client 1:8.9p1-3ubuntu0.4 fixed in 1:8.9p1-3ubuntu0.14 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-40735 | MEDIUM4.5 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.16 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5363 | MEDIUM4.5 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.12 | 3.3% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6952 | MEDIUM4.5 | patch 2.7.6-7build2 No fix yet | 8.4% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5344 | MEDIUM4.5 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.13 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5344 | MEDIUM4.5 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.13 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5344 | MEDIUM4.5 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.13 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-52615 | MEDIUM4.5 | libavahi-client3 0.8-5ubuntu5.1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-52616 | MEDIUM4.5 | libavahi-client3 0.8-5ubuntu5.1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-52615 | MEDIUM4.5 | libavahi-common-data 0.8-5ubuntu5.1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-52616 | MEDIUM4.5 | libavahi-common-data 0.8-5ubuntu5.1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-52615 | MEDIUM4.5 | libavahi-common3 0.8-5ubuntu5.1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-52616 | MEDIUM4.5 | libavahi-common3 0.8-5ubuntu5.1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-3341 | MEDIUM4.5 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-0518 | MEDIUM4.5 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-3341 | MEDIUM4.5 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-0518 | MEDIUM4.5 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-3341 | MEDIUM4.5 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-0518 | MEDIUM4.5 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-3341 | MEDIUM4.5 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-0518 | MEDIUM4.5 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-3341 | MEDIUM4.5 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-0518 | MEDIUM4.5 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc-bin 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.13 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-bin 2.35-0ubuntu3.4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc-dev-bin 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.13 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-dev-bin 2.35-0ubuntu3.4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc6 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.13 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6 2.35-0ubuntu3.4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc6-dev 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.13 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6-dev 2.35-0ubuntu3.4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-34979 | MEDIUM4.5 | libcups2 2.4.1op1-1ubuntu4.7 fixed in 2.4.1op1-1ubuntu4.20 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-28834 | MEDIUM4.5 | libgnutls30 3.7.3-4ubuntu1.2 fixed in 3.7.3-4ubuntu1.5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-14831 | MEDIUM4.5 | libgnutls30 3.7.3-4ubuntu1.2 fixed in 3.7.3-4ubuntu1.8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM4.5 | libgnutls30 3.7.3-4ubuntu1.2 fixed in 3.7.3-4ubuntu1.9 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-52722 | MEDIUM4.5 | libgs9 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-33869 | MEDIUM4.5 | libgs9 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-52722 | MEDIUM4.5 | libgs9-common 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-33869 | MEDIUM4.5 | libgs9-common 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | liblzma5 5.2.5-2ubuntu1 fixed in 5.2.5-2ubuntu1.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-50952 | MEDIUM4.5 | libopenjp2-7 2.4.0-6 fixed in 2.4.0-6ubuntu0.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3341 | MEDIUM4.5 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-0518 | MEDIUM4.5 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-40217 | MEDIUM4.5 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-12084 | MEDIUM4.5 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.14 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-40217 | MEDIUM4.5 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-12084 | MEDIUM4.5 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.14 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-2975 | MEDIUM4.5 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.12 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.25 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.25 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3341 | MEDIUM4.5 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-0518 | MEDIUM4.5 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-3341 | MEDIUM4.5 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-0518 | MEDIUM4.5 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-8851 | MEDIUM4.5 | libtiff5 4.3.0-6ubuntu0.6 fixed in 4.3.0-6ubuntu0.11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-3523 | MEDIUM4.5 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-50700 | MEDIUM4.5 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53726 | MEDIUM4.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54092 | MEDIUM4.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54181 | MEDIUM4.5 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26886 | MEDIUM4.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-117.127 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-35857 | MEDIUM4.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-47689 | MEDIUM4.5 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-39968 | MEDIUM4.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39972 | MEDIUM4.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40204 | MEDIUM4.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40353 | MEDIUM4.5 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68367 | MEDIUM4.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71225 | MEDIUM4.5 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23457 | MEDIUM4.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53194 | MEDIUM4.5 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-24858 | MEDIUM4.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-24860 | MEDIUM4.5 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-40217 | MEDIUM4.5 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-12084 | MEDIUM4.5 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.14 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-40217 | MEDIUM4.5 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-12084 | MEDIUM4.5 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.14 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48525 | MEDIUM4.5 | PyJWT 2.8.0 fixed in 2.13.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34073 | MEDIUM4.5 | cryptography 41.0.4 fixed in 46.0.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45409 | MEDIUM4.5 | idna 3.4 fixed in 3.15 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59927 | MEDIUM4.5 | mistune 3.0.1 fixed in 3.3.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-4565 | MEDIUM4.5 | protobuf 4.24.3 fixed in 4.25.8, 5.29.5, 6.31.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27448 | MEDIUM4.5 | pyOpenSSL 23.2.0 fixed in 26.0.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47081 | MEDIUM4.5 | requests 2.31.0 fixed in 2.32.4 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-67725 | MEDIUM4.5 | tornado 6.3.3 fixed in 6.5.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-67726 | MEDIUM4.5 | tornado 6.3.3 fixed in 6.5.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-35536 | MEDIUM4.5 | tornado 6.3.3 fixed in 6.5.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44431 | MEDIUM4.5 | urllib3 2.0.7 fixed in 2.7.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1594 | MEDIUM4.49 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-29506 | MEDIUM4.49 | ghostscript 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.9 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2024-52005 | MEDIUM4.49 | git 1:2.34.1-1ubuntu1.10 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-47162 | MEDIUM4.49 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.32 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-47162 | MEDIUM4.49 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.32 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-47162 | MEDIUM4.49 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.32 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-7264 | MEDIUM4.48 | curl 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.17 | 17.3% High Exploitation Risk | Post-Exploit |
| CVE-2024-7264 | MEDIUM4.48 | libcurl3-gnutls 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.17 | 17.3% High Exploitation Risk | Post-Exploit |
| CVE-2024-7264 | MEDIUM4.48 | libcurl4 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.17 | 17.3% High Exploitation Risk | Post-Exploit |
| CVE-2023-51385 | MEDIUM4.48 | openssh-client 1:8.9p1-3ubuntu0.4 fixed in 1:8.9p1-3ubuntu0.6 | 19.8% High Exploitation Risk | Post-Exploit |
| CVE-2026-34990 | MEDIUM4.42 | libcups2 2.4.1op1-1ubuntu4.7 fixed in 2.4.1op1-1ubuntu4.20 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-53841 | MEDIUM4.42 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39970 | MEDIUM4.42 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40217 | MEDIUM4.42 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40338 | MEDIUM4.42 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40343 | MEDIUM4.42 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-28085 | MEDIUM4.4 | libblkid1 2.37.2-4ubuntu3 fixed in 2.37.2-4ubuntu3.4 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-29511 | MEDIUM4.4 | libgs9 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-29511 | MEDIUM4.4 | libgs9-common 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28085 | MEDIUM4.4 | libmount1 2.37.2-4ubuntu3 fixed in 2.37.2-4ubuntu3.4 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28085 | MEDIUM4.4 | libsmartcols1 2.37.2-4ubuntu3 fixed in 2.37.2-4ubuntu3.4 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28085 | MEDIUM4.4 | libuuid1 2.37.2-4ubuntu3 fixed in 2.37.2-4ubuntu3.4 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-52798 | MEDIUM4.4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-35845 | MEDIUM4.4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-38541 | MEDIUM4.4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-38605 | MEDIUM4.4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-32487 | MEDIUM4.39 | less 590-1ubuntu0.22.04.1 fixed in 590-1ubuntu0.22.04.3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-4516 | MEDIUM4.33 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4516 | MEDIUM4.33 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48666 | MEDIUM4.33 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-50721 | MEDIUM4.33 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40178 | MEDIUM4.33 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71193 | MEDIUM4.33 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23035 | MEDIUM4.33 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4516 | MEDIUM4.33 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4516 | MEDIUM4.33 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-6121 | MEDIUM4.3 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-12360 | MEDIUM4.26 | texlive-binaries 2021.20210626.59705-1ubuntu0.1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-12493 | MEDIUM4.26 | texlive-binaries 2021.20210626.59705-1ubuntu0.1 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-57360 | MEDIUM4.25 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-28835 | MEDIUM4.25 | libgnutls30 3.7.3-4ubuntu1.2 fixed in 3.7.3-4ubuntu1.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libgssapi-krb5-2 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libk5crypto3 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5-3 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5support0 1.19.2-2ubuntu0.2 fixed in 1.19.2-2ubuntu0.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-0397 | MEDIUM4.25 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-0397 | MEDIUM4.25 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM4.25 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.25 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61145 | MEDIUM4.25 | libtiff5 4.3.0-6ubuntu0.6 fixed in 4.3.0-6ubuntu0.12 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52633 | MEDIUM4.25 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40121 | MEDIUM4.25 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23180 | MEDIUM4.25 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-0397 | MEDIUM4.25 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-0397 | MEDIUM4.25 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-34982 | MEDIUM4.18 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.27 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-52859 | MEDIUM4.18 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.32 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-34982 | MEDIUM4.18 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.27 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-52859 | MEDIUM4.18 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.32 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-34982 | MEDIUM4.18 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.27 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-52859 | MEDIUM4.18 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.32 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-24842 | MEDIUM4.18 | tar 6.1.15 fixed in 7.5.7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-34324 | MEDIUM4.17 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | MEDIUM4.13 | curl 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.22 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | curl 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.25 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl3-gnutls 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.22 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl3-gnutls 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.25 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl4 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.22 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl4 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.25 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-35385 | MEDIUM4.13 | openssh-client 1:8.9p1-3ubuntu0.4 fixed in 1:8.9p1-3ubuntu0.15 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-35386 | MEDIUM4.13 | openssh-client 1:8.9p1-3ubuntu0.4 fixed in 1:8.9p1-3ubuntu0.15 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-35414 | MEDIUM4.13 | openssh-client 1:8.9p1-3ubuntu0.4 fixed in 1:8.9p1-3ubuntu0.15 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-28387 | MEDIUM4.13 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.23 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-26465 | MEDIUM4.08 | openssh-client 1:8.9p1-3ubuntu0.4 fixed in 1:8.9p1-3ubuntu0.11 | 7.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-4039 | MEDIUM4.08 | gcc-11-base 11.4.0-1ubuntu1~22.04 fixed in 11.4.0-1ubuntu1~22.04.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | gcc-12-base 12.3.0-1ubuntu1~22.04 fixed in 12.3.0-1ubuntu1~22.04.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libasan6 11.4.0-1ubuntu1~22.04 fixed in 11.4.0-1ubuntu1~22.04.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libatomic1 12.3.0-1ubuntu1~22.04 fixed in 12.3.0-1ubuntu1~22.04.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libcc1-0 12.3.0-1ubuntu1~22.04 fixed in 12.3.0-1ubuntu1~22.04.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libgcc-11-dev 11.4.0-1ubuntu1~22.04 fixed in 11.4.0-1ubuntu1~22.04.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libgcc-s1 12.3.0-1ubuntu1~22.04 fixed in 12.3.0-1ubuntu1~22.04.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libgfortran5 12.3.0-1ubuntu1~22.04 fixed in 12.3.0-1ubuntu1~22.04.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-4373 | MEDIUM4.08 | libglib2.0-0 2.72.4-0ubuntu2.2 fixed in 2.72.4-0ubuntu2.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libgomp1 12.3.0-1ubuntu1~22.04 fixed in 12.3.0-1ubuntu1~22.04.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libitm1 12.3.0-1ubuntu1~22.04 fixed in 12.3.0-1ubuntu1~22.04.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | liblsan0 12.3.0-1ubuntu1~22.04 fixed in 12.3.0-1ubuntu1~22.04.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam-modules 1.4.0-11ubuntu2.3 fixed in 1.4.0-11ubuntu2.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam-modules-bin 1.4.0-11ubuntu2.3 fixed in 1.4.0-11ubuntu2.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam-runtime 1.4.0-11ubuntu2.3 fixed in 1.4.0-11ubuntu2.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam0g 1.4.0-11ubuntu2.3 fixed in 1.4.0-11ubuntu2.7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | MEDIUM4.08 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.08 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | MEDIUM4.08 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.08 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libquadmath0 12.3.0-1ubuntu1~22.04 fixed in 12.3.0-1ubuntu1~22.04.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-6004 | MEDIUM4.08 | libssh-4 0.9.6-2ubuntu0.22.04.1 fixed in 0.9.6-2ubuntu0.22.04.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-6004 | MEDIUM4.08 | libssh-gcrypt-4 0.9.6-2ubuntu0.22.04.1 fixed in 0.9.6-2ubuntu0.22.04.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libstdc++-11-dev 11.4.0-1ubuntu1~22.04 fixed in 11.4.0-1ubuntu1~22.04.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libstdc++6 12.3.0-1ubuntu1~22.04 fixed in 12.3.0-1ubuntu1~22.04.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libtsan0 11.4.0-1ubuntu1~22.04 fixed in 11.4.0-1ubuntu1~22.04.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libubsan1 12.3.0-1ubuntu1~22.04 fixed in 12.3.0-1ubuntu1~22.04.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-24859 | MEDIUM4.08 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | MEDIUM4.08 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.08 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | MEDIUM4.08 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.08 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.37.2-4ubuntu3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | MEDIUM4 | libelf1 0.186-1build1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount1 2.37.2-4ubuntu3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols1 2.37.2-4ubuntu3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8114 | MEDIUM4 | libssh-4 0.9.6-2ubuntu0.22.04.1 fixed in 0.9.6-2ubuntu0.22.04.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8114 | MEDIUM4 | libssh-gcrypt-4 0.9.6-2ubuntu0.22.04.1 fixed in 0.9.6-2ubuntu0.22.04.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.19 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.21 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4598 | MEDIUM4 | libsystemd0 249.11-0ubuntu3.10 fixed in 249.11-0ubuntu3.16 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-4598 | MEDIUM4 | libudev1 249.11-0ubuntu3.10 fixed in 249.11-0ubuntu3.16 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.37.2-4ubuntu3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52955 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-6176 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26583 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26585 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26923 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57857 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21947 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-38561 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-168.178 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23004 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23169 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43047 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-1205 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-48816 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49967 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50350 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-46862 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52478 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52489 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52589 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52602 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52608 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52609 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52639 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52645 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53178 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53188 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53204 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53368 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53401 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53447 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53452 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53478 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53501 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53520 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53615 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53766 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53794 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53799 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53816 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53824 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53839 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53861 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54035 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54071 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54149 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54166 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54185 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54201 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54323 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-22386 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-23196 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-24855 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-101.111 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26607 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26631 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26671 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26698 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26837 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-138.148 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26859 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26861 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26862 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26869 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26874 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26878 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26897 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26915 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27009 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27019 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27408 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27415 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27419 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35809 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35848 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36024 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36927 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36949 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36952 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-37354 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38306 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-38580 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38596 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38601 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38613 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38662 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39293 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-39500 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39508 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40905 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40943 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40953 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41005 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41020 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42102 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42107 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42152 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42253 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42287 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43866 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43892 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44954 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45003 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46679 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46787 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-143.153 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46870 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-47660 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47668 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47679 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49859 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49866 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49998 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50006 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50082 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50135 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50192 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53088 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53124 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53136 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53176 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53178 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56568 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56576 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56637 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56788 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57913 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-135.146 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57974 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21651 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21701 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-138.148 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21732 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21825 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22027 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22050 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22060 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23151 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37920 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37985 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38048 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-152.162 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38078 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-152.162 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38083 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-151.161 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38085 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38112 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38232 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38234 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38393 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38440 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38448 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38461 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38462 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38477 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-157.167 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38515 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38524 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38617 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-157.167 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-38681 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38687 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38717 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39673 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39697 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39713 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39726 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39754 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39813 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-163.173 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39825 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39884 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39927 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39961 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39977 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39980 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39992 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39996 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40006 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40011 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40016 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40039 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40085 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40110 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40120 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40134 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40139 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40179 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40187 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40215 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40220 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40244 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40250 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40252 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40254 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40331 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40342 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68214 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68239 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68241 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68264 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68296 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68312 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68745 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71074 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71111 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71274 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23071 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23101 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23110 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23118 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23126 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23167 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23181 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23207 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23212 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23302 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23348 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23452 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23463 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31393 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31466 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31523 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31697 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31728 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31751 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43053 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43163 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43275 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43342 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43383 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43420 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43430 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43439 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43448 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45905 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45949 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46159 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46187 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53108 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53352 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31083 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52749 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26910 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50010 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50183 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21943 | MEDIUM4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-140.150 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-5206 | MEDIUM4 | scikit-learn 1.3.1 fixed in 1.5.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | libc-bin 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.8 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | libc-dev-bin 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.8 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | libc6 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.8 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | libc6-dev 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.8 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3715 | LOW3.98 | bash 5.1-6ubuntu1 fixed in 5.1-6ubuntu1.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-44840 | LOW3.98 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-45703 | LOW3.98 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-47695 | LOW3.98 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.6 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-44840 | LOW3.98 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-45703 | LOW3.98 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-47695 | LOW3.98 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.6 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-44840 | LOW3.98 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-45703 | LOW3.98 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-47695 | LOW3.98 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.6 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-32230 | LOW3.98 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-46951 | LOW3.98 | ghostscript 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-46952 | LOW3.98 | ghostscript 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-46953 | LOW3.98 | ghostscript 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-46956 | LOW3.98 | ghostscript 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-32465 | LOW3.98 | git 1:2.34.1-1ubuntu1.10 fixed in 1:2.34.1-1ubuntu1.11 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW3.98 | ncurses-bin 6.3-2ubuntu0.1 fixed in 6.3-2ubuntu0.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-47038 | LOW3.98 | perl 5.34.0-3ubuntu1.2 fixed in 5.34.0-3ubuntu1.3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2023-47038 | LOW3.98 | perl-base 5.34.0-3ubuntu1.2 fixed in 5.34.0-3ubuntu1.3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-35535 | LOW3.98 | sudo 1.9.9-1ubuntu2.4 fixed in 1.9.9-1ubuntu2.6 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-24106 | LOW3.98 | texlive-binaries 2021.20210626.59705-1ubuntu0.1 fixed in 2021.20210626.59705-1ubuntu0.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-24107 | LOW3.98 | texlive-binaries 2021.20210626.59705-1ubuntu0.1 fixed in 2021.20210626.59705-1ubuntu0.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-4733 | LOW3.98 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.13 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-4734 | LOW3.98 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.13 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4735 | LOW3.98 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.13 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4750 | LOW3.98 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.13 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-4751 | LOW3.98 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.13 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4752 | LOW3.98 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.13 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4781 | LOW3.98 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.13 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-5535 | LOW3.98 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.13 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-28421 | LOW3.98 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-39881 | LOW3.98 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.28 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-52858 | LOW3.98 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.32 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-52860 | LOW3.98 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.32 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55693 | LOW3.98 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-55895 | LOW3.98 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.33 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-57455 | LOW3.98 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57456 | LOW3.98 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-59856 | LOW3.98 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.34 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-59858 | LOW3.98 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.34 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-22667 | LOW3.98 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.16 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4733 | LOW3.98 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.13 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-4734 | LOW3.98 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.13 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4735 | LOW3.98 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.13 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4750 | LOW3.98 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.13 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-4751 | LOW3.98 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.13 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4752 | LOW3.98 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.13 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4781 | LOW3.98 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.13 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-5535 | LOW3.98 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.13 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-28421 | LOW3.98 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-39881 | LOW3.98 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.28 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-52858 | LOW3.98 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.32 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-52860 | LOW3.98 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.32 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55693 | LOW3.98 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-55895 | LOW3.98 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.33 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-57455 | LOW3.98 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57456 | LOW3.98 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-59856 | LOW3.98 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.34 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-59858 | LOW3.98 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.34 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-22667 | LOW3.98 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.16 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4733 | LOW3.98 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.13 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-4734 | LOW3.98 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.13 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4735 | LOW3.98 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.13 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4750 | LOW3.98 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.13 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-4751 | LOW3.98 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.13 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4752 | LOW3.98 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.13 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4781 | LOW3.98 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.13 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-5535 | LOW3.98 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.13 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-28421 | LOW3.98 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-39881 | LOW3.98 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.28 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-52858 | LOW3.98 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.32 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-52860 | LOW3.98 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.32 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55693 | LOW3.98 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-55895 | LOW3.98 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.33 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-57455 | LOW3.98 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57456 | LOW3.98 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-59856 | LOW3.98 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.34 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-59858 | LOW3.98 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.34 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-22667 | LOW3.98 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.16 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-53000 | LOW3.98 | nbconvert 7.9.2 fixed in 7.17.0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-37453 | LOW3.91 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-15213 | LOW3.91 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4010 | LOW3.91 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-49934 | LOW3.91 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-3826 | LOW3.9 | cpp-11 11.4.0-1ubuntu1~22.04 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2023-46218 | LOW3.9 | curl 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.15 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-9681 | LOW3.9 | curl 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.19 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3826 | LOW3.9 | g++-11 11.4.0-1ubuntu1~22.04 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3826 | LOW3.9 | gcc-11 11.4.0-1ubuntu1~22.04 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2023-46218 | LOW3.9 | libcurl3-gnutls 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.15 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-9681 | LOW3.9 | libcurl3-gnutls 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.19 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-46218 | LOW3.9 | libcurl4 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.15 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-9681 | LOW3.9 | libcurl4 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.19 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-6129 | LOW3.9 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.14 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0840 | LOW3.82 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.7 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-0840 | LOW3.82 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.7 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-0840 | LOW3.82 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.7 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | curl 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.25 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | curl 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.24 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | curl 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.24 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-6603 | LOW3.82 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-63757 | LOW3.82 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW3.82 | gzip 1.10-4ubuntu4.1 fixed in 1.10-4ubuntu4.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl3-gnutls 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.25 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl3-gnutls 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.24 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl3-gnutls 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.24 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl4 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.25 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl4 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.24 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl4 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.24 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59999 | LOW3.82 | openssh-client 1:8.9p1-3ubuntu0.4 fixed in 1:8.9p1-3ubuntu0.16 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-60000 | LOW3.82 | openssh-client 1:8.9p1-3ubuntu0.4 fixed in 1:8.9p1-3ubuntu0.16 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69421 | LOW3.82 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.21 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28388 | LOW3.82 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.23 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-28389 | LOW3.82 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.23 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28390 | LOW3.82 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.23 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-26269 | LOW3.82 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.26 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-26269 | LOW3.82 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.26 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-26269 | LOW3.82 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.26 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-24001 | LOW3.82 | diff 5.1.0 fixed in 8.0.3, 5.2.2, 4.0.4, 3.5.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-59873 | LOW3.82 | tar 6.1.15 fixed in 7.5.19 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59874 | LOW3.82 | tar 6.1.15 fixed in 7.5.18 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59871 | LOW3.82 | tar 6.1.15 fixed in 7.5.18 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11468 | LOW3.82 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0865 | LOW3.82 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | LOW3.82 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0865 | LOW3.82 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69277 | LOW3.82 | libsodium23 1.0.18-1build2 fixed in 1.0.18-1ubuntu0.22.04.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4877 | LOW3.82 | libssh-4 0.9.6-2ubuntu0.22.04.1 fixed in 0.9.6-2ubuntu0.22.04.4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4877 | LOW3.82 | libssh-gcrypt-4 0.9.6-2ubuntu0.22.04.1 fixed in 0.9.6-2ubuntu0.22.04.4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-45896 | LOW3.82 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53831 | LOW3.82 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54113 | LOW3.82 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40308 | LOW3.82 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40312 | LOW3.82 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | LOW3.82 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0865 | LOW3.82 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | LOW3.82 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0865 | LOW3.82 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-55798 | LOW3.82 | Pillow 10.1.0 fixed in 12.3.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-29510 | LOW3.79 | ghostscript 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.7 | 28.0% High Exploitation Risk | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | curl 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.25 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl3-gnutls 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.25 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl4 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.25 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW3.77 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.25 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69419 | LOW3.77 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.21 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-64505 | LOW3.74 | libpng16-16 1.6.37-3build5 fixed in 1.6.37-3ubuntu0.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34757 | LOW3.74 | libpng16-16 1.6.37-3build5 fixed in 1.6.37-3ubuntu0.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23458 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-17977 | LOW3.74 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-50720 | LOW3.74 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-3772 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-3773 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-39194 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-52492 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52508 | LOW3.74 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52585 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52617 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52618 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-52627 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52768 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52800 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52838 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52844 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52855 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52858 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52870 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52884 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53718 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53722 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53733 | LOW3.74 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54155 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54247 | LOW3.74 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54253 | LOW3.74 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54263 | LOW3.74 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26648 | LOW3.74 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26661 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26662 | LOW3.74 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26672 | LOW3.74 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26712 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26747 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26757 | LOW3.74 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26758 | LOW3.74 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26769 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26810 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26857 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26875 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36031 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-36894 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36910 | LOW3.74 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36944 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36950 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38540 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38548 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38550 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38559 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38628 | LOW3.74 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42114 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42154 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42230 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-142.152 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46695 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40001 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40021 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40081 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40123 | LOW3.74 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40183 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40198 | LOW3.74 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40200 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40206 | LOW3.74 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40281 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68768 | LOW3.74 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2020-14304 | LOW3.74 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26846 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42131 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53052 | LOW3.74 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-133.144 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-21538 | LOW3.74 | cross-spawn 7.0.3 fixed in 7.0.5, 6.0.6 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-56406 | LOW3.72 | perl 5.34.0-3ubuntu1.2 fixed in 5.34.0-3ubuntu1.4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-56406 | LOW3.72 | perl-base 5.34.0-3ubuntu1.2 fixed in 5.34.0-3ubuntu1.4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-33412 | LOW3.72 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.27 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-41411 | LOW3.72 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.29 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-25749 | LOW3.72 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-33412 | LOW3.72 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.27 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-41411 | LOW3.72 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.29 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-25749 | LOW3.72 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-33412 | LOW3.72 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.27 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-41411 | LOW3.72 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.29 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-25749 | LOW3.72 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-4032 | LOW3.7 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.5 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4032 | LOW3.7 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.5 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-9143 | LOW3.7 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.19 | 6.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4032 | LOW3.7 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.5 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4032 | LOW3.7 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.5 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-31879 | LOW3.66 | wget 1.21.2-2ubuntu1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-25068 | LOW3.65 | libasound2 1.2.6.1-1ubuntu1 fixed in 1.2.6.1-1ubuntu1.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25068 | LOW3.65 | libasound2-data 1.2.6.1-1ubuntu1 fixed in 1.2.6.1-1ubuntu1.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-39327 | LOW3.65 | libopenjp2-7 2.4.0-6 fixed in 2.4.0-6ubuntu0.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-6069 | LOW3.65 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.11 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-8291 | LOW3.65 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.12 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6069 | LOW3.65 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.11 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-8291 | LOW3.65 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.12 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40275 | LOW3.65 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-47233 | LOW3.65 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-107.117 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6069 | LOW3.65 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.11 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-8291 | LOW3.65 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.12 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6069 | LOW3.65 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.11 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-8291 | LOW3.65 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.12 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-49080 | LOW3.65 | jupyter_server 2.8.0 fixed in 2.11.2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-59842 | LOW3.65 | jupyterlab 4.0.7 fixed in 4.4.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59930 | LOW3.65 | mistune 3.0.1 fixed in 3.3.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-32021 | LOW3.62 | git 1:2.34.1-1ubuntu1.10 fixed in 1:2.34.1-1ubuntu1.11 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-35177 | LOW3.62 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-35177 | LOW3.62 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-58471 | LOW3.62 | wget 1.21.2-2ubuntu1 fixed in 1.21.2-2ubuntu1.3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-58472 | LOW3.62 | wget 1.21.2-2ubuntu1 fixed in 1.21.2-2ubuntu1.3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-35177 | LOW3.62 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-26960 | LOW3.62 | tar 6.1.15 fixed in 7.5.8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gpgv 2.2.27-3ubuntu2.1 fixed in 2.2.27-3ubuntu2.5 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46483 | LOW3.57 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.31 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-46483 | LOW3.57 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.31 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-46483 | LOW3.57 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.31 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-8058 | LOW3.57 | libc-bin 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | libc-dev-bin 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | libc6 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | libc6-dev 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1484 | LOW3.57 | libglib2.0-0 2.72.4-0ubuntu2.2 fixed in 2.72.4-0ubuntu2.9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-41848 | LOW3.57 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48522 | LOW3.57 | PyJWT 2.8.0 fixed in 2.13.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | LOW3.54 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-11053 | LOW3.54 | curl 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.20 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2024-11053 | LOW3.54 | libcurl3-gnutls 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.20 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2024-11053 | LOW3.54 | libcurl4 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.20 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2023-6237 | LOW3.54 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.14 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-5535 | LOW3.54 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.17 | 5.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-15146 | LOW3.54 | wget 1.21.2-2ubuntu1 fixed in 1.21.2-2ubuntu1.4 | — | Post-Exploit |
| CVE-2022-48646 | LOW3.48 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52872 | LOW3.48 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-100.110 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36928 | LOW3.48 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-118.128 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42156 | LOW3.48 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42157 | LOW3.48 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42158 | LOW3.48 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42229 | LOW3.48 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40173 | LOW3.48 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1965 | LOW3.47 | curl 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.23 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-33870 | LOW3.47 | ghostscript 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl3-gnutls 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.23 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl4 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.23 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-5742 | LOW3.42 | nano-tiny 6.2-1 fixed in 6.2-1ubuntu0.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-33602 | LOW3.4 | libc-bin 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | libc-dev-bin 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | libc6 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | libc6-dev 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-9820 | LOW3.4 | libgnutls30 3.7.3-4ubuntu1.2 fixed in 3.7.3-4ubuntu1.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW3.4 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.21 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52597 | LOW3.4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53708 | LOW3.4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54229 | LOW3.4 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3449 | LOW3.4 | @tootallnate/once 2.0.0 fixed in 3.0.1, 2.0.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28419 | LOW3.37 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-28419 | LOW3.37 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-28419 | LOW3.37 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-9230 | LOW3.36 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.20 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4741 | LOW3.36 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.17 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2024-8096 | LOW3.31 | curl 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.18 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | curl 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.24 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | curl 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.24 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | curl 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.22 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | curl 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.23 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.25 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-59728 | LOW3.31 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-59732 | LOW3.31 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-59733 | LOW3.31 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-8096 | LOW3.31 | libcurl3-gnutls 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.18 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl3-gnutls 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.24 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl3-gnutls 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.24 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl3-gnutls 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.22 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl3-gnutls 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.23 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl3-gnutls 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.25 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-8096 | LOW3.31 | libcurl4 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.18 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl4 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.24 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl4 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.24 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl4 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.22 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl4 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.23 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl4 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.25 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-50495 | LOW3.31 | ncurses-bin 6.3-2ubuntu0.1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-35387 | LOW3.31 | openssh-client 1:8.9p1-3ubuntu0.4 fixed in 1:8.9p1-3ubuntu0.15 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59998 | LOW3.31 | openssh-client 1:8.9p1-3ubuntu0.4 fixed in 1:8.9p1-3ubuntu0.16 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-60001 | LOW3.31 | openssh-client 1:8.9p1-3ubuntu0.4 fixed in 1:8.9p1-3ubuntu0.16 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58469 | LOW3.31 | wget 1.21.2-2ubuntu1 fixed in 1.21.2-2ubuntu1.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-28863 | LOW3.31 | tar 6.1.15 fixed in 6.2.1 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-39377 | LOW3.31 | nbconvert 7.9.2 fixed in 7.17.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-36613 | LOW3.31 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36613 | LOW3.31 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36613 | LOW3.31 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36613 | LOW3.31 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36613 | LOW3.31 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36613 | LOW3.31 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36613 | LOW3.31 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36613 | LOW3.31 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | LOW3.3 | binutils 2.38-4ubuntu2.3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010204 | LOW3.3 | binutils 2.38-4ubuntu2.3 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-common 2.38-4ubuntu2.3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010204 | LOW3.3 | binutils-common 2.38-4ubuntu2.3 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010204 | LOW3.3 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-0727 | LOW3.3 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.14 | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1771 | LOW3.3 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1771 | LOW3.3 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1771 | LOW3.3 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-34397 | LOW3.23 | libglib2.0-0 2.72.4-0ubuntu2.2 fixed in 2.72.4-0ubuntu2.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-48386 | LOW3.21 | git 1:2.34.1-1ubuntu1.10 fixed in 1:2.34.1-1ubuntu1.13 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5958 | LOW3.21 | sed 4.8-1ubuntu2 fixed in 4.8-1ubuntu2.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-29786 | LOW3.21 | tar 6.1.15 fixed in 7.5.10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-3446 | LOW3.18 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.12 | 5.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-3817 | LOW3.18 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.12 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5678 | LOW3.18 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.14 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4603 | LOW3.18 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.17 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1152 | LOW3.15 | libbinutils 2.38-4ubuntu2.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf-nobfd0 2.38-4ubuntu2.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf0 2.38-4ubuntu2.3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-0988 | LOW3.15 | libglib2.0-0 2.72.4-0ubuntu2.2 fixed in 2.72.4-0ubuntu2.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-3360 | LOW3.15 | libglib2.0-0 2.72.4-0ubuntu2.2 fixed in 2.72.4-0ubuntu2.7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-7039 | LOW3.15 | libglib2.0-0 2.72.4-0ubuntu2.2 fixed in 2.72.4-0ubuntu2.7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3832 | LOW3.15 | libgnutls30 3.7.3-4ubuntu1.2 fixed in 3.7.3-4ubuntu1.9 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-7883 | LOW3.15 | libllvm15 1:15.0.7-0ubuntu0.22.04.3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-11168 | LOW3.15 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-11168 | LOW3.15 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | libssl3 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.25 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0989 | LOW3.15 | libxml2 2.9.13+dfsg-1ubuntu0.3 fixed in 2.9.13+dfsg-1ubuntu0.11 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-32251 | LOW3.15 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-53791 | LOW3.15 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-11168 | LOW3.15 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-11168 | LOW3.15 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-55655 | LOW3.11 | openssh-client 1:8.9p1-3ubuntu0.4 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23745 | LOW3.11 | tar 6.1.15 fixed in 7.5.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59890 | LOW3.11 | setuptools 68.2.2 fixed in 83.0.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-4878 | LOW3.06 | libssh-4 0.9.6-2ubuntu0.22.04.1 fixed in 0.9.6-2ubuntu0.22.04.4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4878 | LOW3.06 | libssh-gcrypt-4 0.9.6-2ubuntu0.22.04.1 fixed in 0.9.6-2ubuntu0.22.04.4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31790 | LOW3.01 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.23 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2025-69420 | LOW3.01 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.21 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-22796 | LOW3.01 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.21 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW3.01 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.25 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.01 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.25 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-40909 | LOW3.01 | perl 5.34.0-3ubuntu1.2 fixed in 5.34.0-3ubuntu1.5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-40909 | LOW3.01 | perl-base 5.34.0-3ubuntu1.2 fixed in 5.34.0-3ubuntu1.5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-23950 | LOW3.01 | tar 6.1.15 fixed in 7.5.4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6357 | LOW2.96 | pip 23.3 fixed in 26.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | curl 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.23 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl3-gnutls 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.23 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl4 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.23 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-39378 | LOW2.91 | nbconvert 7.9.2 fixed in 7.17.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-2511 | LOW2.89 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.17 | 54.0% Actively Exploited | Post-Exploit |
| CVE-2025-68740 | LOW2.89 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2020-35501 | LOW2.89 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | LOW2.86 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-45582 | LOW2.86 | tar 1.34+dfsg-1ubuntu0.1.22.04.1 fixed in 1.34+dfsg-1ubuntu0.1.22.04.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-35205 | LOW2.8 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47007 | LOW2.8 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47008 | LOW2.8 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47010 | LOW2.8 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47011 | LOW2.8 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-48063 | LOW2.8 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.6 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-48065 | LOW2.8 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.6 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.12 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.12 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.12 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.12 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils 2.38-4ubuntu2.3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | binutils 2.38-4ubuntu2.3 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-4285 | LOW2.8 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-48064 | LOW2.8 | binutils 2.38-4ubuntu2.3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-35205 | LOW2.8 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47007 | LOW2.8 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47008 | LOW2.8 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47010 | LOW2.8 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47011 | LOW2.8 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-48063 | LOW2.8 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.6 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-48065 | LOW2.8 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.6 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.12 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.12 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.12 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.12 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-common 2.38-4ubuntu2.3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | binutils-common 2.38-4ubuntu2.3 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-4285 | LOW2.8 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-48064 | LOW2.8 | binutils-common 2.38-4ubuntu2.3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-35205 | LOW2.8 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47007 | LOW2.8 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47008 | LOW2.8 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47010 | LOW2.8 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47011 | LOW2.8 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-48063 | LOW2.8 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.6 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-48065 | LOW2.8 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.6 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.12 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.12 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.12 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.12 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-4285 | LOW2.8 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-48064 | LOW2.8 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2021-46195 | LOW2.8 | cpp-11 11.4.0-1ubuntu1~22.04 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | cpp-11 11.4.0-1ubuntu1~22.04 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-10256 | LOW2.8 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-46195 | LOW2.8 | g++-11 11.4.0-1ubuntu1~22.04 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | g++-11 11.4.0-1ubuntu1~22.04 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2021-46195 | LOW2.8 | gcc-11 11.4.0-1ubuntu1~22.04 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | gcc-11 11.4.0-1ubuntu1~22.04 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2024-46955 | LOW2.8 | ghostscript 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-27830 | LOW2.8 | ghostscript 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-27831 | LOW2.8 | ghostscript 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.11 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-27832 | LOW2.8 | ghostscript 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.11 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-27834 | LOW2.8 | ghostscript 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-27835 | LOW2.8 | ghostscript 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-27836 | LOW2.8 | ghostscript 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.11 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-59798 | LOW2.8 | ghostscript 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.13 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-59799 | LOW2.8 | ghostscript 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.13 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-59800 | LOW2.8 | ghostscript 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.13 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-4641 | LOW2.8 | login 1:4.8.1-2ubuntu2.1 fixed in 1:4.8.1-2ubuntu2.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6843 | LOW2.8 | nano-tiny 6.2-1 fixed in 6.2-1ubuntu0.2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-51384 | LOW2.8 | openssh-client 1:8.9p1-3ubuntu0.4 fixed in 1:8.9p1-3ubuntu0.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-22795 | LOW2.8 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.21 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW2.8 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.25 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-4641 | LOW2.8 | passwd 1:4.8.1-2ubuntu2.1 fixed in 1:4.8.1-2ubuntu2.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2019-20633 | LOW2.8 | patch 2.7.6-7build2 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2021-45261 | LOW2.8 | patch 2.7.6-7build2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.34+dfsg-1ubuntu0.1.22.04.1 fixed in 1.34+dfsg-1ubuntu0.1.22.04.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-32668 | LOW2.8 | texlive-binaries 2021.20210626.59705-1ubuntu0.1 fixed in 2021.20210626.59705-1ubuntu0.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-46246 | LOW2.8 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-5441 | LOW2.8 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.13 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-22134 | LOW2.8 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.22 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-24014 | LOW2.8 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.23 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-28418 | LOW2.8 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45130 | LOW2.8 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.30 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55892 | LOW2.8 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-59857 | LOW2.8 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.34 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-1725 | LOW2.8 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-46246 | LOW2.8 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-5441 | LOW2.8 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.13 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-22134 | LOW2.8 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.22 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-24014 | LOW2.8 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.23 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-28418 | LOW2.8 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45130 | LOW2.8 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.30 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55892 | LOW2.8 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-59857 | LOW2.8 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.34 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-1725 | LOW2.8 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-46246 | LOW2.8 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-5441 | LOW2.8 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.13 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-22134 | LOW2.8 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.22 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-24014 | LOW2.8 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.23 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-28418 | LOW2.8 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45130 | LOW2.8 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.30 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55892 | LOW2.8 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-59857 | LOW2.8 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.34 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-1725 | LOW2.8 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-31802 | LOW2.8 | tar 6.1.15 fixed in 7.5.11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53655 | LOW2.8 | tar 6.1.15 fixed in 7.5.16 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-8643 | LOW2.8 | pip 23.3 fixed in 26.1.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-24049 | LOW2.8 | wheel 0.41.2 fixed in 0.46.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW2.8 | libbinutils 2.38-4ubuntu2.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf-nobfd0 2.38-4ubuntu2.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf0 2.38-4ubuntu2.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6199 | LOW2.8 | libgdk-pixbuf-2.0-0 2.42.8+dfsg-1ubuntu0.2 fixed in 2.42.8+dfsg-1ubuntu0.4 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6199 | LOW2.8 | libgdk-pixbuf2.0-common 2.42.8+dfsg-1ubuntu0.2 fixed in 2.42.8+dfsg-1ubuntu0.4 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-29508 | LOW2.8 | libgs9 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-48708 | LOW2.8 | libgs9 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.12 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-29508 | LOW2.8 | libgs9-common 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-48708 | LOW2.8 | libgs9-common 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.12 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6192 | LOW2.8 | libopenjp2-7 2.4.0-6 fixed in 2.4.0-6ubuntu0.5 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-4016 | LOW2.8 | libprocps8 2:3.3.17-6ubuntu2 fixed in 2:3.3.17-6ubuntu2.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.8 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.8 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0965 | LOW2.8 | libssh-4 0.9.6-2ubuntu0.22.04.1 fixed in 0.9.6-2ubuntu0.22.04.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0965 | LOW2.8 | libssh-gcrypt-4 0.9.6-2ubuntu0.22.04.1 fixed in 0.9.6-2ubuntu0.22.04.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 249.11-0ubuntu3.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8961 | LOW2.8 | libtiff5 4.3.0-6ubuntu0.6 fixed in 4.3.0-6ubuntu0.12 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9165 | LOW2.8 | libtiff5 4.3.0-6ubuntu0.6 fixed in 4.3.0-6ubuntu0.12 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 249.11-0ubuntu3.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8732 | LOW2.8 | libxml2 2.9.13+dfsg-1ubuntu0.3 fixed in 2.9.13+dfsg-1ubuntu0.11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52926 | LOW2.8 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48667 | LOW2.8 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48668 | LOW2.8 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50628 | LOW2.8 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50778 | LOW2.8 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50811 | LOW2.8 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52561 | LOW2.8 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53992 | LOW2.8 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54127 | LOW2.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54145 | LOW2.8 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54172 | LOW2.8 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54177 | LOW2.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54194 | LOW2.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54211 | LOW2.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54220 | LOW2.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54227 | LOW2.8 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54230 | LOW2.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54233 | LOW2.8 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54261 | LOW2.8 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54282 | LOW2.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54320 | LOW2.8 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54322 | LOW2.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26614 | LOW2.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-106.116 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26764 | LOW2.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35935 | LOW2.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-116.126 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41007 | LOW2.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41027 | LOW2.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-121.131 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-43841 | LOW2.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-125.135 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47738 | LOW2.8 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50044 | LOW2.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-127.137 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50057 | LOW2.8 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50211 | LOW2.8 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50280 | LOW2.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57898 | LOW2.8 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39964 | LOW2.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-164.174 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40035 | LOW2.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40268 | LOW2.8 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40303 | LOW2.8 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40341 | LOW2.8 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68191 | LOW2.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68746 | LOW2.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68782 | LOW2.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71224 | LOW2.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22978 | LOW2.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31668 | LOW2.8 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.8 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.8 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4539 | LOW2.8 | Pygments 2.16.1 fixed in 2.20.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59995 | LOW2.75 | openssh-client 1:8.9p1-3ubuntu0.4 fixed in 1:8.9p1-3ubuntu0.16 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59996 | LOW2.75 | openssh-client 1:8.9p1-3ubuntu0.4 fixed in 1:8.9p1-3ubuntu0.16 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59997 | LOW2.75 | openssh-client 1:8.9p1-3ubuntu0.4 fixed in 1:8.9p1-3ubuntu0.16 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | curl 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.24 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | curl 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.24 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | curl 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.24 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3341 | LOW2.7 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-0518 | LOW2.7 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-52722 | LOW2.7 | ghostscript 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.7 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-33869 | LOW2.7 | ghostscript 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl3-gnutls 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.24 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl3-gnutls 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.24 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl3-gnutls 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.24 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl4 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.24 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl4 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.24 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl4 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.24 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-61984 | LOW2.7 | openssh-client 1:8.9p1-3ubuntu0.4 fixed in 1:8.9p1-3ubuntu0.14 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-61985 | LOW2.7 | openssh-client 1:8.9p1-3ubuntu0.4 fixed in 1:8.9p1-3ubuntu0.14 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-2975 | LOW2.7 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.12 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42766 | LOW2.7 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.25 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42767 | LOW2.7 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.25 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41957 | LOW2.7 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.18 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-44656 | LOW2.7 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.30 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-47167 | LOW2.7 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.32 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41957 | LOW2.7 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.18 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-44656 | LOW2.7 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.30 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-47167 | LOW2.7 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.32 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-58470 | LOW2.7 | wget 1.21.2-2ubuntu1 fixed in 1.21.2-2ubuntu1.3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41957 | LOW2.7 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.18 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-44656 | LOW2.7 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.30 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-47167 | LOW2.7 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.32 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-34743 | LOW2.7 | xz-utils 5.2.5-2ubuntu1 fixed in 5.2.5-2ubuntu1.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-59875 | LOW2.7 | tar 6.1.15 fixed in 7.5.17 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-8869 | LOW2.7 | pip 23.3 fixed in 25.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-28085 | LOW2.64 | bsdutils 1:2.37.2-4ubuntu3 fixed in 2.37.2-4ubuntu3.4 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-29511 | LOW2.64 | ghostscript 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.9 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28085 | LOW2.64 | mount 2.37.2-4ubuntu3 fixed in 2.37.2-4ubuntu3.4 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28085 | LOW2.64 | util-linux 2.37.2-4ubuntu3 fixed in 2.37.2-4ubuntu3.4 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1148 | LOW2.63 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libbinutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf-nobfd0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf0 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1795 | LOW2.63 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1795 | LOW2.63 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-0968 | LOW2.63 | libssh-4 0.9.6-2ubuntu0.22.04.1 fixed in 0.9.6-2ubuntu0.22.04.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-8277 | LOW2.63 | libssh-4 0.9.6-2ubuntu0.22.04.1 fixed in 0.9.6-2ubuntu0.22.04.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0968 | LOW2.63 | libssh-gcrypt-4 0.9.6-2ubuntu0.22.04.1 fixed in 0.9.6-2ubuntu0.22.04.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-8277 | LOW2.63 | libssh-gcrypt-4 0.9.6-2ubuntu0.22.04.1 fixed in 0.9.6-2ubuntu0.22.04.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1795 | LOW2.63 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1795 | LOW2.63 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-5889 | LOW2.63 | brace-expansion 1.1.11 fixed in 2.0.2, 1.1.12, 3.0.1, 4.0.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-5889 | LOW2.63 | brace-expansion 2.0.1 fixed in 2.0.2, 1.1.12, 3.0.1, 4.0.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | LOW2.55 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-34180 | LOW2.55 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.25 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3219 | LOW2.55 | pip 23.3 fixed in 26.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0992 | LOW2.46 | libxml2 2.9.13+dfsg-1ubuntu0.3 fixed in 2.9.13+dfsg-1ubuntu0.11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | LOW2.45 | cpp-11 11.4.0-1ubuntu1~22.04 fixed in 11.4.0-1ubuntu1~22.04.2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | curl 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.22 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-4039 | LOW2.45 | g++-11 11.4.0-1ubuntu1~22.04 fixed in 11.4.0-1ubuntu1~22.04.2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-4039 | LOW2.45 | gcc-11 11.4.0-1ubuntu1~22.04 fixed in 11.4.0-1ubuntu1~22.04.2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl3-gnutls 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.22 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl4 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.22 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.37.2-4ubuntu3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.22 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-50349 | LOW2.4 | git 1:2.34.1-1ubuntu1.10 fixed in 1:2.34.1-1ubuntu1.12 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgv 2.2.27-3ubuntu2.1 fixed in 2.2.27-3ubuntu2.3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.10-4ubuntu4.1 fixed in 1.10-4ubuntu4.2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl3-gnutls 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.22 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl4 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.22 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.37.2-4ubuntu3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-13176 | LOW2.4 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.19 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-68160 | LOW2.4 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.21 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.37.2-4ubuntu3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-48706 | LOW2.4 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-43374 | LOW2.4 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.18 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-57452 | LOW2.4 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47814 | LOW2.4 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.21 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-48706 | LOW2.4 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-43374 | LOW2.4 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.18 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-57452 | LOW2.4 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47814 | LOW2.4 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.21 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-48706 | LOW2.4 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-43374 | LOW2.4 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.18 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-57452 | LOW2.4 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.33 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47814 | LOW2.4 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.21 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW2.38 | libbinutils 2.38-4ubuntu2.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf-nobfd0 2.38-4ubuntu2.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf0 2.38-4ubuntu2.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1485 | LOW2.38 | libglib2.0-0 2.72.4-0ubuntu2.2 fixed in 2.72.4-0ubuntu2.9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-43802 | LOW2.29 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.19 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-43802 | LOW2.29 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.19 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-43802 | LOW2.29 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.19 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-28420 | LOW2.24 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42307 | LOW2.24 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.30 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28420 | LOW2.24 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42307 | LOW2.24 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.30 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28420 | LOW2.24 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.26 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42307 | LOW2.24 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.30 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2024-9143 | LOW2.22 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.19 | 6.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-27613 | LOW2.19 | git 1:2.34.1-1ubuntu1.10 fixed in 1:2.34.1-1ubuntu1.15 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-48231 | LOW2.19 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48233 | LOW2.19 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48234 | LOW2.19 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48235 | LOW2.19 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48236 | LOW2.19 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48237 | LOW2.19 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48231 | LOW2.19 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48233 | LOW2.19 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48234 | LOW2.19 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48235 | LOW2.19 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48236 | LOW2.19 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48237 | LOW2.19 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48231 | LOW2.19 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48233 | LOW2.19 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48234 | LOW2.19 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48235 | LOW2.19 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48236 | LOW2.19 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-48237 | LOW2.19 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.15 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-26603 | LOW2.14 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.24 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-26603 | LOW2.14 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.24 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-26603 | LOW2.14 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.24 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-24515 | LOW2.12 | libexpat1 2.4.7-1ubuntu0.2 fixed in 2.4.7-1ubuntu0.7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-57053 | LOW2.12 | libidn12 1.38-4ubuntu1 fixed in 1.38-4ubuntu1.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8534 | LOW2.12 | libtiff5 4.3.0-6ubuntu0.6 fixed in 4.3.0-6ubuntu0.11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6170 | LOW2.12 | libxml2 2.9.13+dfsg-1ubuntu0.3 fixed in 2.9.13+dfsg-1ubuntu0.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52620 | LOW2.12 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54246 | LOW2.12 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54267 | LOW2.12 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54283 | LOW2.12 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-112.122 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54316 | LOW2.12 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68788 | LOW2.12 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW2.04 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.21 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36613 | LOW1.99 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1703 | LOW1.99 | pip 23.3 fixed in 26.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-50583 | LOW1.95 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-32728 | LOW1.94 | openssh-client 1:8.9p1-3ubuntu0.4 fixed in 1:8.9p1-3ubuntu0.13 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils 2.38-4ubuntu2.3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-common 2.38-4ubuntu2.3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-55654 | LOW1.89 | openssh-client 1:8.9p1-3ubuntu0.4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-45446 | LOW1.89 | openssl 3.0.2-0ubuntu1.10 fixed in 3.0.2-0ubuntu1.25 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | login 1:4.8.1-2ubuntu2.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.8.1-2ubuntu2.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.38-4ubuntu2.3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-common 2.38-4ubuntu2.3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-29508 | LOW1.68 | ghostscript 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.9 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-48708 | LOW1.68 | ghostscript 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.12 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-32020 | LOW1.68 | git 1:2.34.1-1ubuntu1.10 fixed in 1:2.34.1-1ubuntu1.11 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-29383 | LOW1.68 | login 1:4.8.1-2ubuntu2.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-29383 | LOW1.68 | passwd 1:4.8.1-2ubuntu2.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-4016 | LOW1.68 | procps 2:3.3.17-6ubuntu2 fixed in 2:3.3.17-6ubuntu2.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-39804 | LOW1.68 | tar 1.34+dfsg-1ubuntu0.1.22.04.1 fixed in 1.34+dfsg-1ubuntu0.1.22.04.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-42155 | LOW1.61 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW1.58 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-common 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.10 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 fixed in 2.38-4ubuntu2.8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-46835 | LOW1.58 | git 1:2.34.1-1ubuntu1.10 fixed in 1:2.34.1-1ubuntu1.15 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils 2.38-4ubuntu2.3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-common 2.38-4ubuntu2.3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-x86-64-linux-gnu 2.38-4ubuntu2.3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6842 | LOW1.27 | nano-tiny 6.2-1 fixed in 6.2-1ubuntu0.2 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-35388 | LOW1.27 | openssh-client 1:8.9p1-3ubuntu0.4 fixed in 1:8.9p1-3ubuntu0.15 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-28422 | LOW1.12 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.26 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-28422 | LOW1.12 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.26 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-28422 | LOW1.12 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.26 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-32002 | NONE0 | git-man 1:2.34.1-1ubuntu1.10 fixed in 1:2.34.1-1ubuntu1.11 | 25.3% High Exploitation Risk | Not Applicable |
| CVE-2024-52005 | NONE0 | git-man 1:2.34.1-1ubuntu1.10 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-2961 | NONE0 | locales 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.7 | 88.3% Actively Exploited | Not Applicable |
| CVE-2026-0861 | NONE0 | locales 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.13 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-48384 | NONE0 | git-man 1:2.34.1-1ubuntu1.10 fixed in 1:2.34.1-1ubuntu1.13 | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2024-32004 | NONE0 | git-man 1:2.34.1-1ubuntu1.10 fixed in 1:2.34.1-1ubuntu1.11 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-32465 | NONE0 | git-man 1:2.34.1-1ubuntu1.10 fixed in 1:2.34.1-1ubuntu1.11 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-33599 | NONE0 | locales 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.8 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-52006 | NONE0 | git-man 1:2.34.1-1ubuntu1.10 fixed in 1:2.34.1-1ubuntu1.12 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-5156 | NONE0 | locales 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.5 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-4055 | NONE0 | xdg-utils 1.1.3-4.1ubuntu3~22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-32021 | NONE0 | git-man 1:2.34.1-1ubuntu1.10 fixed in 1:2.34.1-1ubuntu1.11 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2025-4802 | NONE0 | locales 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.10 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | locales 2.35-0ubuntu3.4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-48386 | NONE0 | git-man 1:2.34.1-1ubuntu1.10 fixed in 1:2.34.1-1ubuntu1.13 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-15281 | NONE0 | locales 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.13 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | locales 2.35-0ubuntu3.4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-4806 | NONE0 | locales 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.5 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-4813 | NONE0 | locales 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.5 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2025-0395 | NONE0 | locales 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.9 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-33600 | NONE0 | locales 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.8 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-0915 | NONE0 | locales 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.13 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4046 | NONE0 | locales 2.35-0ubuntu3.4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-50349 | NONE0 | git-man 1:2.34.1-1ubuntu1.10 fixed in 1:2.34.1-1ubuntu1.12 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-27613 | NONE0 | git-man 1:2.34.1-1ubuntu1.10 fixed in 1:2.34.1-1ubuntu1.15 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-8058 | NONE0 | locales 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-33601 | NONE0 | locales 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.8 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-33602 | NONE0 | locales 2.35-0ubuntu3.4 fixed in 2.35-0ubuntu3.8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-32020 | NONE0 | git-man 1:2.34.1-1ubuntu1.10 fixed in 1:2.34.1-1ubuntu1.11 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-46835 | NONE0 | git-man 1:2.34.1-1ubuntu1.10 fixed in 1:2.34.1-1ubuntu1.15 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-52968 | NONE0 | xdg-utils 1.1.3-4.1ubuntu3~22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-0167 | NONE0 | curl 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.23 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-8458 | NONE0 | curl 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.25 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-6297 | NONE0 | dpkg 1.21.1ubuntu2.2 fixed in 1.21.1ubuntu2.6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-6297 | NONE0 | dpkg-dev 1.21.1ubuntu2.2 fixed in 1.21.1ubuntu2.6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-49502 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-50010 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-51793 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-51794 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-51798 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6601 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6602 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6604 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6605 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-31578 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-35366 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-35367 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-35368 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-36616 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-36617 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36618 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22919 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-25467 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-25473 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-59731 | NONE0 | ffmpeg 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-7462 | NONE0 | ghostscript 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.13 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56109 | NONE0 | libasound2 1.2.6.1-1ubuntu1 fixed in 1.2.6.1-1ubuntu1.2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56109 | NONE0 | libasound2-data 1.2.6.1-1ubuntu1 fixed in 1.2.6.1-1ubuntu1.2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-49502 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-50010 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-51793 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-51794 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-51798 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6601 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6602 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6604 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6605 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-31578 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-35366 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-35367 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-35368 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-36616 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-36617 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36618 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22919 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-25467 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-25473 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-59731 | NONE0 | libavcodec58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-49502 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-50010 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-51793 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-51794 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-51798 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6601 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6602 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6604 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6605 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-31578 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-35366 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-35367 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-35368 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-36616 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-36617 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36618 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22919 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-25467 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-25473 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-59731 | NONE0 | libavdevice58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-49502 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-50010 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-51793 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-51794 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-51798 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6601 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6602 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6604 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6605 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-31578 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-35366 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-35367 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-35368 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-36616 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-36617 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36618 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22919 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-25467 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-25473 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-59731 | NONE0 | libavfilter7 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-49502 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-50010 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-51793 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-51794 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-51798 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6601 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6602 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6604 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6605 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-31578 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-35366 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-35367 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-35368 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-36616 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-36617 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36618 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22919 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-25467 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-25473 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-59731 | NONE0 | libavformat58 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-49502 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-50010 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-51793 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-51794 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-51798 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6601 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6602 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6604 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6605 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-31578 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-35366 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-35367 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-35368 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-36616 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-36617 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36618 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22919 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-25467 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-25473 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-59731 | NONE0 | libavutil56 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42046 | NONE0 | libcaca0 0.99.beta19-2.2ubuntu4 fixed in 0.99.beta19-2.2ubuntu4.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-0167 | NONE0 | libcurl3-gnutls 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.23 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl3-gnutls 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.25 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-0167 | NONE0 | libcurl4 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.23 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl4 7.81.0-1ubuntu1.14 fixed in 7.81.0-1ubuntu1.25 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-6297 | NONE0 | libdpkg-perl 1.21.1ubuntu2.2 fixed in 1.21.1ubuntu2.6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-50593 | NONE0 | libgraphite2-3 1.3.14-1build2 fixed in 1.3.14-1ubuntu0.1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-7462 | NONE0 | libgs9 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.13 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-7462 | NONE0 | libgs9-common 9.55.0~dfsg1-0ubuntu5.5 fixed in 9.55.0~dfsg1-0ubuntu5.13 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-25262 | NONE0 | libkpathsea6 2021.20210626.59705-1ubuntu0.1 fixed in 2021.20210626.59705-1ubuntu0.2 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-22656 | NONE0 | libmfx1 22.3.0-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-47282 | NONE0 | libmfx1 22.3.0-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40930 | NONE0 | libpng16-16 1.6.37-3build5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-49502 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-50010 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-51793 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-51794 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-51798 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6601 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6602 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6604 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6605 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-31578 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-35366 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-35367 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-35368 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-36616 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-36617 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36618 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22919 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-25467 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-25473 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-59731 | NONE0 | libpostproc55 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-25262 | NONE0 | libptexenc1 2021.20210626.59705-1ubuntu0.1 fixed in 2021.20210626.59705-1ubuntu0.2 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.10-stdlib 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-44235 | NONE0 | librabbitmq4 0.10.0-1ubuntu2 fixed in 0.10.0-1ubuntu2.1 | — | Not Applicable |
| CVE-2026-44236 | NONE0 | librabbitmq4 0.10.0-1ubuntu2 fixed in 0.10.0-1ubuntu2.1 | — | Not Applicable |
| CVE-2026-11822 | NONE0 | libsqlite3-0 3.37.2-2ubuntu0.1 fixed in 3.37.2-2ubuntu0.6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-0 3.37.2-2ubuntu0.1 fixed in 3.37.2-2ubuntu0.6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50812 | NONE0 | libsqlite3-0 3.37.2-2ubuntu0.1 fixed in 3.37.2-2ubuntu0.7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50813 | NONE0 | libsqlite3-0 3.37.2-2ubuntu0.1 fixed in 3.37.2-2ubuntu0.7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-49502 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-50010 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-51793 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-51794 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-51798 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6601 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6602 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6604 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6605 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-31578 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-35366 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-35367 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-35368 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-36616 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-36617 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36618 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22919 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-25467 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-25473 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-59731 | NONE0 | libswresample3 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-49502 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-50010 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-51793 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-51794 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-51798 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6601 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6602 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6604 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6605 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-31578 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-35366 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-35367 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-35368 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-36616 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-36617 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36618 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22919 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-25467 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-25473 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-59731 | NONE0 | libswscale5 7:4.4.2-0ubuntu0.22.04.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-25262 | NONE0 | libsynctex2 2021.20210626.59705-1ubuntu0.1 fixed in 2021.20210626.59705-1ubuntu0.2 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-25262 | NONE0 | libtexlua53 2021.20210626.59705-1ubuntu0.1 fixed in 2021.20210626.59705-1ubuntu0.2 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-25262 | NONE0 | libtexluajit2 2021.20210626.59705-1ubuntu0.1 fixed in 2021.20210626.59705-1ubuntu0.2 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-25467 | NONE0 | libx264-163 2:0.163.3060+git5db6aa6-2build1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-68263 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43011 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53215 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23268 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23372 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23393 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31405 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31432 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31433 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31476 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31478 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31627 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31656 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31657 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31659 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31695 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31705 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31706 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31712 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31716 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31780 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43075 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43076 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43206 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43236 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43370 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43490 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52911 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52914 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53040 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53043 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53046 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53068 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53130 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53186 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53198 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-50634 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50708 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50759 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50785 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53693 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53707 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53714 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53727 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53742 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53748 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53782 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53817 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-53834 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53855 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53865 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54005 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54017 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54047 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54049 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54059 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54104 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54105 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54112 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54115 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54125 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54140 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-91.101 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54151 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54162 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54178 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54180 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54183 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54187 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54203 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54219 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54240 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54250 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-102.112 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54266 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54297 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-88.98 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54304 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-94.104 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36331 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-27558 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37838 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-144.157 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39985 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39986 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39987 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39988 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39995 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40003 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40012 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40032 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40036 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40043 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40055 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40060 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40068 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40073 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40077 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40084 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40087 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40093 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40095 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40097 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40106 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40107 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40112 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40116 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40124 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40126 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40127 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40137 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40180 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40188 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40192 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40193 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40208 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40223 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40233 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40243 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40245 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40262 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40263 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40266 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40278 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40282 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40285 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40286 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40288 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40289 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40306 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40310 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40311 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40313 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40314 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40315 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40317 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40332 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40333 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40335 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40337 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40354 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40356 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40358 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-54505 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-62626 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68174 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68175 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68177 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68184 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68190 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68196 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68201 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68217 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68220 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68230 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68238 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68246 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68249 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-170.180 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68254 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68255 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68256 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68257 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68258 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68266 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68286 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68289 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68290 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68302 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68303 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68311 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68315 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68318 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68322 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68325 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68327 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68328 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68330 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68332 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68335 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68339 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68344 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68364 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68727 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68728 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68733 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68750 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-156.166 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68759 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68765 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68767 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68769 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68771 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68772 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68777 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68781 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68786 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68787 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68796 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68797 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68799 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68804 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68806 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68808 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68809 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71067 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71069 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71192 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71195 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71196 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71197 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71198 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71199 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23033 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23037 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23049 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23056 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-176.186 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23176 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23182 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23245 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23269 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23364 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23406 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23407 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-173.183 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31409 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31417 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31477 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31494 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31597 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31598 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31602 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31611 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31612 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31622 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31626 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31629 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31683 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31707 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31711 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31768 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43117 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-185.195 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43184 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43203 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43245 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43336 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43373 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43377 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43476 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45935 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45958 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46006 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46062 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46112 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46124 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46177 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46197 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46198 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46199 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46205 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46206 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46208 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46212 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46218 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46230 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46238 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46328 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52919 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52922 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52931 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52934 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53041 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53045 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53329 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53356 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53368 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-53374 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-53375 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-53376 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-53377 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-53382 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-53383 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-53386 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-53387 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-53390 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-53401 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63793 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63796 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63798 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63805 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63806 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63814 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63815 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63817 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63818 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63819 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63825 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63827 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63828 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63833 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63834 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63835 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63836 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63846 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63847 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63848 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63854 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63855 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63856 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63862 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63879 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63881 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63882 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63895 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63905 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63908 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63915 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63930 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63931 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63933 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63934 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63954 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63959 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63960 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-63967 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-64010 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-64033 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64055 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64056 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64083 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64084 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64085 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64086 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64087 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64088 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64089 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64090 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-64091 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-64093 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-64094 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-64095 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-64096 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64097 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-64135 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64138 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-64164 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64165 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64166 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64168 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | — | Not Applicable |
| CVE-2026-64188 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | — | Not Applicable |
| CVE-2026-31396 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31761 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43207 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43232 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43249 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43283 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43291 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43324 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43497 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46250 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46265 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46270 | NONE0 | linux-libc-dev 5.15.0-87.97 fixed in 5.15.0-186.196 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53161 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53216 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53217 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53273 | NONE0 | linux-libc-dev 5.15.0-87.97 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.10 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.10-minimal 3.10.12-1~22.04.2 fixed in 3.10.12-1~22.04.16 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-25262 | NONE0 | texlive-binaries 2021.20210626.59705-1ubuntu0.1 fixed in 2021.20210626.59705-1ubuntu0.2 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-43961 | NONE0 | vim-common 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.31 | — | Not Applicable |
| CVE-2026-43961 | NONE0 | vim-tiny 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.31 | — | Not Applicable |
| CVE-2026-43961 | NONE0 | xxd 2:8.2.3995-1ubuntu2.12 fixed in 2:8.2.3995-1ubuntu2.31 | — | Not Applicable |
| GHSA-r4q5-vmmm-2653 | NONE0 | follow-redirects 1.15.2 fixed in 1.16.0 | — | Not Applicable |
| CVE-2024-38999 | NONE0 | requirejs 2.3.6 fixed in 2.3.7 | 0.7% Theoretical Threat | Not Applicable |
| GHSA-r292-9mhp-454m | NONE0 | tar 6.1.15 fixed in 7.5.21 | — | Not Applicable |
| CVE-2026-42215 | NONE0 | GitPython 3.1.40 fixed in 3.1.47 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-44244 | NONE0 | GitPython 3.1.40 fixed in 3.1.49 | 0.2% Theoretical Threat | Not Applicable |
| GHSA-2f96-g7mh-g2hx | NONE0 | GitPython 3.1.40 fixed in 3.1.51 | — | Not Applicable |
| GHSA-3rp5-jjmw-4wv2 | NONE0 | GitPython 3.1.40 fixed in 3.1.53 | — | Not Applicable |
| GHSA-6p8h-3wgx-97gf | NONE0 | GitPython 3.1.40 fixed in 3.1.54 | — | Not Applicable |
| GHSA-956x-8gvw-wg5v | NONE0 | GitPython 3.1.40 fixed in 3.1.51 | — | Not Applicable |
| GHSA-fjr4-x663-mwxc | NONE0 | GitPython 3.1.40 fixed in 3.1.54 | — | Not Applicable |
| GHSA-mv93-w799-cj2w | NONE0 | GitPython 3.1.40 fixed in 3.1.50 | — | Not Applicable |
| GHSA-r9mr-m37c-5fr3 | NONE0 | GitPython 3.1.40 fixed in 3.1.54 | — | Not Applicable |
| GHSA-rwj8-pgh3-r573 | NONE0 | GitPython 3.1.40 fixed in 3.1.52 | — | Not Applicable |
| GHSA-gj48-438w-jh9v | NONE0 | bleach 6.1.0 fixed in 6.4.0 | — | Not Applicable |
| GHSA-8rfp-98v4-mmr6 | NONE0 | bleach 6.1.0 fixed in 6.4.0 | — | Not Applicable |
| GHSA-537c-gmf6-5ccf | NONE0 | cryptography 41.0.4 fixed in 48.0.1 | — | Not Applicable |
| GHSA-h4gh-qq45-vh27 | NONE0 | cryptography 41.0.4 fixed in 43.0.1 | — | Not Applicable |
| CVE-2025-30167 | NONE0 | jupyter_core 5.4.0 fixed in 5.8.1 | 0.2% Theoretical Threat | Not Applicable |
| GHSA-gx64-gj6p-pc4c | NONE0 | jupyterlab 4.0.7 fixed in 4.6.2, 4.5.10 | — | Not Applicable |
| GHSA-pppj-hq3g-57pj | NONE0 | jupyterlab 4.0.7 fixed in 4.6.2, 4.5.10 | — | Not Applicable |
| GHSA-vmhf-c436-hxj4 | NONE0 | jupyterlab 4.0.7 fixed in 4.5.9 | — | Not Applicable |
| GHSA-whvh-wf3x-g77j | NONE0 | jupyterlab 4.0.7 fixed in 4.6.2, 4.5.10 | — | Not Applicable |
| CVE-2026-59922 | NONE0 | mistune 3.0.1 fixed in 3.3.0 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-59924 | NONE0 | mistune 3.0.1 fixed in 3.3.0 | 0.3% Theoretical Threat | Not Applicable |
| GHSA-6v7p-g79w-8964 | NONE0 | msgpack 1.0.6 fixed in 1.2.1 | — | Not Applicable |
| CVE-2026-49853 | NONE0 | tornado 6.3.3 fixed in 6.5.6 | — | Not Applicable |
| CVE-2026-49855 | NONE0 | tornado 6.3.3 fixed in 6.5.6 | — | Not Applicable |
| GHSA-753j-mpmx-qq6g | NONE0 | tornado 6.3.3 fixed in 6.4.1 | — | Not Applicable |
| GHSA-78cv-mqj4-43f7 | NONE0 | tornado 6.3.3 fixed in 6.5.5 | — | Not Applicable |
| GHSA-pw6j-qg29-8w7f | NONE0 | tornado 6.3.3 fixed in 6.5.7 | — | Not Applicable |
| GHSA-w235-7p84-xx57 | NONE0 | tornado 6.3.3 fixed in 6.4.1 | — | Not Applicable |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.