Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. The container exposes 1808 vulnerabilities, including 145 with severity 6.0 or higher, and the most severe (6.88) are XSS flaws in golang.org/x/net (CVE-2026-25681, CVE-2026-27136) and kernel use-after-free issues such as CVE-2026-31532 that require local access. In practice, the XSS issues only matter if the application parses and renders untrusted HTML, and the kernel flaws need a local attacker with the ability to trigger specific operations; the post-exploitation findings are all low severity. Limiting local access and avoiding exposure of untrusted input to HTML rendering can substantially reduce the real-world risk, but given the large attack surface, caution is warranted.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-25681 | MEDIUM6.88 | golang.org/x/net v0.40.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27136 | MEDIUM6.88 | golang.org/x/net v0.40.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-15794 | MEDIUM6.7 | linux-libc-dev 7.0.0-15.15 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31532 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31709 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43499 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-46274 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46323 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-22.22 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53148 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53262 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53359 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-3238 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50090 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50240 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-0030 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-26242 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31578 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31581 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31582 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31696 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45839 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45989 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45995 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45996 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45998 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-22.22 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46001 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46004 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46045 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46047 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46068 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46069 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46075 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46084 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46097 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46121 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46122 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46136 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46162 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46163 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46180 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46183 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46189 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46213 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46215 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46219 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46234 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46241 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46243 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52943 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52962 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52969 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52992 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53004 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53109 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53136 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53137 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53143 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53286 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53294 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53296 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53362 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53366 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63794 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63804 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64600 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-13165 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-12930 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-12931 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-26934 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-33053 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31576 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31580 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31583 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31686 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31702 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31715 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45837 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46279 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46281 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46285 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46294 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46301 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46308 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53059 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53067 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53089 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53097 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53098 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53112 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53115 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53116 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53117 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53118 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53119 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53120 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53129 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53156 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53157 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53195 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53233 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53234 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53272 | MEDIUM6.63 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-1193 | MEDIUM6.5 | linux-libc-dev 7.0.0-15.15 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-43501 | MEDIUM6.38 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-46195 | MEDIUM6.38 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-53071 | MEDIUM6.38 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53266 | MEDIUM6.38 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-25836 | MEDIUM6.38 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM6.38 | golang.org/x/net v0.40.0 fixed in 0.53.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | libssl3t64 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-14899 | MEDIUM6.29 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | openssl-provider-legacy 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31607 | MEDIUM6.21 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46244 | MEDIUM6.21 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46135 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31613 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-50551 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31614 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45994 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46020 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46022 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46033 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46053 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46056 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46064 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46067 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46094 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46120 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46130 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46140 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46150 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46155 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46191 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46203 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46209 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52968 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53138 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53149 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53179 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53303 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53309 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53330 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53346 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46293 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53255 | MEDIUM6.03 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46043 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52989 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52993 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53002 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53260 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-54518 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31586 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31694 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31703 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43493 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-43494 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-22.22 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43503 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-22.22 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46039 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46119 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46185 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46275 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46319 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52924 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53006 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53031 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53036 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53054 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53072 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53145 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53153 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53175 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53182 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53185 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53192 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53193 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53212 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53224 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53235 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53239 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53250 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53254 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53256 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53259 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53264 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53270 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53275 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53276 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53277 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-3864 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-1247 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-2961 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46015 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46052 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46054 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46076 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46090 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46099 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46114 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46116 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46117 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46123 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46133 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-46145 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46149 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46152 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46166 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46173 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46174 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46176 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46181 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46227 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46306 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46309 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46316 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46317 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46324 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52912 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52917 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52918 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52920 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52933 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52935 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52942 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52947 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52950 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52951 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52952 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52953 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52956 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52957 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52971 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52973 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52976 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52986 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-52987 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52991 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52998 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53000 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53005 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53009 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53011 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53016 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53026 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53049 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53075 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53091 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53131 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53132 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53133 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53223 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53228 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53242 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53244 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53246 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53268 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53290 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53322 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53341 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53354 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53355 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53357 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53360 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53361 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53381 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53384 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53388 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53391 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53392 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53395 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53396 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53397 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53398 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53399 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63795 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63800 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63801 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63802 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63807 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63808 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63809 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63823 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63824 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63826 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63829 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63830 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63831 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63866 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63875 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63883 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63884 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63886 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63887 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63888 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63889 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63891 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63894 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63896 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63898 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63899 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63901 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63910 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63912 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63913 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63914 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63916 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63917 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63918 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63919 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63920 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63921 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63922 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63923 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63924 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63925 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63928 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63938 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63939 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63940 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63941 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63944 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63945 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63946 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63947 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63950 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63952 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63956 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63957 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63958 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63962 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63970 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63971 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63975 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63978 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63979 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63981 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63984 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63987 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63992 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63993 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63994 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63996 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64000 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64001 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64002 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64007 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64008 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64009 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64011 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64015 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64017 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64018 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64024 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64025 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64026 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64027 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64029 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64030 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64032 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64034 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64035 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64037 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64041 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64042 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64047 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64048 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64051 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64053 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64054 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64061 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64068 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64069 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64071 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64080 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64098 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64099 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64102 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64109 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64111 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64113 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64114 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64115 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64117 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64119 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64122 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64132 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64136 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64137 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64160 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64174 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64189 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64191 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64192 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64208 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64216 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64217 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64247 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64251 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64255 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64265 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64266 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64267 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64268 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-64271 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64276 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64277 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64280 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64283 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64286 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64287 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64296 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64298 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64300 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64303 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-64304 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64305 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64306 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64312 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64317 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64319 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64320 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-64321 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64322 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64323 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64324 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64340 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64341 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64342 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64354 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64355 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64364 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64366 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64372 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64375 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64377 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64378 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64379 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64380 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64382 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64383 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64384 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64385 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64387 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64401 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64402 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64410 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64414 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64418 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64422 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64434 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64439 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64448 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64456 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64470 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64471 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64473 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64475 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64481 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64483 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64490 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64508 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64515 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64516 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64520 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64523 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64525 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64527 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64530 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64531 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64534 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64539 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64543 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64548 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64551 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64552 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64554 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-45885 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53053 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53062 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53078 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53110 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53189 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53200 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53202 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53203 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53209 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53230 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53253 | MEDIUM5.95 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt20 1.12.0-2ubuntu0.1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.9 | libssl3t64 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3714 | MEDIUM5.9 | linux-libc-dev 7.0.0-15.15 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-1121 | MEDIUM5.9 | linux-libc-dev 7.0.0-15.15 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.9 | openssl-provider-legacy 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-53196 | MEDIUM5.78 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46125 | MEDIUM5.78 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46331 | MEDIUM5.7 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-6238 | MEDIUM5.7 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53094 | MEDIUM5.7 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31589 | MEDIUM5.61 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45991 | MEDIUM5.61 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53267 | MEDIUM5.61 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-dev-bin 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-gconv-modules-extra 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6-dev 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53176 | MEDIUM5.52 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2015-8553 | MEDIUM5.52 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31588 | MEDIUM5.52 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64535 | MEDIUM5.52 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-0564 | MEDIUM5.52 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-25680 | MEDIUM5.52 | golang.org/x/net v0.40.0 fixed in 0.55.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libbinutils 2.46-3ubuntu2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf-nobfd0 2.46-3ubuntu2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf0 2.46-3ubuntu2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libgprofng0 2.46-3ubuntu2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libsframe3 2.46-3ubuntu2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-52910 | MEDIUM5.44 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53033 | MEDIUM5.44 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53081 | MEDIUM5.44 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53085 | MEDIUM5.44 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53090 | MEDIUM5.44 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-44034 | MEDIUM5.44 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53092 | MEDIUM5.44 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM5.35 | libssl3t64 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | libssl3t64 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM5.35 | openssl-provider-legacy 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | openssl-provider-legacy 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | libp11-kit0 0.26.2-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40190 | MEDIUM5.18 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31700 | MEDIUM5.18 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31708 | MEDIUM5.18 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42502 | MEDIUM5.18 | golang.org/x/net v0.40.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-dev-bin 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-gconv-modules-extra 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6-dev 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.02 | libssl3t64 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | libssl3t64 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | libssl3t64 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.02 | openssl-provider-legacy 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | openssl-provider-legacy 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | openssl-provider-legacy 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | libssl3t64 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | openssl-provider-legacy 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-52908 | MEDIUM4.93 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46065 | MEDIUM4.93 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46113 | MEDIUM4.93 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52923 | MEDIUM4.93 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46024 | MEDIUM4.84 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-0537 | MEDIUM4.7 | linux-libc-dev 7.0.0-15.15 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | libssl3t64 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45988 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43502 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46273 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46304 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46320 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52909 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52958 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53050 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53086 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53095 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53151 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53159 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53183 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53269 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2015-7837 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-8660 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-0480 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-4543 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-48846 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48929 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49940 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50230 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50232 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50332 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50380 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-0160 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31082 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-52879 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53642 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-54190 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35895 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35995 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21988 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31574 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31575 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31577 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31579 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31585 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31590 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31591 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31592 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31593 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31594 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31595 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31596 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31599 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31600 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31601 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31603 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31604 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31605 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31606 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31610 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31615 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31616 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31617 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31618 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31619 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31621 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31623 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31624 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31625 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31628 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31698 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31699 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31701 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31704 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31710 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31713 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31714 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31719 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43058 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43072 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43073 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43348 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43349 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43350 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43491 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43492 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43496 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45834 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45835 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45836 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45840 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45842 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45843 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45845 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45846 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45986 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45987 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45990 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45997 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45999 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46000 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-22.22 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46002 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46003 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46005 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46007 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46009 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46010 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46012 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46013 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46014 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46016 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46018 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46019 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46021 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46023 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46026 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46027 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46028 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46030 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46032 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46034 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46035 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46037 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46038 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46040 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46041 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46042 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46044 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46046 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46049 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46050 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46051 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46059 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46060 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46061 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46063 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46066 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46070 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46071 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46072 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46073 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46074 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46077 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46078 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46079 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46080 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46082 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46083 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46086 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46087 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46088 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46089 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46091 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46092 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46093 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46095 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46096 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46098 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46101 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46102 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46103 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46104 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46105 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46106 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46107 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46108 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46109 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46111 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46115 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46118 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46126 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46127 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46128 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46131 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46132 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46134 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46137 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46138 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46139 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46141 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46142 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46143 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46144 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46146 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46148 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46151 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46153 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46156 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46157 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46158 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46160 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46161 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46165 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46167 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46168 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46169 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46170 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46171 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46172 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46178 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46179 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46182 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46184 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46186 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46188 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46190 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46192 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46193 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46196 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46200 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46201 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46202 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46207 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46211 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46214 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46216 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46220 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46221 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46222 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46223 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46224 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46225 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46226 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46228 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46229 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46231 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46233 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46235 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46236 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46239 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46289 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46290 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46302 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46303 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46305 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46314 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46315 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46321 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46322 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52905 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52913 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52915 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52916 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52921 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52925 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52926 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52927 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52928 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52929 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52930 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52936 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52937 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52938 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52939 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52940 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52941 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52944 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52948 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52949 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52954 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52960 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52961 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52963 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52964 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52965 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52967 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52970 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52974 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52975 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52977 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52978 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52979 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52980 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52981 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52984 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52985 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52988 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52990 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52994 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52995 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52996 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52997 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52999 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53001 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53003 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53007 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53012 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53013 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53014 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53015 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53017 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53018 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53019 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53021 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53022 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53023 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53027 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53028 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53029 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53030 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53032 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53034 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53037 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53039 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53051 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53056 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53064 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53066 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53069 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53074 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53076 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53077 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53079 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53080 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53083 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53088 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53101 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53103 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53105 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53107 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53114 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53122 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53127 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53128 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53134 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53139 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53140 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53141 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53144 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53150 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53155 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53163 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53164 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53167 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53168 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53169 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53180 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53181 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53184 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53187 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53190 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53191 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53197 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53199 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53208 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53210 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53211 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53214 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53218 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53219 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53220 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53221 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53227 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53231 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53241 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53243 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53245 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53251 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53252 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53257 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53263 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53271 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53274 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53278 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53279 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53280 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53281 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53282 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53283 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53284 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53285 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53287 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53288 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53289 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53291 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53292 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53293 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53295 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53297 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53298 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53299 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53301 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53302 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53304 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53305 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53306 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53307 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53308 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53310 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53311 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53312 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53313 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53314 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53315 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53316 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53317 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53318 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53319 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53320 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53321 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53323 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53324 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53325 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53326 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53327 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53328 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53331 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53332 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53333 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53334 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53335 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53336 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53337 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53338 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53339 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53340 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53342 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53343 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53344 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53345 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53347 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53348 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53349 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53350 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53351 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53353 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53358 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53364 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53365 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53367 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53369 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53370 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53371 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53372 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53373 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53376 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53377 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53378 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53379 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53382 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53385 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53393 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53394 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53400 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53402 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53403 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63798 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63803 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63810 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63821 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63822 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63832 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63837 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63838 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63840 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63841 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63842 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63843 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63844 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63845 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63849 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63850 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63851 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63852 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63853 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63858 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63860 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63863 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63864 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63865 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63867 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63868 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63869 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63870 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63871 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63872 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63876 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63877 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63878 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63880 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63890 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63892 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63893 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63897 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63900 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63902 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63903 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63904 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63906 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63926 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63927 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63929 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63935 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63937 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63942 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63943 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63948 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63955 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63961 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63963 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63964 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63968 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63969 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63973 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63974 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63976 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63977 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63980 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63982 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63983 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63985 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63986 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63988 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63989 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63990 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63991 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63995 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63997 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63998 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63999 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64003 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64004 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64005 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64006 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64012 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64013 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64014 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64019 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64020 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64021 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64036 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64038 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64039 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64040 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64046 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64052 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64057 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64058 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64059 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64060 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64062 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64063 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64064 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64065 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64066 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64067 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64070 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64072 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64073 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64076 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64077 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64078 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64079 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64081 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64103 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64105 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64106 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64107 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64110 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64112 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64116 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64118 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64120 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64121 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64123 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64125 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-64126 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64127 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64128 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64130 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64131 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64133 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64134 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64144 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64145 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64146 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64149 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64150 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64151 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64152 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64153 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64155 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64156 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64157 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64158 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64159 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64162 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64163 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64170 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64171 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64172 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64173 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64175 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64176 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64177 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64178 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64179 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64180 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64181 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64182 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64183 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64184 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64185 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64186 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64187 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64190 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64205 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64206 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64210 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64212 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64213 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64214 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64220 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64222 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64223 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64224 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64225 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64227 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64228 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64229 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64231 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64232 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64235 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64237 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64239 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64243 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64244 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64245 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64253 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64254 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64256 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64275 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64279 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64282 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64284 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64288 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64289 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64290 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64291 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64292 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64293 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64294 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64295 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64297 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64299 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64301 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64307 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64308 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64309 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64310 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64313 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64315 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64316 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64325 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64326 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64327 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64328 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64329 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64330 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64332 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64333 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64334 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64335 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64336 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64338 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64343 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64344 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64346 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64347 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64351 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64352 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64356 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64357 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64360 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64362 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64363 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64365 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64368 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64369 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64370 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64373 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64374 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64376 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64381 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64388 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64403 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64404 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64405 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64406 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64407 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64408 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64409 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64411 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64412 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64413 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64415 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64416 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64417 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64419 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64423 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64424 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64426 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64428 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64430 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64433 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64435 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64436 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64451 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64452 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64453 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64454 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64455 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64458 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64460 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64463 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64464 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64465 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64472 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64474 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64476 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64477 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64478 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64479 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64480 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64482 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64485 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64486 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64487 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64488 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64489 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64491 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64496 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64507 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64510 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64511 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64512 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64513 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64514 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64517 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64519 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64522 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64524 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64526 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64529 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64537 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64540 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64541 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64542 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64544 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64545 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64546 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64547 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64553 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64555 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-13693 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-12928 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-12929 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-22077 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31609 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43071 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45838 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45841 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45844 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46147 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46276 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46278 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46280 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46282 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46283 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46284 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46286 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46287 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46291 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46292 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46295 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46296 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46297 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46299 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46307 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46310 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46312 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46313 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46318 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52904 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52982 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53035 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53038 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53042 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53044 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53047 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53048 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53052 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53058 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53060 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53061 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53063 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53065 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53070 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53073 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53082 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53084 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53093 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53096 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53099 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53100 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53102 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53104 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53106 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53111 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53113 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53121 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53123 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53124 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53125 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53126 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53135 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53142 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53146 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53147 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53152 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53154 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53158 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53162 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53177 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53188 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53204 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53205 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53206 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53207 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53213 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53222 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53225 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53226 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53229 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53232 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53236 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53237 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53238 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53249 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53258 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53261 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53265 | MEDIUM4.67 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | openssl-provider-legacy 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g 1:1.3.dfsg+really1.3.1-1ubuntu3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42506 | MEDIUM4.59 | golang.org/x/net v0.40.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid1 2.41.3-3ubuntu2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-bin 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-dev-bin 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-gconv-modules-extra 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6-dev 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount1 2.41.3-3ubuntu2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libsmartcols1 2.41.3-3ubuntu2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | libssl3t64 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | libssl3t64 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.41.3-3ubuntu2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53194 | MEDIUM4.5 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64538 | MEDIUM4.5 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | openssl-provider-legacy 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | openssl-provider-legacy 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-47911 | MEDIUM4.5 | golang.org/x/net v0.40.0 fixed in 0.45.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58190 | MEDIUM4.5 | golang.org/x/net v0.40.0 fixed in 0.45.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-dev-bin 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-dev-bin 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-gconv-modules-extra 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-gconv-modules-extra 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6-dev 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6-dev 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam-modules 1.7.0-5ubuntu3 fixed in 1.7.0-5ubuntu3.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam-modules-bin 1.7.0-5ubuntu3 fixed in 1.7.0-5ubuntu3.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam-runtime 1.7.0-5ubuntu3 fixed in 1.7.0-5ubuntu3.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam0g 1.7.0-5ubuntu3 fixed in 1.7.0-5ubuntu3.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.41.3-3ubuntu2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount1 2.41.3-3ubuntu2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols1 2.41.3-3ubuntu2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.41.3-3ubuntu2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52955 | MEDIUM4 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31697 | MEDIUM4 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46008 | MEDIUM4 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46025 | MEDIUM4 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46159 | MEDIUM4 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46187 | MEDIUM4 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46194 | MEDIUM4 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53008 | MEDIUM4 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53108 | MEDIUM4 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53352 | MEDIUM4 | linux-libc-dev 7.0.0-15.15 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46298 | MEDIUM4 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31620 | LOW3.91 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-15213 | LOW3.91 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4010 | LOW3.91 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-41992 | LOW3.82 | gzip 1.14-1~exp2ubuntu1 fixed in 1.14-1~exp2ubuntu1.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW3.77 | openssl 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2018-17977 | LOW3.74 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-14304 | LOW3.74 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43284 | LOW3.65 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-22.22 | 93.2% Actively Exploited | Post-Exploit |
| CVE-2026-43500 | LOW3.65 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-22.22 | 92.9% Actively Exploited | Post-Exploit |
| CVE-2022-41848 | LOW3.57 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42764 | LOW3.54 | openssl 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils 2.46-3ubuntu2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-common 2.46-3ubuntu2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-x86-64-linux-gnu 2.46-3ubuntu2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34181 | LOW3.21 | openssl 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42768 | LOW3.21 | openssl 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-45446 | LOW3.15 | libssl3t64 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | openssl-provider-legacy 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | LOW3.01 | openssl 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW3.01 | openssl 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.01 | openssl 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | libperl5.40 5.40.1-7build1 fixed in 5.40.1-7ubuntu0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl 5.40.1-7build1 fixed in 5.40.1-7ubuntu0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-base 5.40.1-7build1 fixed in 5.40.1-7ubuntu0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-modules-5.40 5.40.1-7build1 fixed in 5.40.1-7ubuntu0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34180 | LOW3 | openssl 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | libssl3t64 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl-provider-legacy 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2020-35501 | LOW2.89 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-45582 | LOW2.86 | tar 1.35+dfsg-4 fixed in 1.35+dfsg-4ubuntu0.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-46300 | LOW2.81 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-22.22 | 7.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-46333 | LOW2.81 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-22.22 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2013-7445 | LOW2.81 | linux-libc-dev 7.0.0-15.15 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19378 | LOW2.81 | linux-libc-dev 7.0.0-15.15 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19814 | LOW2.81 | linux-libc-dev 7.0.0-15.15 No fix yet | 3.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-7383 | LOW2.8 | openssl 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2019-20633 | LOW2.8 | patch 2.8-2build1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2021-45261 | LOW2.8 | patch 2.8-2build1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.35+dfsg-4 fixed in 1.35+dfsg-4ubuntu0.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-40228 | LOW2.8 | libsystemd0 259.5-0ubuntu3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 259.5-0ubuntu3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46057 | LOW2.8 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | LOW2.78 | libperl5.40 5.40.1-7build1 fixed in 5.40.1-7ubuntu0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | LOW2.78 | libssl3t64 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | LOW2.78 | openssl 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | LOW2.78 | openssl-provider-legacy 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | LOW2.78 | perl 5.40.1-7build1 fixed in 5.40.1-7ubuntu0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | LOW2.78 | perl-base 5.40.1-7build1 fixed in 5.40.1-7ubuntu0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | LOW2.78 | perl-modules-5.40 5.40.1-7build1 fixed in 5.40.1-7ubuntu0.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34183 | LOW2.7 | libssl3t64 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-0400 | LOW2.7 | linux-libc-dev 7.0.0-15.15 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-20426 | LOW2.7 | linux-libc-dev 7.0.0-15.15 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34183 | LOW2.7 | openssl 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34183 | LOW2.7 | openssl-provider-legacy 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6952 | LOW2.7 | patch 2.8-2build1 No fix yet | 8.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.41.3-3ubuntu2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | login 1:4.16.0-2+really2.41.3-3ubuntu2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.41.3-3ubuntu2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42766 | LOW2.7 | openssl 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-42767 | LOW2.7 | openssl 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.41.3-3ubuntu2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-63797 | LOW2.57 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46242 | LOW2.52 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-39821 | LOW2.51 | golang.org/x/net v0.40.0 fixed in 0.55.0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.41.3-3ubuntu2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.14-1~exp2ubuntu1 fixed in 1.14-1~exp2ubuntu1.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | login 1:4.16.0-2+really2.41.3-3ubuntu2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.41.3-3ubuntu2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.41.3-3ubuntu2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45446 | LOW1.89 | openssl 3.5.5-1ubuntu3 fixed in 3.5.5-1ubuntu3.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.17.4-2ubuntu3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-39822 | NONE0 | stdlib v1.26.2 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-27145 | NONE0 | stdlib v1.26.2 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-33811 | NONE0 | stdlib v1.26.2 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-33814 | NONE0 | stdlib v1.26.2 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39820 | NONE0 | stdlib v1.26.2 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39836 | NONE0 | stdlib v1.26.2 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42499 | NONE0 | stdlib v1.26.2 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42504 | NONE0 | stdlib v1.26.2 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-39825 | NONE0 | stdlib v1.26.2 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-35373 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-39823 | NONE0 | stdlib v1.26.2 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39826 | NONE0 | stdlib v1.26.2 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42505 | NONE0 | stdlib v1.26.2 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42507 | NONE0 | stdlib v1.26.2 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-56433 | NONE0 | login.defs 1:4.17.4-2ubuntu3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-11822 | NONE0 | libsqlite3-0 3.46.1-9 fixed in 3.46.1-9ubuntu0.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-0 3.46.1-9 fixed in 3.46.1-9ubuntu0.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50812 | NONE0 | libsqlite3-0 3.46.1-9 fixed in 3.46.1-9ubuntu0.2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50813 | NONE0 | libsqlite3-0 3.46.1-9 fixed in 3.46.1-9ubuntu0.2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31608 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53215 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31584 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31627 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31705 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31706 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31712 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31716 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31718 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43490 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46277 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46311 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47333 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-22.22 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52911 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52914 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53010 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53040 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53043 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53046 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53055 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53068 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53130 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53170 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53171 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53172 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53173 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53186 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53198 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53240 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-54105 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54187 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-54505 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31597 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31598 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31602 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31611 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31612 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31622 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31626 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31629 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31707 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31711 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31717 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43495 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43498 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46006 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46011 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46029 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46031 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46036 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46055 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46058 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46062 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46081 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46085 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46100 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46110 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46112 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46124 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46129 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46154 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46164 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46177 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46197 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46198 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46199 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46204 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46205 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46206 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46208 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46210 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46212 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46218 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46230 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46232 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46238 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46240 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47326 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-22.22 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47327 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-22.22 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47328 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-22.22 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47332 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-22.22 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47334 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-22.22 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47337 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-22.22 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52906 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52907 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52919 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52922 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52931 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52932 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52934 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52959 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52983 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53020 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53041 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53045 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53165 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53174 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53201 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53300 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53329 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53356 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53363 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53368 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53374 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53375 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53380 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53383 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-53386 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53387 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53389 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53390 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53401 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63793 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63796 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63799 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63805 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63806 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63811 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63812 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63813 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63814 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63815 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63816 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63817 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63818 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63819 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63820 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63825 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63827 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63828 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63833 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63834 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63835 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63836 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63839 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63846 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63847 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63848 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63854 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63855 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63856 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63857 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63859 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63861 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63862 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63873 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63874 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63879 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63881 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63882 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63895 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63905 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63907 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63908 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63909 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63911 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63915 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63930 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63931 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63932 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63933 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63934 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63936 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63949 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63951 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63953 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63954 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63959 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63960 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63965 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63966 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63967 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63972 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64010 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64022 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64023 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64031 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64033 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64043 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64044 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64045 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64049 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64050 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64055 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64056 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64074 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64075 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64082 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64083 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64084 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64085 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64086 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64087 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64088 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64089 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64090 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64091 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64093 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64094 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64095 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64096 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64097 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64100 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64101 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64104 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64108 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64124 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64129 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64135 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64138 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64139 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64140 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64141 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64142 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64143 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64147 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64148 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64154 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64161 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64164 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64165 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64166 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64167 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64168 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64169 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64188 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64207 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64209 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64211 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64215 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64218 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64219 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64221 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64226 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64230 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64233 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64234 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64236 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64238 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64240 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64241 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64242 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64246 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64249 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64258 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64259 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64260 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64261 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64262 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64263 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64264 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64269 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64270 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64272 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64273 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64274 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64278 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64285 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64302 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64314 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64318 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64331 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64337 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64339 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64345 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64348 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64349 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64350 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64353 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64358 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64359 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64361 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64367 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64371 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64386 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64389 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64390 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64391 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64392 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64393 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64394 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64395 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64396 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64397 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64398 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64399 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64400 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64420 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64421 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64425 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64429 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64432 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64437 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64438 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64440 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64441 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64442 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64443 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64444 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64445 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64446 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64447 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64449 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64450 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64457 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64459 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64461 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64462 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64466 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64467 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64468 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64469 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64484 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64492 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64493 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64494 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64495 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64497 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64499 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64500 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64501 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64502 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64503 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64504 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64505 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64509 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64518 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64521 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64528 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64532 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64533 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64536 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64549 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64550 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-20585 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31587 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43497 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46288 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46332 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-27.27 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-47329 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-22.22 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47330 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-22.22 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53057 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53087 | NONE0 | linux-libc-dev 7.0.0-15.15 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53160 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53161 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53216 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53217 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53247 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53248 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53273 | NONE0 | linux-libc-dev 7.0.0-15.15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35341 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-35344 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35345 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35348 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35350 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35351 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35352 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35354 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35357 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35359 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35360 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35363 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-35364 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35367 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35368 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35370 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35371 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35374 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35377 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46600 | NONE0 | golang.org/x/net v0.40.0 fixed in 0.56.0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39824 | NONE0 | golang.org/x/sys v0.33.0 fixed in 0.44.0 | 0.1% Theoretical Threat | Not Applicable |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.