Last scanned:
This image is safe for production use. Although the scan identifies 36 exposed and 54 post-exploit findings, all are low severity (maximum 5.5 and 3.3 respectively), meaning they do not present a practical risk to production workloads. The image is from the trusted NVIDIA publisher, pinned by digest, and carries a threat score of 0.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| 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-13757 | MEDIUM5.27 | libp11-kit0 0.26.2-2 No fix yet | 0.1% 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-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-3184 | MEDIUM4.5 | libuuid1 2.41.3-3ubuntu2 No fix yet | 0.4% 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-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-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-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-35373 | LOW2.8 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.35+dfsg-4ubuntu0.2 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-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 | mount 2.41.3-3ubuntu2 No fix yet | 0.4% 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-39821 | LOW2.51 | golang.org/x/net v0.40.0 fixed in 0.55.0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-25681 | LOW2.48 | golang.org/x/net v0.40.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27136 | LOW2.48 | golang.org/x/net v0.40.0 fixed in 0.55.0 | 0.2% 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-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-33814 | LOW2.29 | golang.org/x/net v0.40.0 fixed in 0.53.0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2024-2236 | LOW2.12 | libgcrypt20 1.12.0-2ubuntu1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-6238 | LOW1.99 | libc-bin 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW1.99 | libc-dev-bin 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW1.99 | libc-gconv-modules-extra 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW1.99 | libc6 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW1.99 | libc6-dev 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-25680 | LOW1.99 | golang.org/x/net v0.40.0 fixed in 0.55.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42502 | LOW1.87 | golang.org/x/net v0.40.0 fixed in 0.55.0 | 0.2% 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-5435 | LOW1.81 | libc-bin 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5435 | LOW1.81 | libc-dev-bin 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5435 | LOW1.81 | libc-gconv-modules-extra 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5435 | LOW1.81 | libc6 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5435 | LOW1.81 | libc6-dev 2.43-2ubuntu2 fixed in 2.43-2ubuntu2.3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42506 | LOW1.65 | golang.org/x/net v0.40.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-47911 | LOW1.62 | golang.org/x/net v0.40.0 fixed in 0.45.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-58190 | LOW1.62 | golang.org/x/net v0.40.0 fixed in 0.45.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-63797 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46274 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53148 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53262 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53359 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2013-7445 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2022-3238 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50090 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50240 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-0030 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-26242 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45839 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46121 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46122 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46136 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46162 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46163 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46180 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46183 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46189 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46213 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46215 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46219 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46234 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46241 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52943 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52962 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52969 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52992 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53004 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53109 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53136 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53137 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53143 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53286 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53294 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53296 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53362 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53366 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63794 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63804 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64600 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2017-13165 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2018-12930 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12931 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19378 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-19814 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-26934 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-33053 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45837 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46294 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46301 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46308 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53059 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53067 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53089 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53097 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53098 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53112 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53115 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53116 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53117 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53118 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53119 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53120 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53129 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53156 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53157 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53195 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53233 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53234 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53272 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-39822 | NONE0 | stdlib v1.26.3 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53071 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53266 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0400 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-25836 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-20426 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2026-27145 | NONE0 | stdlib v1.26.3 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42504 | NONE0 | stdlib v1.26.3 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-14899 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-50551 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46120 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46130 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46140 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46150 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46191 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46203 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46209 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52968 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53138 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53149 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53179 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53303 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53309 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53330 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53346 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46293 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53255 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52989 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52993 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53002 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53260 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-54518 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46242 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-46275 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46319 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52924 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53006 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53031 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53036 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53054 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53072 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53145 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53153 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53175 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53182 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53185 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53192 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53193 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53212 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53224 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53235 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53239 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53250 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53254 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53256 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53259 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53264 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53270 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53275 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53276 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53277 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2021-3864 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2022-1247 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2961 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46114 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46116 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46117 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46123 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46133 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46145 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46149 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46152 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46166 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46173 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46174 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46176 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46181 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46227 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46306 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46309 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46317 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52912 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52917 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52918 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52920 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52935 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52942 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52947 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52950 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52951 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52952 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52953 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52956 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52957 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52971 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52973 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52976 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52986 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-52987 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52991 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52998 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53000 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53005 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53009 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53011 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53016 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53026 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53049 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53075 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53091 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53131 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53132 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53133 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53223 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53228 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53242 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53244 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53246 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53268 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53290 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53322 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53341 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53354 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53355 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53357 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53360 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53361 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53381 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53384 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53388 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53391 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53392 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53395 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53396 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53397 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53398 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53399 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63795 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63800 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63801 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63802 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63807 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63808 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63809 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63823 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63824 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63826 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63829 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63830 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63831 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63866 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63875 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63883 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63884 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63886 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63887 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63888 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63889 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63891 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63894 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63896 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63898 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63899 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63901 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63910 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63912 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63913 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63914 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63916 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63917 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63918 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63919 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63920 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63921 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63922 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63923 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63924 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63925 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63928 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63938 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63939 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63940 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63941 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63944 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63945 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63946 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63947 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63950 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63952 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63956 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63957 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63958 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63962 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63970 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63971 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63975 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63978 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63979 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63981 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63984 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63987 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63992 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63993 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63994 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63996 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64000 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64001 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64002 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64007 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64008 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64009 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64011 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64015 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64017 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64018 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64024 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64025 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64026 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64027 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64029 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64030 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64032 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64034 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64035 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64037 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64041 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64042 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64047 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64048 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64051 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64053 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64054 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64061 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64068 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64069 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64071 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64080 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64098 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64099 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64102 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64109 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64111 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64113 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64114 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64115 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64117 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64119 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64122 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64132 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64136 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64137 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64160 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64174 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64189 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64191 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64192 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64208 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64216 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64217 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64247 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64251 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64255 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64265 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64266 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64267 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64268 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64271 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64276 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64277 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64280 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64283 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64286 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64287 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64296 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64298 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64300 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64303 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64304 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64305 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64306 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64312 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64317 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64319 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64320 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64321 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64322 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64323 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64324 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64340 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64341 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64342 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64354 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64355 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64364 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64366 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64372 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64375 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64377 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64378 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64379 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64380 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64382 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64383 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64384 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64385 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64387 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64401 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64402 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64410 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64414 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64418 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64422 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64434 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64439 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64448 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64456 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64470 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64471 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64473 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64475 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64481 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64483 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64490 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64508 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64515 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64516 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64520 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64523 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64525 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64527 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64530 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64531 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64534 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64539 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64543 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64548 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64551 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64552 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64554 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45885 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53053 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53062 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53078 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53110 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53189 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53200 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53202 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53203 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53209 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53230 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53253 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53196 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46125 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46331 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-15794 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-6238 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53094 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53267 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53176 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2015-8553 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-1193 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-64535 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-0564 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-52910 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53033 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53081 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53085 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53090 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-44034 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53092 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40190 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-3714 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2018-1121 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-52908 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46113 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52923 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43502 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46273 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46304 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46320 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52909 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52958 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53050 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53086 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53095 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53151 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53159 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53183 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53269 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2015-7837 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-8660 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-0480 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-4543 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-48846 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48929 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-49940 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50230 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50232 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50332 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50380 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-0160 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31082 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52879 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53642 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54190 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35895 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35995 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21988 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43492 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43496 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45834 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45835 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45836 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45840 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45842 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45843 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45845 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45846 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46104 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46105 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46106 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46107 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46108 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46109 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46111 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46118 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46126 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46127 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46128 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46131 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46132 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46134 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46138 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46139 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46141 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46142 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46143 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46144 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46146 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46148 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46151 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46153 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46156 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46157 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46158 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46160 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46161 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46165 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46167 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46168 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46169 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46170 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46171 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46172 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46178 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46179 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46182 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46184 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46186 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46188 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46190 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46192 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46193 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46196 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46200 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46201 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46202 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46207 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46211 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46214 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46216 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46220 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46221 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46222 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46223 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46224 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46225 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46226 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46228 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46229 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46231 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46233 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46235 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46236 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46239 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46290 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46302 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46303 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46305 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46314 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46315 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46321 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46322 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52913 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52915 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52916 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52921 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52925 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52926 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52927 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52928 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52929 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52930 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52936 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52937 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52938 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52939 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52940 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52941 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52944 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52948 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52949 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52954 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52960 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52961 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52963 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52964 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52965 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52967 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52970 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52974 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52975 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52977 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52978 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52979 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52980 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52981 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52984 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52985 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52988 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52990 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52994 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52995 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52996 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52997 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52999 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53001 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53003 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53007 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53012 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53013 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53014 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53015 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53017 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53018 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53019 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53021 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53022 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53023 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53027 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53028 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53029 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53030 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53032 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53034 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53037 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53039 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53051 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53056 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53064 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53066 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53069 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53074 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53076 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53077 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53079 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53080 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53083 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53088 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53101 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53103 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53105 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53107 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53114 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53122 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53127 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53128 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53134 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53139 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53140 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53141 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53144 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53150 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53155 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53163 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53164 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53167 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53168 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53169 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53180 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53181 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53184 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53187 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53190 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53191 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53197 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53199 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53208 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53210 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53211 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53214 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53218 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53219 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53220 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53221 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53227 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53231 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53241 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53243 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53245 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53251 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53252 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53257 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53263 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53271 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53274 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53278 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53279 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53280 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53281 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53282 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53283 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53284 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53285 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53287 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53288 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53289 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53291 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53292 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53293 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53295 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53297 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53298 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53299 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53301 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53302 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53304 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53305 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53306 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53307 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53308 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53310 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53311 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53312 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53313 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53314 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53315 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53316 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53317 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53318 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53319 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53320 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53321 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53323 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53324 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53325 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53326 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53327 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53328 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53331 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53332 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53333 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53334 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53335 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53336 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53337 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53338 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53339 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53340 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53342 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53343 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53344 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53345 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53347 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53348 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53349 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53350 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53351 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53353 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53358 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53364 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53365 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53367 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53369 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53370 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53371 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53372 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53373 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53376 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53377 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53378 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53379 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53382 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53385 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53393 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53394 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53400 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53402 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53403 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63798 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63803 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63810 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63821 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63822 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63832 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63837 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63838 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63840 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63841 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63842 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63843 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63844 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63845 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63849 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63850 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63851 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63852 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63853 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63858 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63860 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63863 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63864 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63865 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63867 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63868 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63869 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63870 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63871 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63872 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63876 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63877 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63878 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63880 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63890 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63892 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63893 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63897 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63900 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63902 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63903 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63904 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63906 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63926 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63927 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63929 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63935 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63937 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63942 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63943 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63948 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63955 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63961 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63963 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63964 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63968 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63969 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63973 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63974 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63976 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63977 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63980 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63982 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63983 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63985 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63986 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63988 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63989 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63990 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63991 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63995 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63997 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63998 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63999 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64003 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64004 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64005 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64006 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64012 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64013 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64014 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64019 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64020 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64021 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64036 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64038 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64039 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64040 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64046 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64052 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64057 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64058 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64059 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64060 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64062 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64063 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64064 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64065 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64066 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64067 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64070 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64072 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64073 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64076 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64077 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64078 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64079 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64081 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64103 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64105 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64106 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64107 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64110 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64112 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64116 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64118 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64120 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64121 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64123 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64125 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64126 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64127 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64128 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64130 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64131 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64133 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64134 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64144 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64145 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64146 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64149 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64150 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64151 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64152 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64153 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64155 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64156 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64157 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64158 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64159 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64162 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64163 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64170 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64171 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64172 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64173 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64175 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64176 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64177 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64178 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64179 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64180 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64181 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64182 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64183 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64184 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64185 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64186 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64187 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64190 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64205 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64206 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64210 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64212 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64213 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64214 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64220 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64222 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64223 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64224 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64225 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64227 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64228 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64229 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64231 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64232 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64235 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64237 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64239 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64243 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64244 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64245 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64253 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64254 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64256 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64275 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64279 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64282 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64284 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64288 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64289 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64290 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64291 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64292 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64293 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64294 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64295 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64297 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64299 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64301 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64307 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64308 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64309 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64310 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64313 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64315 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64316 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64325 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64326 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64327 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64328 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64329 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64330 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64332 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64333 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64334 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64335 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64336 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64338 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64343 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64344 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64346 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64347 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64351 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64352 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64356 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64357 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64360 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64362 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64363 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64365 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64368 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64369 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64370 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64373 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64374 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64376 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64381 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64388 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64403 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64404 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64405 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64406 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64407 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64408 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64409 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64411 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64412 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64413 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64415 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64416 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64417 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64419 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64423 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64424 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64426 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64428 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64430 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64433 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64435 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64436 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64451 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64452 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64453 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64454 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64455 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64458 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64460 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64463 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64464 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64465 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64472 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64474 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64476 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64477 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64478 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64479 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64480 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64482 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64485 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64486 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64487 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64488 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64489 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64491 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64496 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64507 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64510 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64511 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64512 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64513 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64514 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64517 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64519 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64522 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64524 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64526 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64529 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64537 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64540 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64541 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64542 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64544 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64545 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64546 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64547 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64553 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64555 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2017-13693 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12928 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12929 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22077 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45838 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45841 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45844 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46291 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46292 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46295 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46296 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46297 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46299 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46307 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46310 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46312 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46313 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46318 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52982 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53035 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53038 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53042 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53044 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53047 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53048 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53052 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53058 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53060 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53061 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53063 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53065 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53070 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53073 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53082 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53084 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53093 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53096 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53099 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53100 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53102 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53104 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53106 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53111 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53113 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53121 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53123 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53124 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53125 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53126 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53135 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53142 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53146 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53147 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53152 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53154 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53158 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53162 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53177 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53188 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53204 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53205 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53206 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53207 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53213 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53222 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53225 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53226 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53229 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53232 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53236 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53237 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53238 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53249 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53258 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53261 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53265 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53194 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64538 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | login 1:4.16.0-2+really2.41.3-3ubuntu2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42505 | NONE0 | stdlib v1.26.3 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.3 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules 1.7.0-5ubuntu3 fixed in 1.7.0-5ubuntu3.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules-bin 1.7.0-5ubuntu3 fixed in 1.7.0-5ubuntu3.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-runtime 1.7.0-5ubuntu3 fixed in 1.7.0-5ubuntu3.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam0g 1.7.0-5ubuntu3 fixed in 1.7.0-5ubuntu3.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52955 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46159 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46187 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46194 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53008 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53108 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53352 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2017-0537 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-46298 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | login 1:4.16.0-2+really2.41.3-3ubuntu2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-15213 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-4010 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-17977 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-14304 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-41848 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% 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-2020-35501 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50812 | NONE0 | libsqlite3-0 3.46.1-9ubuntu0.1 fixed in 3.46.1-9ubuntu0.2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50813 | NONE0 | libsqlite3-0 3.46.1-9ubuntu0.1 fixed in 3.46.1-9ubuntu0.2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53215 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43490 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46311 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52911 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52914 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53010 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53040 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53043 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53046 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53055 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53068 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53130 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53170 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53171 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53172 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53173 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53186 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53198 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53240 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-54105 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54187 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43495 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43498 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46055 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46110 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46112 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46124 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46129 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46154 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46164 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46177 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46197 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46198 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46199 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46204 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46205 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46206 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46208 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46210 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46212 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46218 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46230 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46232 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46238 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46240 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52919 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52922 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52931 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52932 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52934 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52959 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52983 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53020 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53041 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53045 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53165 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53174 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53201 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53300 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53329 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53356 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53363 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53368 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53374 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53375 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53380 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53383 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-53386 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53387 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53389 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53390 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53401 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63793 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63796 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63799 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63805 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63806 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63811 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63812 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63813 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63814 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63815 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63816 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63817 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63818 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63819 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63820 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63825 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63827 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63828 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63833 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63834 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63835 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63836 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63839 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63846 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63847 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63848 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63854 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63855 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63856 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63857 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63859 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63861 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63862 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63873 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63874 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63879 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63881 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63882 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63895 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63905 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63907 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63908 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63909 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63911 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63915 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63930 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63931 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63932 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63933 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63934 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63936 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63949 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63951 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63953 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63954 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63959 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63960 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63965 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63966 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63967 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63972 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64010 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64022 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64023 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64031 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64033 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64043 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64044 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64045 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64049 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64050 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64055 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64056 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64074 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64075 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64082 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64083 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64084 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64085 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64086 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64087 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64088 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64089 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64090 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64091 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64093 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64094 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64095 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64096 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64097 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64100 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64101 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64104 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64108 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64124 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64129 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64135 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64138 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64139 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64140 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64141 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64142 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64143 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64147 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64148 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64154 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64161 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64164 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64165 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64166 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64167 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64168 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64169 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64188 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64207 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64209 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64211 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64215 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64218 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64219 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64221 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64226 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64230 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64233 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64234 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64236 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64238 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64240 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64241 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64242 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64246 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64249 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64258 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64259 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64260 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64261 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64262 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64263 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64264 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64269 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64270 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64272 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64273 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64274 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64278 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64285 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64302 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64314 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64318 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64331 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64337 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64339 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64345 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64348 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64349 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64350 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64353 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64358 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64359 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64361 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64367 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64371 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64386 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64389 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64390 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64391 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64392 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64393 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64394 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64395 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64396 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64397 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64398 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64399 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64400 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64420 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64421 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64425 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64429 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64432 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64437 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64438 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64440 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64441 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64442 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64443 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64444 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64445 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64446 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64447 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64449 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64450 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64457 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64459 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64461 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64462 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64466 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64467 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64468 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64469 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64484 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64492 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64493 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64494 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64495 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64497 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64499 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64500 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64501 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64502 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64503 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64504 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64505 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64509 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64518 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64521 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64528 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64532 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64533 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64536 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64549 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64550 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-20585 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43497 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53057 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53087 | NONE0 | linux-libc-dev 7.0.0-27.27 fixed in 7.0.0-28.28 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53160 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53161 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53216 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53217 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53247 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53248 | NONE0 | linux-libc-dev 7.0.0-27.27 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53273 | NONE0 | linux-libc-dev 7.0.0-27.27 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.