This image carries significant risk; production deployment is highly discouraged without strict compensating controls. Over 1,665 vulnerabilities were identified, 202 with severity >=6.0 (max 6.63), including CVE-2026-31402 and CVE-2026-23428. These kernel vulnerabilities require local access and are present in the linux-libc-dev package, which is typically used for development and not loaded at runtime, reducing exploitability. However, an attacker with local shell access could still attempt to leverage them for privilege escalation. The threat score of 50 confirms caution is warranted.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-31402 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-23428 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43378 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46274 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50240 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-0030 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-26242 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27022 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38581 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40954 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-44932 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44951 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44964 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46820 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46833 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53098 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21687 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37882 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38069 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38082 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38091 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38187 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38206 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38421 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38563 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-38565 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39859 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39862 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39896 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39958 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40014 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71073 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71152 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71238 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23171 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23208 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23221 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23226 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23227 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23233 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23234 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23319 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23343 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23344 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23359 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23361 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23378 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23387 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23390 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23412 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23413 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23447 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23448 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31399 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31452 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31455 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31474 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31485 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31488 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31489 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31493 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31500 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31506 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31527 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31530 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31532 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31566 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31576 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31578 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31580 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31581 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31582 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31583 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31686 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31688 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31696 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31702 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31709 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31715 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31720 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31729 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31730 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31731 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31747 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31748 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31759 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31776 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43007 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43015 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43020 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43027 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43049 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43120 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43128 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43150 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43196 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43205 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43250 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43328 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43426 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43458 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45946 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45989 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45996 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46004 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46047 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46163 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46180 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46189 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46219 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46234 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46241 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46243 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-33053 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-50217 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46246 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46267 | MEDIUM6.63 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-18064 | MEDIUM6.5 | libcairo-gobject2 1.18.0-3build1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | MEDIUM6.5 | libcairo2 1.18.0-3build1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-1193 | MEDIUM6.5 | linux-libc-dev 6.8.0-124.124 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1352 | MEDIUM6.38 | libelf1t64 0.190-1.1ubuntu0.1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-41989 | MEDIUM6.38 | libgcrypt20 1.10.3-2build1 fixed in 1.10.3-2ubuntu0.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-26740 | MEDIUM6.38 | libgif7 5.2.2-1ubuntu1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-33846 | MEDIUM6.38 | libgnutls30t64 3.8.3-1.1ubuntu3.5 fixed in 3.8.3-1.1ubuntu3.6 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-42009 | MEDIUM6.38 | libgnutls30t64 3.8.3-1.1ubuntu3.5 fixed in 3.8.3-1.1ubuntu3.6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-43501 | MEDIUM6.38 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31669 | MEDIUM6.38 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43186 | MEDIUM6.38 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-46195 | MEDIUM6.38 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-25836 | MEDIUM6.38 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40210 | MEDIUM6.38 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43110 | MEDIUM6.38 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43190 | MEDIUM6.38 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3833 | MEDIUM6.29 | libgnutls30t64 3.8.3-1.1ubuntu3.5 fixed in 3.8.3-1.1ubuntu3.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM6.29 | libgnutls30t64 3.8.3-1.1ubuntu3.5 fixed in 3.8.3-1.1ubuntu3.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-40170 | MEDIUM6.29 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-14899 | MEDIUM6.29 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-43038 | MEDIUM6.21 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31607 | MEDIUM6.21 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-23243 | MEDIUM6.21 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43074 | MEDIUM6.21 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43248 | MEDIUM6.21 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46244 | MEDIUM6.21 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM6.03 | libgnutls30t64 3.8.3-1.1ubuntu3.5 fixed in 3.8.3-1.1ubuntu3.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46135 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-23455 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46259 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50551 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53216 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58015 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21985 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22104 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38204 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38329 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38330 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38340 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38636 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40064 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68324 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68356 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71231 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23235 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23244 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23315 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23318 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23325 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23327 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23363 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23388 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23397 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31430 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31568 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31613 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31614 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31685 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31778 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43040 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43051 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43052 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43056 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43126 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43141 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43241 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43281 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43330 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43380 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43386 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43427 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43449 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43450 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43453 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45957 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45994 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46022 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46033 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46056 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46120 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46150 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46191 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46203 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46209 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43414 | MEDIUM6.03 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23868 | MEDIUM5.95 | libgif7 5.2.2-1ubuntu1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5222 | MEDIUM5.95 | libicu74 74.2-1ubuntu3.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43304 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46043 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43198 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43341 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43493 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45972 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46119 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46185 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46275 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46319 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-3864 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-1247 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-2961 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50106 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37776 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39905 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40135 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40158 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40168 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71203 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71221 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23270 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23392 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23454 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31408 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31508 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31586 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31663 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31694 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31772 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43023 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43050 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43116 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43158 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43226 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43233 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43303 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43329 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43332 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43334 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43339 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43491 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45840 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45852 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45856 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45858 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45859 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45860 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45861 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45886 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45892 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45894 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45899 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45910 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45912 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45934 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45942 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45970 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45984 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46015 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46052 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46053 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46054 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46069 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46076 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46084 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46090 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46099 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46114 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46116 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46117 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46121 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46123 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46125 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46132 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46133 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-46139 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46145 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46149 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46152 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46173 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46174 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46176 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46181 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46227 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46242 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46266 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46306 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46324 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46325 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46330 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-45885 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46251 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46294 | MEDIUM5.95 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt20 1.10.3-2build1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3714 | MEDIUM5.9 | linux-libc-dev 6.8.0-124.124 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2018-1121 | MEDIUM5.9 | linux-libc-dev 6.8.0-124.124 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6238 | MEDIUM5.7 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.61 | libgnutls30t64 3.8.3-1.1ubuntu3.5 fixed in 3.8.3-1.1ubuntu3.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45991 | MEDIUM5.61 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42013 | MEDIUM5.58 | libgnutls30t64 3.8.3-1.1ubuntu3.5 fixed in 3.8.3-1.1ubuntu3.6 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-4437 | MEDIUM5.52 | libc-bin 2.39-0ubuntu8.7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.39-0ubuntu8.7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc-dev-bin 2.39-0ubuntu8.7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-dev-bin 2.39-0ubuntu8.7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc6 2.39-0ubuntu8.7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.39-0ubuntu8.7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc6-dev 2.39-0ubuntu8.7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6-dev 2.39-0ubuntu8.7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-37769 | MEDIUM5.52 | libpixman-1-0 0.42.2-1build1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2015-8553 | MEDIUM5.52 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40336 | MEDIUM5.52 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68729 | MEDIUM5.52 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31470 | MEDIUM5.52 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31588 | MEDIUM5.52 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43239 | MEDIUM5.52 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-0564 | MEDIUM5.52 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.6% 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-7475 | MEDIUM5.5 | libcairo-gobject2 1.18.0-3build1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | MEDIUM5.5 | libcairo2 1.18.0-3build1 No fix yet | 1.8% 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-23450 | MEDIUM5.44 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-40074 | MEDIUM5.44 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23383 | MEDIUM5.44 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23456 | MEDIUM5.44 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31502 | MEDIUM5.44 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31516 | MEDIUM5.44 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31525 | MEDIUM5.44 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45932 | MEDIUM5.44 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-44034 | MEDIUM5.44 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-40146 | MEDIUM5.27 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23253 | MEDIUM5.27 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40190 | MEDIUM5.18 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40355 | MEDIUM5.18 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68736 | MEDIUM5.18 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31449 | MEDIUM5.18 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31464 | MEDIUM5.18 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31505 | MEDIUM5.18 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31511 | MEDIUM5.18 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31570 | MEDIUM5.18 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31700 | MEDIUM5.18 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31708 | MEDIUM5.18 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43044 | MEDIUM5.18 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43134 | MEDIUM5.18 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43321 | MEDIUM5.18 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43197 | MEDIUM5.18 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31649 | MEDIUM5.1 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.39-0ubuntu8.7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-dev-bin 2.39-0ubuntu8.7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.39-0ubuntu8.7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6-dev 2.39-0ubuntu8.7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23246 | MEDIUM5.02 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23240 | MEDIUM4.93 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31414 | MEDIUM4.93 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40203 | MEDIUM4.93 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40340 | MEDIUM4.93 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23239 | MEDIUM4.93 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23271 | MEDIUM4.93 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23317 | MEDIUM4.93 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31392 | MEDIUM4.93 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31426 | MEDIUM4.93 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43279 | MEDIUM4.93 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46065 | MEDIUM4.93 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46113 | MEDIUM4.93 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46024 | MEDIUM4.84 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-0537 | MEDIUM4.7 | linux-libc-dev 6.8.0-124.124 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-59529 | MEDIUM4.67 | libavahi-client3 0.8-13ubuntu6.2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59529 | MEDIUM4.67 | libavahi-common-data 0.8-13ubuntu6.2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59529 | MEDIUM4.67 | libavahi-common3 0.8-13ubuntu6.2 No fix yet | 0.2% Theoretical Threat | 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-66382 | MEDIUM4.67 | libexpat1 2.6.1-2ubuntu0.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1-dev 2.6.1-2ubuntu0.4 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-31637 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45988 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-71315 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31436 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43083 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43084 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43406 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43407 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46273 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46304 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46320 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2015-7837 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-8660 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-0480 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-4543 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-48846 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48929 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49940 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50230 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50232 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50332 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50380 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-0160 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31082 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-52879 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53642 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-54190 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-14027 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27025 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35895 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35948 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35995 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41008 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42125 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42139 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43844 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43872 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-46742 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46748 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47729 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49904 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49908 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49910 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49916 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49932 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49940 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49970 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49990 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50003 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50034 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50102 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-52560 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53056 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53064 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53207 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56368 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56544 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56591 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56617 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56639 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56671 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56702 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56712 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57809 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57852 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57875 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57922 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57950 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57976 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58012 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58089 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58094 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58095 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58098 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58100 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58241 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21693 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21696 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21709 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21730 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21751 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21752 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21817 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21819 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21907 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22002 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22043 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22077 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22108 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22109 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22116 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22127 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23131 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23132 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23135 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23162 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37743 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37746 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37747 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37806 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37807 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37833 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37834 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37855 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37870 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37876 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37877 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37880 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37907 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38029 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38033 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38036 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38038 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38041 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38042 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38047 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38064 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38070 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38092 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38096 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38132 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38140 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38168 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38188 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38189 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38199 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38203 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38205 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38207 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38237 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38261 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38272 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38311 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38353 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38359 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38360 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38372 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38426 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38438 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38486 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38498 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38597 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38605 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38621 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38669 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38672 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38673 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38674 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38689 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39677 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39745 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39762 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39764 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39771 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39789 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39833 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39908 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39910 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39925 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39933 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39990 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40005 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40040 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-40075 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40086 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40102 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40195 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40334 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40362 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68188 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68193 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68209 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68211 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68212 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68236 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68251 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68281 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68304 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68309 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68317 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68333 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68334 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68353 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68730 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68779 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68802 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68822 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71115 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71158 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71161 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71202 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71204 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71223 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71227 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71229 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71232 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71233 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71235 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71236 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71237 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71239 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71265 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71266 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71267 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71269 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71272 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71273 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71285 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71286 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71287 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71288 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71289 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71290 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71291 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71292 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71293 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71294 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71295 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71297 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71299 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71300 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71302 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71305 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71313 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22981 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22985 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22993 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23017 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23066 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23100 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23104 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23137 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23138 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23152 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23154 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23157 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23196 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23201 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23217 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23220 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23222 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23228 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23229 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23230 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23236 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23237 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23238 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23241 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23242 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23247 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23248 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23249 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23255 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23259 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23265 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23266 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23267 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23272 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23276 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23277 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23278 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23279 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23284 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23285 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23286 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23287 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23289 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23290 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23291 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23292 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23293 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23296 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23298 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23300 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23303 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23304 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23306 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23307 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23308 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23310 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23312 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23313 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23321 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23324 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23330 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23334 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23335 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23336 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23339 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23340 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23346 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23347 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23352 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23356 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23357 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23360 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23362 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23365 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23367 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23368 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23369 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23370 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23371 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23374 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23375 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23377 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23379 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23381 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23382 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23386 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23389 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23391 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23396 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23398 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23399 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23401 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23414 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23418 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23419 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23420 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23426 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23434 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23438 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23439 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23442 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23444 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23446 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23449 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23460 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23461 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23462 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23464 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23465 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23468 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23470 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23472 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23474 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23475 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31391 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31394 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31400 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31403 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31407 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31410 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31411 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31412 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31415 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31416 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31418 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31420 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31421 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31422 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31423 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31424 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31425 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31427 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31428 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31429 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31434 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31438 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31439 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31440 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31441 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31446 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31447 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31450 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31451 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31453 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31454 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31458 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31461 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31462 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31467 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31469 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31473 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31479 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31480 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31482 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31483 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31486 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31487 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31492 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31495 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31496 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31497 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31498 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31499 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31503 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31507 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31509 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31510 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31512 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31515 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31518 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31519 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31520 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31521 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31522 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31524 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31526 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31528 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31531 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31537 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31540 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31542 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31545 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31546 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31548 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31549 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31550 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31551 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31552 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31554 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31555 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31556 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31557 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31560 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31565 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31575 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31577 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31579 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31585 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31590 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31592 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31594 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31595 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31596 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31599 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31603 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31604 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31605 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31606 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31610 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31615 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31616 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31617 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31618 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31619 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31623 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31624 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31625 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31628 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31630 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31634 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31638 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31639 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31642 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31645 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31646 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31648 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31651 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31655 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31658 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31660 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31661 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31662 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31664 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31665 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31667 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31670 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31671 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31672 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31673 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31674 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31675 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31677 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31678 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31679 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31680 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31681 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31682 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31684 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31687 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31689 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31692 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31693 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31698 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31699 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31701 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31704 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31714 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31721 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31722 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31723 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31724 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31725 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31726 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31737 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31738 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31740 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31741 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31749 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31752 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31754 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31755 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31756 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31758 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31762 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31763 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31767 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31770 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31771 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31773 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31777 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31779 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31781 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43009 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43010 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43012 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43013 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43014 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43016 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43017 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43018 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43019 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43021 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43022 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43024 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43025 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43026 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43028 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43029 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43030 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43032 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43034 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43035 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43036 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43041 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43042 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43043 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43045 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43046 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43048 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43054 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43057 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43058 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43059 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43060 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43061 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43062 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43064 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43065 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43066 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43068 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43069 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43072 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43073 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43079 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43080 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43081 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43082 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43085 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43086 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43088 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43089 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43091 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43092 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43093 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43094 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43098 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43099 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43101 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43103 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43104 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43105 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43107 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43109 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43111 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43112 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43113 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43114 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43115 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43118 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43119 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43123 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43124 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43127 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43129 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43130 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43131 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43132 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43133 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43135 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43136 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43137 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43139 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43140 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43143 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43145 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43147 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43148 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43149 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43152 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43153 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43156 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43157 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43159 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43161 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43162 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43165 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43167 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43168 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43169 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43170 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43171 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43172 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43173 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43175 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43176 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43180 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43182 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43183 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43187 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43189 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43191 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43194 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43195 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43199 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43200 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43201 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43202 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43204 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43209 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43211 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43213 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43214 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43215 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43216 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43218 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43219 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43220 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43221 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43223 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43225 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43227 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43228 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43229 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43230 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43231 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43234 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43238 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43240 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43242 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43243 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43244 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43246 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43251 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43252 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43253 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43255 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43257 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43261 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43262 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43264 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43265 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43266 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43267 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43268 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43269 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43270 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43271 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43273 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43277 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43278 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43287 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43288 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43289 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43292 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43294 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43295 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43296 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43297 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43298 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43299 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43300 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43301 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43302 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43305 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43306 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43308 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43309 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43310 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43311 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43312 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43313 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43314 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43315 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43316 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43317 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43318 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43319 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43320 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43327 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43331 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43333 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43338 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43340 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43343 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43344 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43345 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43350 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43352 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43353 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43355 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43357 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43359 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43360 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43361 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43362 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43363 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43365 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43366 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43371 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43372 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43381 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43382 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43387 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43395 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43397 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43398 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43400 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43405 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43408 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43409 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43410 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43411 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43412 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43413 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43416 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43419 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43420 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43421 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43424 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43425 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43428 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43429 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43432 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43436 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43437 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43441 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43443 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43445 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43451 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43452 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43455 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43456 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43457 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43459 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43463 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43464 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43466 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43467 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43468 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43469 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43471 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43472 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43473 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43474 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43475 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43483 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43484 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43488 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43492 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43496 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43502 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45834 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45835 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45836 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45838 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45841 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45842 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45843 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45844 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45845 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45846 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45847 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45851 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45855 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45857 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45862 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45868 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45870 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45871 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45872 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45873 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45877 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45880 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45891 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45895 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45897 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45901 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45904 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45905 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45911 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45913 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45914 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45915 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45917 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45919 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45920 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45923 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45941 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45943 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45944 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45947 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45948 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45954 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45960 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45961 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45962 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45963 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45964 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45965 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45968 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45969 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45973 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45974 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45976 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45978 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45981 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45982 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45983 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45985 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45986 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45987 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45993 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45997 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45999 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46002 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46003 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46005 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46007 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46009 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46012 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46014 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46016 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46018 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46019 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46021 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46023 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46026 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46027 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46032 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46037 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46038 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46040 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46041 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46044 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46046 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46049 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46050 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46051 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46059 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46061 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46063 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46064 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46066 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46068 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46070 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46071 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46078 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46079 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46082 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46083 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46086 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46088 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46089 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46092 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46094 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46101 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46102 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46103 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46106 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46107 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46111 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46115 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46126 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46127 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46130 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46131 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46136 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46137 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46138 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46144 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46146 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46148 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46151 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46153 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46157 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46158 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46160 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46161 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46167 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46168 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46169 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46170 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46171 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46172 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46178 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46179 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46184 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46186 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46190 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46193 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46196 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46200 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46201 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46207 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46211 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46214 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46220 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46225 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46226 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46229 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46231 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46233 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46235 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46236 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46247 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46260 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46289 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46302 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46315 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46321 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46322 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-13693 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-12928 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-12929 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31448 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43071 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43465 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46147 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46245 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46249 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46252 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46253 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46254 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46255 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46261 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46280 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46291 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46292 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46299 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46307 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46312 | MEDIUM4.67 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-52615 | MEDIUM4.5 | libavahi-client3 0.8-13ubuntu6.2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-52616 | MEDIUM4.5 | libavahi-client3 0.8-13ubuntu6.2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-52615 | MEDIUM4.5 | libavahi-common-data 0.8-13ubuntu6.2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-52616 | MEDIUM4.5 | libavahi-common-data 0.8-13ubuntu6.2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-52615 | MEDIUM4.5 | libavahi-common3 0.8-13ubuntu6.2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-52616 | MEDIUM4.5 | libavahi-common3 0.8-13ubuntu6.2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-bin 2.39-0ubuntu8.7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-dev-bin 2.39-0ubuntu8.7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6 2.39-0ubuntu8.7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6-dev 2.39-0ubuntu8.7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM4.5 | libgnutls30t64 3.8.3-1.1ubuntu3.5 fixed in 3.8.3-1.1ubuntu3.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-22693 | MEDIUM4.5 | libharfbuzz0b 8.3.0-2build2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23457 | MEDIUM4.5 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40217 | MEDIUM4.42 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40338 | MEDIUM4.42 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40344 | MEDIUM4.42 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.39.3-9ubuntu6.5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | MEDIUM4 | libelf1t64 0.190-1.1ubuntu0.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libfdisk1 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-2024-39293 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-42107 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56552 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56788 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57857 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21984 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37906 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38242 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38440 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38717 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39754 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39884 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40139 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68239 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68296 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68745 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71074 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71274 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23004 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23118 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23169 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23181 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23207 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23302 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23348 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23440 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23441 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23452 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23463 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23469 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31389 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31393 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31466 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31523 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31697 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31728 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31751 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43047 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43053 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43163 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43275 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43342 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43383 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43415 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43430 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43439 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43448 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45949 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46159 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46187 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46194 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46272 | MEDIUM4 | linux-libc-dev 6.8.0-124.124 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-15213 | LOW3.91 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4010 | LOW3.91 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-68360 | LOW3.82 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-17977 | LOW3.74 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-68768 | LOW3.74 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23458 | LOW3.74 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2020-14304 | LOW3.74 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-41848 | LOW3.57 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc-bin 2.39-0ubuntu8.7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc-dev-bin 2.39-0ubuntu8.7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc6 2.39-0ubuntu8.7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc6-dev 2.39-0ubuntu8.7 No fix yet | 0.2% 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-2026-3832 | LOW3.15 | libgnutls30t64 3.8.3-1.1ubuntu3.5 fixed in 3.8.3-1.1ubuntu3.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5419 | LOW3.15 | libgnutls30t64 3.8.3-1.1ubuntu3.5 fixed in 3.8.3-1.1ubuntu3.6 | 0.5% 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-42010 | LOW3 | libgnutls30t64 3.8.3-1.1ubuntu3.5 fixed in 3.8.3-1.1ubuntu3.6 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2020-35501 | LOW2.89 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35195 | LOW2.86 | python3-pip 24.0+dfsg-1ubuntu1.3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-45582 | LOW2.86 | tar 1.35+dfsg-3build1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2013-7445 | LOW2.81 | linux-libc-dev 6.8.0-124.124 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19378 | LOW2.81 | linux-libc-dev 6.8.0-124.124 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19814 | LOW2.81 | linux-libc-dev 6.8.0-124.124 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-2021-45261 | LOW2.8 | patch 2.7.6-7build3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-24049 | LOW2.8 | python3-wheel 0.42.0-2 No fix yet | 0.3% 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-2026-40228 | LOW2.8 | libpam-systemd 255.4-1ubuntu8.16 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.8 | libpython3.12-dev 3.12.3-1ubuntu0.13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | libpython3.12-dev 3.12.3-1ubuntu0.13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.8 | libpython3.12-minimal 3.12.3-1ubuntu0.13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | libpython3.12-minimal 3.12.3-1ubuntu0.13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.8 | libpython3.12-stdlib 3.12.3-1ubuntu0.13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | libpython3.12-stdlib 3.12.3-1ubuntu0.13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.8 | libpython3.12t64 3.12.3-1ubuntu0.13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | libpython3.12t64 3.12.3-1ubuntu0.13 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 | libsystemd-shared 255.4-1ubuntu8.16 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 255.4-1ubuntu8.16 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 255.4-1ubuntu8.16 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31668 | LOW2.8 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.8 | python3.12 3.12.3-1ubuntu0.13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | python3.12 3.12.3-1ubuntu0.13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.8 | python3.12-dev 3.12.3-1ubuntu0.13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | python3.12-dev 3.12.3-1ubuntu0.13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.8 | python3.12-minimal 3.12.3-1ubuntu0.13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | python3.12-minimal 3.12.3-1ubuntu0.13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | systemd-dev 255.4-1ubuntu8.16 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-33845 | LOW2.78 | libgnutls30t64 3.8.3-1.1ubuntu3.5 fixed in 3.8.3-1.1ubuntu3.6 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-0400 | LOW2.7 | linux-libc-dev 6.8.0-124.124 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-20426 | LOW2.7 | linux-libc-dev 6.8.0-124.124 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6952 | LOW2.7 | patch 2.7.6-7build3 No fix yet | 8.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-43037 | LOW2.69 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-23395 | LOW2.69 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5260 | LOW2.51 | libgnutls30t64 3.8.3-1.1ubuntu3.5 fixed in 3.8.3-1.1ubuntu3.6 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-31788 | LOW2.51 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2019-15794 | LOW2.41 | linux-libc-dev 6.8.0-124.124 No fix yet | 1.2% Low-Moderate Risk | 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-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-2020-14356 | LOW2.39 | linux-libc-dev 6.8.0-124.124 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-3238 | LOW2.39 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-50090 | LOW2.39 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2017-13165 | LOW2.39 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-12930 | LOW2.39 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2018-12931 | LOW2.39 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-26934 | LOW2.39 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% 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-66418 | LOW2.29 | python3-pip 24.0+dfsg-1ubuntu1.3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-66471 | LOW2.29 | python3-pip 24.0+dfsg-1ubuntu1.3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-21441 | LOW2.29 | python3-pip 24.0+dfsg-1ubuntu1.3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2021-31879 | LOW2.2 | wget 1.21.4-1ubuntu4.1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-1703 | LOW1.99 | python3-pip 24.0+dfsg-1ubuntu1.3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| 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-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-2026-40228 | LOW1.68 | systemd-sysv 255.4-1ubuntu8.16 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-2026-40228 | NONE0 | systemd 255.4-1ubuntu8.16 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43011 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-54518 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31405 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31478 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31657 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31659 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31705 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-54105 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54187 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40003 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40012 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40073 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40097 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40098 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40150 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40208 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40222 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40274 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40332 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40335 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40354 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40356 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-54505 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-62626 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68174 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68175 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68196 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68230 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68318 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68338 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68376 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68781 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71304 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23245 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23281 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23364 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23372 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23393 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31396 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31409 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31413 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31417 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31432 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31433 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31476 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31477 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31494 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31563 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31584 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31587 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31597 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31598 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31602 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31611 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31612 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31622 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31626 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31627 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31629 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31656 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31683 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31695 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31706 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31707 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31711 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31712 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31716 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31761 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31768 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31769 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31780 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43075 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43076 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43117 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43184 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43203 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43206 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43207 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43212 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43222 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43232 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43236 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43237 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43245 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43249 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43256 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43258 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43263 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43274 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43283 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43291 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43324 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43336 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43368 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43370 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43373 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43377 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43384 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43476 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43480 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43485 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43490 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43495 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43497 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43499 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45839 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45848 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45849 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45850 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45864 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45865 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45866 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45867 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45869 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45875 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45878 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45879 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45881 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45882 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45883 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45884 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45885 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45890 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45893 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45902 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45916 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45921 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45924 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45928 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45930 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45935 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45936 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45938 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45958 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46006 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46011 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46031 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46058 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46062 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46072 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46073 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46075 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46077 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46080 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46091 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46098 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46108 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46110 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46112 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46118 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46122 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46124 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46128 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46129 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46142 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46143 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46164 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46177 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46197 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46198 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46199 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46204 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46205 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46206 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46208 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46212 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46218 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46230 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46232 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46238 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46303 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46314 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46328 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46250 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46265 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46270 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46282 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46285 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46286 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46287 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46293 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46296 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46301 | NONE0 | linux-libc-dev 6.8.0-124.124 No fix yet | 0.2% Theoretical Threat | Not Applicable |