Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker with local code execution could exploit kernel CVEs (e.g., CVE-2026-43114 and CVE-2026-43133) to escalate privileges or escape the container if the host kernel is affected. Updating the host kernel to a patched version would fully eliminate exposure to these linux-libc-dev vulnerabilities. Note that the image ships only development headers, not the running kernel, so exploitability heavily depends on the host environment; however, the sheer number of medium-severity findings warrants caution.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-43114 | MEDIUM6.88 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43133 | MEDIUM6.71 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-15794 | MEDIUM6.7 | linux-libc-dev 6.8.0-117.117 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31402 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-38187 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38563 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-71073 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23171 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23208 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23226 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23227 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23378 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23412 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23413 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23428 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31474 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31488 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31532 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31566 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31709 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31720 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31729 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31759 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43049 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43059 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43120 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43128 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43329 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43378 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43499 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45891 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46274 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46323 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53148 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53262 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53359 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-14356 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-3238 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50090 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50240 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-0030 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-26242 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27022 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38581 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40954 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-44932 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44951 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44964 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46820 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46833 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53098 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21687 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71238 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23281 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23343 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23447 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23448 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31452 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31578 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31581 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31582 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31696 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43007 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43196 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43250 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45839 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45902 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45914 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45916 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45920 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45936 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45938 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45946 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45984 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45989 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45996 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45998 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46004 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46047 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46068 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46069 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46075 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46084 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46121 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46122 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46136 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46163 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46180 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46189 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46219 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46234 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46241 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46243 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52943 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52962 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52969 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52992 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53004 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53109 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53136 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53137 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53143 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53294 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53296 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53362 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53366 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63794 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63804 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64600 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-13165 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-12930 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-12931 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-26934 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-33053 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-50217 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-38069 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38206 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38421 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38565 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39859 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39862 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39896 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39958 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40014 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71152 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23221 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23233 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23234 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23319 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23359 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23361 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23387 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31399 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31455 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31485 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31489 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31493 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31500 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31506 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31527 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31530 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31576 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31580 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31583 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31686 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31702 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31715 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31730 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31731 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31747 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31748 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43015 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43020 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43027 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43150 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43205 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43328 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43426 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43458 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45866 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45867 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45879 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45882 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45885 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46246 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46267 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46285 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46294 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46301 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53059 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53089 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53097 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53098 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53112 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53115 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53117 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53118 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53120 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53129 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53156 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53157 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53195 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53272 | MEDIUM6.63 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-1193 | MEDIUM6.5 | linux-libc-dev 6.8.0-117.117 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-43501 | MEDIUM6.38 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-31669 | MEDIUM6.38 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43186 | MEDIUM6.38 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-46195 | MEDIUM6.38 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-53071 | MEDIUM6.38 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53266 | MEDIUM6.38 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-25836 | MEDIUM6.38 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40210 | MEDIUM6.38 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43110 | MEDIUM6.38 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43190 | MEDIUM6.38 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | libssl3t64 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40170 | MEDIUM6.29 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-14899 | MEDIUM6.29 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-43038 | MEDIUM6.21 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31607 | MEDIUM6.21 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43074 | MEDIUM6.21 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-23243 | MEDIUM6.21 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46244 | MEDIUM6.21 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43248 | MEDIUM6.21 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46135 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31613 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46259 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50551 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-14040 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53216 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58015 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21985 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22104 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38204 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38329 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38330 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38340 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38636 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40064 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68324 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68356 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71231 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23235 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23244 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23315 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23318 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23325 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23327 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23363 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23388 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23397 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31430 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31568 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31614 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31685 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31778 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43040 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43051 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43052 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43141 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43241 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43281 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43330 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43386 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43427 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43449 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43450 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43453 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45893 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45943 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45957 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45994 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46022 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46033 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46053 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46056 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46064 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46094 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46120 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46130 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46150 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46191 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46203 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46209 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52968 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53138 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53149 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53179 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53303 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53309 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53330 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43056 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43126 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43380 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43414 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45851 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46293 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53255 | MEDIUM6.03 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43304 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46043 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52989 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52993 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53002 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-54518 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23392 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31586 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31663 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31694 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31772 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43023 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43116 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43198 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43341 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43493 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-43494 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43503 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45852 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45972 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46119 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46185 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46275 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46319 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46330 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52924 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53006 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53036 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53072 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53175 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53182 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53185 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53212 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53224 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53239 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53250 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53254 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53256 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53264 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53270 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53275 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-3864 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-1247 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-2961 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50106 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37776 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-39905 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40135 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-40158 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40168 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-71203 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71221 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23270 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23454 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31408 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43050 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43158 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43226 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43233 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43303 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43334 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43339 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45856 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45859 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45860 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45910 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45942 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45970 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46015 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46052 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46054 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46076 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46090 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46099 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46114 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46116 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46117 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46123 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46133 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-46145 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46149 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46152 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46173 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46174 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46176 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46181 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46227 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46266 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46306 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46324 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52912 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52917 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52918 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52920 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52933 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52935 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52942 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52945 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52947 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52951 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52953 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52956 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52957 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52986 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-52991 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52998 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53000 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53005 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53009 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53011 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53016 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53049 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53075 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53091 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53131 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53132 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53133 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53223 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53228 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53242 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53246 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53268 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53354 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53355 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53357 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53361 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53381 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53384 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53388 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53391 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53392 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53397 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53398 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53399 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63795 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63800 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63801 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63802 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63807 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63808 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63809 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63823 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63824 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63826 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63829 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63830 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63831 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63875 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63883 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63884 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63886 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63887 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63888 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63889 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63891 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63896 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63898 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63899 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63901 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63912 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63913 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63914 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63916 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63917 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63919 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63920 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63921 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63922 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63924 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63925 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63928 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63940 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63944 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63945 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63946 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63947 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63952 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63956 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63957 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63958 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63962 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63970 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63971 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63975 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63978 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63979 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63984 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63992 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63993 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63994 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64000 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64001 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64002 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64007 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64009 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64011 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64015 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64017 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64018 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64025 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64026 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64029 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64032 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64034 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64047 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64048 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64051 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64098 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64099 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64102 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64109 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64111 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64113 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64114 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64115 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64117 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64136 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64137 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64160 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64174 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64189 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64191 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64192 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64217 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64247 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64255 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64266 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64268 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-64271 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64276 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64277 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64280 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64283 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64286 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64287 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64296 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64298 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64303 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-64304 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64305 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64306 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64312 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64317 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64319 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64320 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-64321 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64322 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64323 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64324 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64340 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64341 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64342 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64355 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64364 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64372 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64375 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64377 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64378 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64379 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64380 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64382 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64383 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64384 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64385 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64387 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64401 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64402 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64418 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64422 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64434 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64448 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64456 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64470 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64471 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64473 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64475 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64481 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64483 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64508 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64523 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64525 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64527 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64530 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64531 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64534 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64539 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64543 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64548 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64551 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64552 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64554 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-45885 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31508 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43332 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45861 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45894 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46251 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46325 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53053 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53062 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53078 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53110 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53189 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53202 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53209 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53230 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53253 | MEDIUM5.95 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt20 1.10.3-2ubuntu0.1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3714 | MEDIUM5.9 | linux-libc-dev 6.8.0-117.117 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-1121 | MEDIUM5.9 | linux-libc-dev 6.8.0-117.117 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-53196 | MEDIUM5.78 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46125 | MEDIUM5.78 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46331 | MEDIUM5.7 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-6238 | MEDIUM5.7 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53094 | MEDIUM5.7 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45991 | MEDIUM5.61 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53267 | MEDIUM5.61 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc-bin 2.39-0ubuntu8.7 fixed in 2.39-0ubuntu8.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.39-0ubuntu8.7 fixed in 2.39-0ubuntu8.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc-dev-bin 2.39-0ubuntu8.7 fixed in 2.39-0ubuntu8.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-dev-bin 2.39-0ubuntu8.7 fixed in 2.39-0ubuntu8.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc6 2.39-0ubuntu8.7 fixed in 2.39-0ubuntu8.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.39-0ubuntu8.7 fixed in 2.39-0ubuntu8.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc6-dev 2.39-0ubuntu8.7 fixed in 2.39-0ubuntu8.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6-dev 2.39-0ubuntu8.7 fixed in 2.39-0ubuntu8.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53176 | MEDIUM5.52 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2015-8553 | MEDIUM5.52 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40336 | MEDIUM5.52 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68729 | MEDIUM5.52 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31470 | MEDIUM5.52 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31588 | MEDIUM5.52 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64535 | MEDIUM5.52 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-0564 | MEDIUM5.52 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-43239 | MEDIUM5.52 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libbinutils 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf0 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libsframe1 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-40226 | MEDIUM5.44 | libsystemd0 255.4-1ubuntu8.15 fixed in 255.4-1ubuntu8.16 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | MEDIUM5.44 | libudev1 255.4-1ubuntu8.15 fixed in 255.4-1ubuntu8.16 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23383 | MEDIUM5.44 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23450 | MEDIUM5.44 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-31502 | MEDIUM5.44 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31516 | MEDIUM5.44 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31525 | MEDIUM5.44 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52910 | MEDIUM5.44 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53033 | MEDIUM5.44 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53085 | MEDIUM5.44 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53090 | MEDIUM5.44 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40074 | MEDIUM5.44 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23456 | MEDIUM5.44 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45932 | MEDIUM5.44 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-44034 | MEDIUM5.44 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | libp11-kit0 0.25.3-4ubuntu2.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23253 | MEDIUM5.27 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40146 | MEDIUM5.27 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40190 | MEDIUM5.18 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31449 | MEDIUM5.18 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31505 | MEDIUM5.18 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31700 | MEDIUM5.18 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31708 | MEDIUM5.18 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-40355 | MEDIUM5.18 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68736 | MEDIUM5.18 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43044 | MEDIUM5.18 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43134 | MEDIUM5.18 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31464 | MEDIUM5.18 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31511 | MEDIUM5.18 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31570 | MEDIUM5.18 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43197 | MEDIUM5.18 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31649 | MEDIUM5.1 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.39-0ubuntu8.7 fixed in 2.39-0ubuntu8.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-dev-bin 2.39-0ubuntu8.7 fixed in 2.39-0ubuntu8.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.39-0ubuntu8.7 fixed in 2.39-0ubuntu8.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6-dev 2.39-0ubuntu8.7 fixed in 2.39-0ubuntu8.8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | libssl3t64 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | libssl3t64 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-23246 | MEDIUM5.02 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | libssl3t64 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-23240 | MEDIUM4.93 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-23271 | MEDIUM4.93 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23317 | MEDIUM4.93 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31414 | MEDIUM4.93 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52908 | MEDIUM4.93 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40203 | MEDIUM4.93 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40340 | MEDIUM4.93 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23239 | MEDIUM4.93 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31426 | MEDIUM4.93 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43279 | MEDIUM4.93 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46065 | MEDIUM4.93 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46113 | MEDIUM4.93 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52923 | MEDIUM4.93 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31392 | MEDIUM4.93 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43284 | MEDIUM4.86 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | 93.2% Actively Exploited | Post-ExploitContext importance: MEDIUM |
| CVE-2026-43500 | MEDIUM4.86 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | 92.9% Actively Exploited | Post-ExploitContext importance: MEDIUM |
| CVE-2026-46024 | MEDIUM4.84 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-0537 | MEDIUM4.7 | linux-libc-dev 6.8.0-117.117 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | libssl3t64 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-31637 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45988 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-71315 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23066 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23222 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23340 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23391 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23449 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31403 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31436 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31447 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31454 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31469 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31473 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31507 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31528 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31548 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31554 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31648 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31665 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31673 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31678 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31680 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31693 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31758 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43009 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43016 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43019 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43030 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43060 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43083 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43084 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43091 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43093 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43111 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43153 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43214 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43215 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43278 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43365 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43406 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43407 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43408 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43437 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43456 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43502 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45850 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45864 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45899 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46273 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46304 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46320 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52909 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52958 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53050 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53086 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53151 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53159 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53183 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53269 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2015-7837 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-8660 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-0480 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-4543 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-48846 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48929 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49940 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50230 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50232 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50332 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50380 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-0160 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31082 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-52879 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53642 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-54190 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-14027 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27025 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35895 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35948 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35995 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41008 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42125 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42139 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43844 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43872 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-46742 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46748 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47729 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49904 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49908 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49910 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49916 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49932 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49940 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49970 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49990 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50003 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50034 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50102 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-52560 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53056 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53064 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53207 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56368 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56544 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56591 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56617 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56639 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56671 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56702 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56712 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57809 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57852 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57875 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57922 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57950 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57976 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58012 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58089 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58094 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58095 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58098 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58100 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58241 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21696 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21709 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21730 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21752 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21817 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21819 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21907 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22002 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22043 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-22108 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-22109 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22116 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22127 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23131 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23132 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23135 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23162 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37743 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37746 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37747 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37806 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37807 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37833 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37834 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37855 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37870 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37876 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37877 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37880 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37907 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38029 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38033 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38036 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38038 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38041 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38042 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38047 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38064 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38070 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38092 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-38096 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38132 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38140 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38168 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38188 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38189 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38199 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38203 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38205 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38207 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38237 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38261 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38272 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38311 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38353 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38359 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38360 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38372 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38426 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38438 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38498 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38597 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38605 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38621 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39677 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39745 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39762 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39764 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39771 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39789 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39833 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39908 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39910 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39925 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39933 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39990 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40005 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40040 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40075 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40086 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40102 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40195 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40334 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40362 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68188 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68193 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68209 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68211 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68212 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68236 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68251 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68281 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68304 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68309 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68317 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68333 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68334 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68353 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68730 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68802 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68822 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71115 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71158 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71161 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-71202 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71204 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-71223 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71227 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71229 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71232 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71233 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71235 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71236 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71237 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71239 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71265 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71266 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71267 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71269 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71272 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71273 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71285 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71286 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71287 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71288 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71289 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-71290 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71291 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71292 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-71293 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71294 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71295 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71297 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71299 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71300 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71302 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22981 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22985 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22993 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23017 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23100 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23104 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23137 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23138 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23152 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23154 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23157 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23196 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23201 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23217 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23220 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23228 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23229 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23236 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23237 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23238 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23241 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23242 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23247 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23249 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23255 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23259 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23265 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23266 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23267 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23272 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23276 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23277 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23278 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23279 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23284 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23285 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23286 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23287 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23289 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23290 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23291 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23292 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23293 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23296 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23298 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23300 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23303 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23304 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23307 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23308 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23310 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23312 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23313 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23321 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23324 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23330 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23334 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23335 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23339 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23346 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23347 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23352 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23356 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23357 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23360 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23362 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23365 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23367 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23368 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23369 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23370 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23371 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23374 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23375 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23377 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23379 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23381 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23382 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23386 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23389 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23396 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23398 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23399 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23401 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23414 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23418 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23419 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23420 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23426 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23434 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23438 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23439 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23442 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23446 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23460 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23461 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23462 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23464 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23465 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23468 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23470 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23472 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23474 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23475 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31391 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31394 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31400 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31407 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31410 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31411 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31412 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31415 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31416 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31418 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31420 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31421 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31422 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31423 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31424 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31425 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31427 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31428 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31429 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31434 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31438 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31439 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31440 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31441 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31450 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31451 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31458 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31461 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31462 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31467 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31479 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31480 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31482 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31483 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31486 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31487 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31492 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31495 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31496 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31497 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31498 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31499 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31503 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31509 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31510 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31512 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31515 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31518 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31519 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31520 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31521 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31522 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31524 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31526 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31531 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31537 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31540 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31542 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31545 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31546 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31549 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31550 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31551 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31552 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31555 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31556 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31557 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31560 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31565 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31575 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31577 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31579 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31585 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31590 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31592 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31594 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31595 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31596 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31599 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31603 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31604 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31605 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31606 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31610 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31615 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31616 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31617 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31618 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31619 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31623 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31624 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31625 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31628 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31630 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31634 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31638 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31639 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31642 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31645 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31646 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31651 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31655 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31658 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31660 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31661 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31662 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31664 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31670 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31671 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31672 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31674 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31675 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31676 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31677 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31679 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31681 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31682 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31684 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31687 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31689 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31692 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31698 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31699 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31701 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31704 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31714 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31721 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31722 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31723 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31724 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31725 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31726 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31737 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31738 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31740 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31741 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31749 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31752 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31754 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31755 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31756 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31762 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31763 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31767 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31770 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31773 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31777 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31781 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43010 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43012 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43013 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43014 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43017 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43018 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43021 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43022 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43024 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43025 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43026 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43028 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43029 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43032 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43034 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43035 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43036 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43041 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43042 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43043 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43045 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43046 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43048 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43054 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43057 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43058 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43061 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43062 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43064 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43065 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43066 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43068 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43069 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43072 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43073 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43079 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43080 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43081 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43082 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43085 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43086 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43088 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43089 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43092 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43094 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43098 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43099 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43101 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43103 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43104 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43105 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43107 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43109 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43113 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43115 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43118 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43119 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43123 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43124 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43127 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43129 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43130 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43131 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43132 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43135 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43136 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43137 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43139 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43140 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43143 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43145 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43147 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43148 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43149 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43152 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43156 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43157 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43159 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43161 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43162 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43165 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43167 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43168 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43169 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43170 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43171 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43172 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43173 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43175 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43182 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43183 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43187 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43189 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43191 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43194 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43195 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43199 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43200 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43201 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43202 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43204 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43209 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43213 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43216 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43218 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43219 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43220 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43221 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43223 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43225 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43227 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43228 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43229 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43230 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43231 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43234 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43238 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43240 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43242 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43243 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43244 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43246 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43251 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43252 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43253 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43255 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43257 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43261 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43262 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43264 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43265 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43266 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43267 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43268 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43269 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43270 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43271 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43273 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43277 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43287 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43288 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43289 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43292 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43294 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43295 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43296 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43297 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43298 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43299 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43300 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43301 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43302 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43305 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43306 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43308 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43309 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43310 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43311 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43312 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43313 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43314 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43315 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43316 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43317 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43318 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43319 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43320 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43327 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43331 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43333 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43338 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43340 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43343 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43344 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43345 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43350 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43355 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43357 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43359 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43360 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43361 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43362 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43363 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43366 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43371 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43372 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43381 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43382 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43387 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43395 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43397 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43398 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43400 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43405 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43409 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43410 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43411 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43412 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43413 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43416 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43419 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43421 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43424 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43425 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43428 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43429 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43432 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43436 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43441 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43443 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43445 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43451 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43452 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43455 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43457 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43459 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43463 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43464 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43466 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43467 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43468 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43469 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43471 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43472 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43473 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43474 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43475 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43483 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43488 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43491 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43492 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43496 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45834 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45835 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45836 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45840 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45842 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45843 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45845 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45846 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45847 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45848 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45855 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45857 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45873 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45886 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45890 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45901 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45904 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45912 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45913 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45915 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45917 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45919 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45921 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45923 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45924 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45928 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45930 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45934 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45940 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45941 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45944 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45947 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45948 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45954 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45960 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45961 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45962 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45963 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45964 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45965 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45968 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45969 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45973 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45974 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45976 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45978 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45981 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45982 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45983 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45985 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45986 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45987 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45997 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45999 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46000 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46002 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46003 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46005 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46007 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46009 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46012 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46014 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46016 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46018 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46019 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46021 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46023 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46026 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46027 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46032 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46037 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46038 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46040 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46041 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46044 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46046 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46049 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46050 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46051 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46059 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46061 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46063 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46066 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46070 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46071 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46072 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46073 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46077 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46078 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46079 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46080 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46082 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46083 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46086 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46088 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46089 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46091 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46092 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46098 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46101 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46102 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46103 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46106 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46107 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46108 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46111 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46115 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46126 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46127 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46128 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46131 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46132 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46137 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46138 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46139 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46142 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46143 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46144 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46146 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46148 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46151 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46153 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46157 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46158 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46160 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46161 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46167 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46168 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46169 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46170 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46171 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46172 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46178 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46179 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46184 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46186 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46190 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46193 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46196 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46200 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46201 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46207 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46211 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46214 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46220 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46225 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46226 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46229 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46231 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46233 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46235 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46236 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46247 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46260 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46289 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46302 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46303 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46314 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46315 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46321 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46322 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52913 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52915 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52916 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52921 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52925 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52926 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52927 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52928 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52929 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52930 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52936 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52937 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52939 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52941 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52944 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52946 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52948 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52954 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52960 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52961 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52963 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52964 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52967 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52970 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52972 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52974 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52975 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52977 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52981 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52984 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52985 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52988 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52990 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52994 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52995 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52999 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53001 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53003 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53012 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53013 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53014 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53015 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53017 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53018 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53021 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53022 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53023 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53027 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53032 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53034 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53037 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53039 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53056 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53064 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53066 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53069 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53074 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53076 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53077 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53080 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53083 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53088 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53103 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53107 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53122 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53128 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53134 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53139 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53140 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53144 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53150 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53163 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53167 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53168 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53181 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53184 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53190 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53199 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53208 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53210 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53214 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53218 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53219 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53220 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53221 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53227 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53245 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53251 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53252 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53263 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53274 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53279 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53281 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53284 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53285 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53287 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53289 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53291 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53292 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53293 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53295 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53297 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53304 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53306 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53313 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53314 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53317 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53320 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53325 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53327 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53331 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53332 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53336 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53337 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53339 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53343 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53345 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53347 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53349 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53350 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53353 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53358 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53365 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53369 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53376 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53377 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53379 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53382 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53385 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53393 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53400 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53402 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53403 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63798 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63803 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63810 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63821 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63822 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63832 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63838 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63843 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63844 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63845 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63851 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63852 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63853 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63858 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63860 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63865 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63867 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63868 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63869 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63870 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63871 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63872 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63876 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63877 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63890 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63892 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63893 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63897 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63900 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63902 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63903 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63904 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63906 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63926 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63927 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63942 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63943 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63948 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63961 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63963 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63964 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63968 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63969 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63973 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63974 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63976 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63980 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63983 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63985 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63990 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63991 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63999 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64003 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64004 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64005 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64006 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64012 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64014 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64036 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64038 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64039 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64046 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64052 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64060 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64064 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64070 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64073 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64076 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64077 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64078 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64079 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64103 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64106 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64112 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64116 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64118 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64121 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64123 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64125 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-64126 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64127 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64128 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64131 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64133 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64134 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64144 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64146 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64153 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64155 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64158 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64163 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64170 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64173 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64176 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64177 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64178 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64179 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64180 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64182 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64183 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64184 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64185 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64187 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64190 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64205 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64206 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64210 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64212 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64213 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64214 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64220 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64222 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64225 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64227 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64231 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64237 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64239 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64243 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64244 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64245 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64254 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64256 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64275 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64279 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64289 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64294 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64297 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64299 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64301 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64313 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64315 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64316 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64326 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64329 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64330 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64332 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64333 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64334 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64335 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64336 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64338 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64343 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64344 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64346 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64347 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64351 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64352 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64360 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64362 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64363 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64365 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64368 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64369 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64370 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64373 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64374 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64376 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64381 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64388 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64403 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64404 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64405 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64406 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64407 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64408 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64409 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64411 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64412 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64413 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64417 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64419 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64423 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64424 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64428 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64430 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64433 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64435 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64436 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64452 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64454 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64455 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64458 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64463 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64465 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64472 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64474 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64476 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64478 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64479 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64480 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64482 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64486 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64487 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64488 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64489 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64496 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64507 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64510 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64511 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64512 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64513 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64514 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64524 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64529 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64537 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64540 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64541 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64542 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64544 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64545 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64546 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64547 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64553 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64555 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-13693 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-12928 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-12929 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-21693 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22077 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-71304 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71305 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71313 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23230 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23306 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23336 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23444 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31446 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31448 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31453 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31667 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31771 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31779 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43071 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43180 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43211 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43352 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43353 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43465 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43480 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43484 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43485 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45838 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45841 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45844 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45849 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45858 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45862 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45865 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45868 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45869 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45870 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45871 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45872 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45875 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45877 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45880 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45881 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45883 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45884 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45895 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45897 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45911 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46147 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46245 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46249 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46252 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46253 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46254 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46255 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46261 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46280 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46282 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46286 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46287 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46291 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46292 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46296 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46299 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46307 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46312 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52982 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53035 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53047 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53048 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53052 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53058 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53060 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53061 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53063 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53065 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53070 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53073 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53082 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53084 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53093 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53096 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53102 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53104 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53106 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53111 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53113 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53123 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53126 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53135 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53142 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53146 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53147 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53154 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53158 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53177 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53205 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53207 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53213 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53225 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53226 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53229 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53232 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53236 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53237 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53238 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53249 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53258 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53261 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53265 | MEDIUM4.67 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g 1:1.3.dfsg-3.1ubuntu2.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-6952 | MEDIUM4.5 | patch 2.7.6-7build3 No fix yet | 8.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4046 | MEDIUM4.5 | libc-bin 2.39-0ubuntu8.7 fixed in 2.39-0ubuntu8.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-dev-bin 2.39-0ubuntu8.7 fixed in 2.39-0ubuntu8.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6 2.39-0ubuntu8.7 fixed in 2.39-0ubuntu8.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6-dev 2.39-0ubuntu8.7 fixed in 2.39-0ubuntu8.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | liblzma5 5.6.1+really5.4.5-1ubuntu0.2 fixed in 5.6.1+really5.4.5-1ubuntu0.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | libssl3t64 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | libssl3t64 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-23457 | MEDIUM4.5 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53194 | MEDIUM4.5 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64538 | MEDIUM4.5 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40217 | MEDIUM4.42 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40338 | MEDIUM4.42 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40344 | MEDIUM4.42 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.39-0ubuntu8.7 fixed in 2.39-0ubuntu8.8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.39-0ubuntu8.7 fixed in 2.39-0ubuntu8.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-dev-bin 2.39-0ubuntu8.7 fixed in 2.39-0ubuntu8.8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-dev-bin 2.39-0ubuntu8.7 fixed in 2.39-0ubuntu8.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.39-0ubuntu8.7 fixed in 2.39-0ubuntu8.8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.39-0ubuntu8.7 fixed in 2.39-0ubuntu8.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6-dev 2.39-0ubuntu8.7 fixed in 2.39-0ubuntu8.8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6-dev 2.39-0ubuntu8.7 fixed in 2.39-0ubuntu8.8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam-modules 1.5.3-5ubuntu5.5 fixed in 1.5.3-5ubuntu5.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam-modules-bin 1.5.3-5ubuntu5.5 fixed in 1.5.3-5ubuntu5.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam-runtime 1.5.3-5ubuntu5.5 fixed in 1.5.3-5ubuntu5.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam0g 1.5.3-5ubuntu5.5 fixed in 1.5.3-5ubuntu5.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.39.3-9ubuntu6.5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount1 2.39.3-9ubuntu6.5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols1 2.39.3-9ubuntu6.5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.39.3-9ubuntu6.5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52955 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-57857 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23004 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23169 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43047 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-39293 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-42107 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56552 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56788 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21984 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37906 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38242 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38440 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38717 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39754 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39884 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40139 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68239 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68296 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68745 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-71074 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71274 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23118 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23181 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23207 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23302 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23348 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23440 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23441 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23452 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23463 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23469 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31393 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31466 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31523 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31697 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31728 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31751 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43053 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43163 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43275 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43342 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43383 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43415 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43420 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43430 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43439 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43448 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45905 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45949 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46159 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46187 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46194 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53108 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53352 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31389 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46272 | MEDIUM4 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-15213 | LOW3.91 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4010 | LOW3.91 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-41992 | LOW3.82 | gzip 1.12-1ubuntu3.1 fixed in 1.12-1ubuntu3.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-68360 | LOW3.82 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | LOW3.77 | openssl 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-46300 | LOW3.74 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | 7.0% Low-Moderate Risk | Post-ExploitContext importance: MEDIUM |
| CVE-2026-46333 | LOW3.74 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | 1.5% Low-Moderate Risk | Post-ExploitContext importance: MEDIUM |
| CVE-2026-23458 | LOW3.74 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-17977 | LOW3.74 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-68768 | LOW3.74 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2020-14304 | LOW3.74 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-41848 | LOW3.57 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc-bin 2.39-0ubuntu8.7 fixed in 2.39-0ubuntu8.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc-dev-bin 2.39-0ubuntu8.7 fixed in 2.39-0ubuntu8.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc6 2.39-0ubuntu8.7 fixed in 2.39-0ubuntu8.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc6-dev 2.39-0ubuntu8.7 fixed in 2.39-0ubuntu8.8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | LOW3.3 | binutils 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-common 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1152 | LOW3.15 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | libssl3t64 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | LOW3.01 | openssl 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.01 | openssl 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | libperl5.38t64 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-base 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-modules-5.38 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34180 | LOW3 | openssl 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | libssl3t64 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2020-35501 | LOW2.89 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-45582 | LOW2.86 | tar 1.35+dfsg-3build1 fixed in 1.35+dfsg-3ubuntu0.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2013-7445 | LOW2.81 | linux-libc-dev 6.8.0-117.117 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19378 | LOW2.81 | linux-libc-dev 6.8.0-117.117 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19814 | LOW2.81 | linux-libc-dev 6.8.0-117.117 No fix yet | 3.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW2.8 | openssl 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2019-20633 | LOW2.8 | patch 2.7.6-7build3 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2021-45261 | LOW2.8 | patch 2.7.6-7build3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.35+dfsg-3build1 fixed in 1.35+dfsg-3ubuntu0.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW2.8 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 255.4-1ubuntu8.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 255.4-1ubuntu8.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31668 | LOW2.8 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | LOW2.78 | libperl5.38t64 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | LOW2.78 | libssl3t64 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | LOW2.78 | openssl 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | LOW2.78 | perl 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | LOW2.78 | perl-base 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | LOW2.78 | perl-modules-5.38 5.38.2-3.2ubuntu0.2 fixed in 5.38.2-3.2ubuntu0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0400 | LOW2.7 | linux-libc-dev 6.8.0-117.117 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-20426 | LOW2.7 | linux-libc-dev 6.8.0-117.117 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42766 | LOW2.7 | openssl 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-42767 | LOW2.7 | openssl 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-34743 | LOW2.7 | xz-utils 5.6.1+really5.4.5-1ubuntu0.2 fixed in 5.6.1+really5.4.5-1ubuntu0.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43037 | LOW2.69 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-23395 | LOW2.69 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-63797 | LOW2.57 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23455 | LOW2.56 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-46242 | LOW2.52 | linux-libc-dev 6.8.0-117.117 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-31788 | LOW2.51 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43112 | LOW2.48 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.39.3-9ubuntu6.5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.12-1ubuntu3.1 fixed in 1.12-1ubuntu3.2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.39.3-9ubuntu6.5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.39.3-9ubuntu6.5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW2.38 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libbinutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf-nobfd0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libgprofng0 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libsframe1 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW1.89 | binutils 2.42-4ubuntu2.10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-45446 | LOW1.89 | openssl 3.0.13-0ubuntu3.9 fixed in 3.0.13-0ubuntu3.11 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | login 1:4.13+dfsg1-4ubuntu3.2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.13+dfsg1-4ubuntu3.2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-common 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-x86-64-linux-gnu 2.42-4ubuntu2.10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | NONE0 | libncursesw6 6.4+20240113-1ubuntu2 fixed in 6.4+20240113-1ubuntu2.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.4+20240113-1ubuntu2 fixed in 6.4+20240113-1ubuntu2.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.4+20240113-1ubuntu2 fixed in 6.4+20240113-1ubuntu2.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.4+20240113-1ubuntu2 fixed in 6.4+20240113-1ubuntu2.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-11822 | NONE0 | libsqlite3-0 3.45.1-1ubuntu2.5 fixed in 3.45.1-1ubuntu2.6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-0 3.45.1-1ubuntu2.5 fixed in 3.45.1-1ubuntu2.6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50812 | NONE0 | libsqlite3-0 3.45.1-1ubuntu2.5 fixed in 3.45.1-1ubuntu2.7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50813 | NONE0 | libsqlite3-0 3.45.1-1ubuntu2.5 fixed in 3.45.1-1ubuntu2.7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43011 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53215 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23372 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23393 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31405 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31413 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31432 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31433 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31476 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31478 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31584 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31627 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31656 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31657 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31659 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31695 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31705 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31706 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31712 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31716 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31780 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43075 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43076 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43206 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43222 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43236 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43263 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43370 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43490 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45878 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-47331 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47333 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52911 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52914 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53040 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53043 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53046 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53068 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53130 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53186 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53198 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-54105 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54187 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40003 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40012 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40073 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40097 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40098 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40150 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40208 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40274 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40332 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40335 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40354 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40356 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-54505 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-62626 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68174 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68175 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68196 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68230 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68318 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68338 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68376 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68781 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23245 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23364 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31409 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31417 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31477 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31494 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31563 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31597 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31598 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31602 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31611 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31612 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31622 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31626 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31629 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31683 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31707 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31711 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31768 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43117 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43184 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43203 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43212 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43245 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43258 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43336 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43368 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43373 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43377 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43384 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43476 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43495 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45935 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45958 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46006 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46011 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46031 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46058 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46062 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46110 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46112 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46124 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46129 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46164 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46177 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46197 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46198 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46199 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46204 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46205 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46206 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46208 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46212 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46218 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46230 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46232 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46238 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46328 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47326 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47327 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47328 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47332 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47334 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47335 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47337 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52919 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52922 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52931 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52934 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53041 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53045 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53329 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53356 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53368 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53374 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53375 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53383 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-53386 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53387 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53389 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53390 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53401 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63793 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63796 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63805 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63806 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63811 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63812 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63814 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63815 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63816 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63817 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63818 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63819 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63825 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63827 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63828 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63833 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63834 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63835 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63836 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63846 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63847 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63848 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63854 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63855 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63856 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63861 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63862 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63879 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63881 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63882 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63895 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63905 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63908 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63909 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63915 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63930 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63931 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63933 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63934 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63949 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63954 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63959 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63960 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63967 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64010 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64022 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64023 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64033 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64055 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64056 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64082 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64083 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64084 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64085 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64086 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64087 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64088 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64089 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64090 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64091 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64092 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64093 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64094 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64095 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64096 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64097 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64108 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64135 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64138 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64147 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64148 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64154 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64164 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64165 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64166 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64168 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64188 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64218 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64219 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64221 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64233 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64234 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64240 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64241 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64242 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64246 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64249 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64269 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64270 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64272 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64273 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64274 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64318 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64331 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64337 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64345 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64348 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64350 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64358 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64359 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64361 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64371 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64386 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64389 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64390 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64391 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64392 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64393 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64394 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64395 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64396 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64397 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64398 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64399 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64400 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64420 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64421 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64425 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64429 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64432 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64438 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64440 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64441 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64442 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64443 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64444 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64445 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64446 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64449 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64450 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64461 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64462 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64468 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64469 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64484 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64493 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64494 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64495 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64497 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64500 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64503 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64504 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64505 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64518 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64528 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64532 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64533 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64536 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64549 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64550 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-20585 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31396 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31587 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31761 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43207 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43232 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43249 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43256 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43283 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43291 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43324 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43497 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-136.136 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46250 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46265 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46270 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-134.134 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47329 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47330 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47336 | NONE0 | linux-libc-dev 6.8.0-117.117 fixed in 6.8.0-124.124 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53160 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53161 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53216 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53217 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53247 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53273 | NONE0 | linux-libc-dev 6.8.0-117.117 No fix yet | 0.1% Theoretical Threat | Not Applicable |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
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.