Last scanned:
This image is safe for production use. The stats show 40 exposed and 65 post-exploit-only entries, but none are in the severity bands at or above 6, and the maximum severities are 5.5 and 3.3. No specific top findings or vulnerability identifiers were supplied in INPUT 4 or INPUT 5, so no particular exploitable path is identified. The image also has positive trust signals: publisher nvidia, RELIABLE verdict, and a pinned digest.
| 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.2% Theoretical Threat | Directly Exposed |
| CVE-2026-75804 | MEDIUM4.5 | libssl3t64 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM4.5 | libssl3t64 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-84784 | MEDIUM4.5 | libssl3t64 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54873 | MEDIUM4.5 | openssl-provider-legacy 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75804 | MEDIUM4.5 | openssl-provider-legacy 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM4.5 | openssl-provider-legacy 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-84784 | MEDIUM4.5 | openssl-provider-legacy 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc-bin 2.43-2ubuntu2.4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc-dev-bin 2.43-2ubuntu2.4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc-gconv-modules-extra 2.43-2ubuntu2.4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc6 2.43-2ubuntu2.4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc6-dev 2.43-2ubuntu2.4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54875 | MEDIUM4 | libssl3t64 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54875 | MEDIUM4 | openssl-provider-legacy 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | libc-bin 2.43-2ubuntu2.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | libc-dev-bin 2.43-2ubuntu2.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | libc-gconv-modules-extra 2.43-2ubuntu2.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | libc6 2.43-2ubuntu2.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | libc6-dev 2.43-2ubuntu2.4 No fix yet | 0.2% 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-x86-64-linux-gnu 2.46-3ubuntu2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2019-20633 | LOW3.3 | patch 2.8-2build1 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-35189 | LOW3.15 | libssl3t64 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35191 | LOW3.15 | libssl3t64 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.15 | openssl-provider-legacy 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35191 | LOW3.15 | openssl-provider-legacy 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102473 | LOW2.8 | dash 0.5.12-12ubuntu3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-45261 | LOW2.8 | patch 2.8-2build1 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-56288 | LOW2.8 | patch 2.8-2build1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56289 | LOW2.8 | patch 2.8-2build1 No fix yet | 0.1% 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-89162 | LOW2.8 | libpcre2-8-0 10.46-1build1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 259.5-0ubuntu3.4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 259.5-0ubuntu3.4 No fix yet | 0.1% 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-42772 | LOW2.7 | openssl 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.7 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54873 | LOW2.7 | openssl 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-75804 | LOW2.7 | openssl 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-75806 | LOW2.7 | openssl 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-84784 | LOW2.7 | openssl 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-86145 | LOW2.51 | libpcre2-8-0 10.46-1build1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-54875 | LOW2.4 | openssl 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-89161 | LOW2.39 | libpcre2-8-0 10.46-1build1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-103111 | LOW2.33 | libpcre2-8-0 10.46-1build1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-89157 | LOW2.26 | libpcre2-8-0 10.46-1build1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-84782 | LOW2.26 | libssl3t64 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-84782 | LOW2.26 | openssl 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-84782 | LOW2.26 | openssl-provider-legacy 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-18477 | LOW2.24 | tar 1.35+dfsg-4ubuntu0.4 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW2.24 | tar 1.35+dfsg-4ubuntu0.4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-102474 | LOW2.04 | dash 0.5.12-12ubuntu3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-89158 | LOW1.99 | libpcre2-8-0 10.46-1build1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-89160 | LOW1.99 | libpcre2-8-0 10.46-1build1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-35189 | LOW1.89 | openssl 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-35191 | LOW1.89 | openssl 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.17.4-2ubuntu3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-89156 | LOW1.81 | libpcre2-8-0 10.46-1build1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54872 | LOW1.81 | libssl3t64 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-72897 | LOW1.81 | libssl3t64 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-75805 | LOW1.81 | libssl3t64 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-77696 | LOW1.81 | libssl3t64 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-54872 | LOW1.81 | openssl 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-72897 | LOW1.81 | openssl 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-75805 | LOW1.81 | openssl 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-77696 | LOW1.81 | openssl 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-54872 | LOW1.81 | openssl-provider-legacy 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-72897 | LOW1.81 | openssl-provider-legacy 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-75805 | LOW1.81 | openssl-provider-legacy 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-77696 | LOW1.81 | openssl-provider-legacy 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.6 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42772 | LOW1.62 | libssl3t64 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.7 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54873 | LOW1.62 | libssl3t64 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42772 | LOW1.62 | openssl-provider-legacy 3.5.5-1ubuntu3.5 fixed in 3.5.5-1ubuntu3.7 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-68457 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64562 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74744 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74752 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89676 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68159 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68480 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72083 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72130 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72222 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72319 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-72323 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74476 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74516 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74588 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74597 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74669 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74705 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89495 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89656 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89674 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89775 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99999 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68156 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74580 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72221 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74469 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-80586 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80844 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89526 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89631 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-93787 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68376 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72129 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72318 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80985 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89653 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90011 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-72003 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89633 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89524 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74509 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64564 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-50240 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68108 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68380 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80714 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89638 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93817 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98260 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2013-7445 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-3238 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50090 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-0030 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-26242 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54187 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64530 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64552 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64565 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64582 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68138 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68143 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68200 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68264 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68290 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68398 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72052 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72098 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72255 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72298 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72339 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74270 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74480 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74518 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74581 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74582 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74583 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74746 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74753 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80521 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80522 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80536 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80951 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81000 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89450 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89507 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89508 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89509 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89513 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89617 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89725 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89736 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89754 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89761 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89970 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-93288 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97528 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97602 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98116 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98256 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2017-13165 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2018-12930 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12931 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19378 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-19814 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-26934 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-33053 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72042 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89465 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89972 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-93827 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80590 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80885 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74345 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74394 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68136 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-0400 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-25836 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64534 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72248 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72251 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74586 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97417 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98417 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-20426 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2026-78667 | NONE0 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-78669 | NONE0 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97031 | NONE0 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74631 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89783 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2019-14899 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-68426 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68121 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68201 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97415 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64563 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68166 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68278 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68294 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72099 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72243 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74283 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74574 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80863 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93262 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93813 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97505 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74556 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68198 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68409 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74510 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89481 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97493 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97497 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-50551 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64549 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64572 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68099 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68155 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68188 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68263 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68373 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72049 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72084 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80530 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89596 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89700 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89769 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89779 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89846 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-93812 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97422 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98155 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97425 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97494 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97495 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72287 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72399 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89530 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89652 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89659 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89708 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98365 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64539 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64543 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64548 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64554 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64557 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64558 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68100 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68117 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68147 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68162 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68236 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68245 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68257 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68323 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68329 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68343 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68393 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68401 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68404 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68427 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68442 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68451 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68470 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72111 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72123 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72135 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72151 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72284 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72288 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72338 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72405 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74269 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74310 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74378 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74390 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74446 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74506 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74533 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74534 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74535 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74537 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74677 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74684 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74700 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74714 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74715 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74724 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80668 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80681 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80683 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80691 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80693 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80700 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80702 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80710 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80716 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80718 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80837 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80841 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80852 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80864 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80982 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89448 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89528 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89537 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89550 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89564 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89580 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89637 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89675 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89680 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89685 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89707 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90092 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90093 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90104 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90111 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90161 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90227 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90237 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90256 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90313 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90317 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90343 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97429 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97555 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97557 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-97564 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97988 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98033 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98034 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98041 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98222 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98229 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98283 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98333 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98341 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98364 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98376 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2021-3864 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-1247 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2961 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53216 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64551 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64559 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64560 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64561 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64573 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64577 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-68118 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68123 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-68125 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68128 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68131 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68140 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68144 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68145 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68148 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68149 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68154 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68157 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68158 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68160 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-68161 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68169 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68181 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68202 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68253 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68266 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68267 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68273 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68274 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68276 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68289 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68293 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68300 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-68315 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68316 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68320 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68325 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68335 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68338 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68349 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68351 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68363 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68365 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68368 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68374 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68377 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68379 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-68381 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68388 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68389 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68390 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68391 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68397 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68402 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68415 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68452 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68453 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68458 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68479 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72018 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72020 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72021 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72027 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72045 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72046 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72053 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72055 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72057 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72061 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72065 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72066 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72069 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72072 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72095 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72102 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72125 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72126 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72136 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72137 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72139 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72157 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72217 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72218 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72220 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72242 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72247 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72249 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72252 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72253 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72261 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72262 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72283 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72289 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72301 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72317 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72320 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72322 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72351 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72361 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72371 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72381 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72382 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72389 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72398 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72407 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72408 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72417 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72419 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72422 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72427 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72442 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72443 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72446 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72449 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72451 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72452 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72463 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72473 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72492 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72499 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72500 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72502 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74256 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74287 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74305 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74306 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74328 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74359 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74364 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74398 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74430 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74434 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74435 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74436 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74439 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74440 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74443 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74447 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74452 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74456 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74471 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74472 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74474 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74488 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74492 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74493 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74496 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74498 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74499 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74501 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74503 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74513 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74517 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74520 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74528 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74541 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74557 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74563 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74569 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74573 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74575 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74587 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74591 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74594 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74598 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74608 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74609 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74610 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74611 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74612 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74614 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74615 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74616 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74621 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74624 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74629 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74630 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74637 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74639 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74640 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74641 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74656 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74660 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74661 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74662 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74666 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74668 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74674 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74682 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74688 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74692 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74695 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74697 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74721 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74730 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74737 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74743 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80528 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80537 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80540 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80552 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80553 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80558 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80561 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80571 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80582 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80584 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80585 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80589 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80603 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80609 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80613 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80630 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-80663 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80722 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80775 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80778 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80780 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80792 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80810 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80824 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80840 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80842 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80848 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80849 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80850 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80878 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80887 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80921 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80929 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80944 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80945 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80947 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80952 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80970 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80971 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80973 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80976 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80977 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80978 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80979 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80981 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80986 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80989 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80994 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81001 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81002 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-81003 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-81008 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81015 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89440 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89444 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89445 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89456 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89458 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89476 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89477 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89478 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89479 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89480 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89482 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89485 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89487 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89488 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89500 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89501 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89510 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89523 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89532 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89533 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89534 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89535 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89536 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89538 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89540 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89541 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89542 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89545 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89546 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89547 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89548 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89551 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89553 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89555 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89558 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89559 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89560 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89563 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89569 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89570 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89575 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89581 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89582 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89583 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89584 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89587 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89602 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89606 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89607 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89609 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89619 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89620 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89625 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89630 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89634 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89641 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89642 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89643 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89649 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89650 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89651 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89655 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89657 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89658 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89660 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89662 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89663 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89664 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89665 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89666 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89668 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89669 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89670 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89671 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89672 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89677 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89678 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89683 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89684 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89686 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89688 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89689 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89690 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89691 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89693 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89694 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89695 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89697 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89698 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89703 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89704 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89705 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89706 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89712 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89727 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89729 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89737 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89739 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89741 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89745 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89746 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89747 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89755 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89758 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89766 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89777 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89791 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89811 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89894 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89930 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89932 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90008 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90049 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90071 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90099 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90102 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90110 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90128 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90135 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90142 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90146 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90151 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90177 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90201 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90203 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90207 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90230 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90234 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90240 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90241 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90243 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90244 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90260 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90263 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90272 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90278 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90284 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90292 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90294 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90303 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90307 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90312 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90325 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90334 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90347 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90427 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93189 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93207 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93283 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93800 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97476 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97524 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-97527 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97533 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97547 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97561 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97563 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97573 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97575 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97583 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97584 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97589 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97594 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97595 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97608 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97611 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97612 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97620 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97903 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97926 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97931 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97934 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97936 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97940 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97943 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97954 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97955 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97957 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97965 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97975 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97990 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97991 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98014 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98015 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98016 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98023 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98025 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98037 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98047 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98048 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98050 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98060 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98066 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98068 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98069 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98070 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98075 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98108 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98122 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98123 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98130 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98154 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98163 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98173 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98176 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98184 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98186 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98196 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98197 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98201 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98204 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98205 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98214 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98215 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98216 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98217 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98221 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98226 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98230 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98231 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98236 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98238 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98239 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98241 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98242 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98246 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98247 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98249 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98251 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98252 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98254 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98255 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98257 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98258 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98261 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98262 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98265 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98266 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98276 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98280 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98281 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98282 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98284 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98287 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98290 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98291 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98295 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98296 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98299 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98306 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98312 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98314 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98318 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98320 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98323 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98330 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98331 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98339 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98342 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98343 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98347 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98350 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98356 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98357 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98358 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98362 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98366 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98367 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98368 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98370 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98373 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98374 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98377 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98378 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98379 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98380 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98381 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98382 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98383 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98392 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98401 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98426 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98428 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98429 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-45885 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68086 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68093 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68142 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68400 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68432 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68448 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72051 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72310 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72329 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72342 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72436 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72469 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74271 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74289 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74391 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74405 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74441 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74554 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74568 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74672 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80698 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89543 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89632 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89636 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89648 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89654 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89682 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89702 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89709 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89713 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89719 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89772 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90036 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90180 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90185 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90189 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90206 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90235 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90315 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90326 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90336 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93200 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97427 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97431 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97496 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97531 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97532 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97901 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97933 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97935 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97938 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97949 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97986 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98032 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98156 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98174 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98175 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98211 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98213 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98245 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98264 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98375 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98403 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98430 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90414 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68284 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93125 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93144 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-15794 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-89579 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89661 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93112 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-6238 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89640 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90255 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64535 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74385 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98167 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-1193 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-64550 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74316 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74323 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89511 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89679 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89696 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-0564 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56866 | NONE0 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94439 | NONE0 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68399 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72183 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90333 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98039 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-44034 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89965 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80788 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98185 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40190 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68103 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68350 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89778 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89786 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90054 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90068 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90211 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72054 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74515 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-94448 | NONE0 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98432 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-3714 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-68334 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-1121 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-98271 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97032 | NONE0 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-93101 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | binutils-common 2.46-3ubuntu2 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-90162 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-100074 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64567 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68098 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68152 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68189 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68196 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68204 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68259 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68445 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68446 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68447 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68471 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72024 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72110 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72124 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72162 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72195 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72196 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72198 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72213 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72331 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72369 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72372 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72373 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72375 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72380 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72383 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72390 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72413 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72423 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72434 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72461 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72462 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72464 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72470 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72472 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72478 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72493 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72494 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72497 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74257 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74268 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74302 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74314 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74317 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74334 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74341 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74344 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74347 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74350 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74363 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74386 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74387 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74388 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74411 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74427 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-74438 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74454 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74465 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74470 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74522 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74529 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74530 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74565 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74578 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74723 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80551 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80554 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80631 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80634 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80637 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80644 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80665 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80671 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80692 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80721 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80937 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80980 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80991 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89492 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89520 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89531 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89544 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89565 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89622 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89837 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90108 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90148 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90149 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90150 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90152 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90155 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90199 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90200 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90204 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90205 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90217 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90320 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90321 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90324 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93192 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93196 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93199 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93282 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93790 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93796 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93806 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93824 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93828 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97442 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97513 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97530 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97562 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97565 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97581 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97603 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97615 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97906 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97960 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98017 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98019 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98056 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98104 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98107 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98115 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98134 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98164 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98332 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98359 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98420 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2015-7837 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-8660 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-0480 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-4543 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-49940 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50380 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-0160 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31082 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-53642 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35895 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-100070 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-100071 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-100073 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100075 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-100076 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100077 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100078 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100079 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64190 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64349 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64537 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64540 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64541 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64542 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64544 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64545 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64546 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64547 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64553 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64555 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64566 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64569 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64570 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64571 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64575 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64576 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64578 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64579 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68096 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68106 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68109 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68110 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68111 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68112 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68113 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68114 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68115 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68119 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68122 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68126 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68127 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68129 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68130 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68132 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68133 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68134 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68135 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68137 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68139 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68141 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68146 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68163 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68164 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68165 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68168 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68170 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68172 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68173 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68174 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68175 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68176 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68178 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68180 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68182 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68183 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68184 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68186 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68187 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68190 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68191 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68193 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68194 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68195 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68197 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68205 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68206 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68208 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68209 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68212 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68214 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68215 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68216 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68217 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68218 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68219 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68222 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68224 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68226 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68227 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68228 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68229 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68231 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68232 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68234 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68235 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68237 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68239 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68241 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68242 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68243 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68244 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68246 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68247 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68248 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68249 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68250 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68251 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68252 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68254 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68255 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68256 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68260 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68261 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68262 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68265 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68268 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68269 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68270 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68271 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68272 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68275 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68277 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68279 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68281 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68282 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68283 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68292 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68296 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68297 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68298 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68299 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68301 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68304 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68306 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68307 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68308 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68309 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68310 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68311 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68312 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68313 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68317 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68318 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68319 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68321 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68322 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68324 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68326 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68328 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68331 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68332 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68333 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68336 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68339 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68341 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-68342 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68345 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68346 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68347 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68348 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68352 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68354 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68355 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68356 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68357 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68358 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68360 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68362 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68364 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68366 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68367 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68369 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68371 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68372 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68375 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68378 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68383 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68384 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68385 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68386 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68387 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68392 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68394 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68395 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68403 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68405 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68406 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68407 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68408 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68410 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68411 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68412 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68413 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68414 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68416 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68417 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68418 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68419 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68420 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68421 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68422 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68425 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68428 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68429 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68430 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68431 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68433 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68434 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68437 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68439 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68440 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68443 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68444 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68449 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68450 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68455 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68456 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68463 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68464 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68465 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68467 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68469 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68472 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68473 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68474 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68475 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68477 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68478 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72004 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72005 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72006 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72007 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72008 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72009 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72010 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72011 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72012 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72013 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72014 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72015 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72016 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72017 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72019 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72022 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72023 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72025 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72026 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72029 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72030 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72032 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72033 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-72034 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72035 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72036 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72037 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72038 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72039 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72040 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72041 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-72047 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72048 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72050 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72056 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72058 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72059 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72060 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72063 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72064 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72067 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72068 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72070 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72073 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72074 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72076 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72077 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72078 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72079 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72080 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72081 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72082 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72085 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72086 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72087 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72088 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72089 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72091 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72093 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72094 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72096 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72097 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72101 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72103 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72104 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72105 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72107 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72109 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72113 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72114 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72115 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72116 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72117 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72118 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72119 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72120 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72121 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72122 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72127 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72128 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72131 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72132 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72133 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72138 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72141 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72142 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72143 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72146 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72148 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72149 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72152 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72153 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72155 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72156 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72158 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72159 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72160 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72161 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72163 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72164 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72165 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72166 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72167 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72168 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72169 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72170 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72171 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72172 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72173 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72174 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72175 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72176 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72177 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72180 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72181 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72182 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72191 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72192 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72193 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72194 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-72197 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72200 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72203 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72212 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72214 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72215 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72216 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72223 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72224 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72225 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72226 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-72227 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72228 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72229 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72230 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72231 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72232 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72233 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72234 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72235 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72236 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72237 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72238 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72240 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72241 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72244 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72245 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72250 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72254 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72256 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72257 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72258 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72259 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72260 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72263 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72264 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72265 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72266 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72267 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72268 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72269 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72270 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72271 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72272 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72273 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72274 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72275 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72276 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72277 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72278 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72279 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72280 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72282 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72285 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72290 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72292 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72293 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72296 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72297 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72299 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72300 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72302 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72304 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72305 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72307 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72308 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72313 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72315 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72321 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72325 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72326 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72327 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72328 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72330 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72332 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72333 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72334 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72340 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72343 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72345 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72347 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72349 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72350 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72355 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72356 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72357 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72360 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72362 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72363 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72364 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72365 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72366 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72367 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72368 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72370 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72374 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72376 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72377 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72379 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72385 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72386 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72387 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72388 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72391 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72392 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72393 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72394 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72395 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72396 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72400 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72401 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72402 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72403 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72404 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72406 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72409 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72412 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72414 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72415 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72416 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72418 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72420 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72421 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72424 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72428 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72429 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72430 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72431 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72433 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72435 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72437 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72438 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72440 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72441 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72444 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72445 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72447 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72448 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72450 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72453 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72455 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72456 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72457 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72458 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72459 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72460 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72465 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72466 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72467 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72468 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72471 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72474 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72475 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72477 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72479 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72480 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72481 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72483 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72484 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72485 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72486 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72488 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72489 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72491 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72495 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72496 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72498 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74255 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74258 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74260 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74261 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74263 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74265 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74266 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74267 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74274 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74276 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74277 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74278 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74279 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-74280 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-74281 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74282 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74284 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74286 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74288 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74290 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74292 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74293 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74294 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74295 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74296 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74297 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74300 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74301 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74303 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74304 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74308 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74309 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74311 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74318 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74320 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74321 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74322 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74325 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74327 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74329 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74330 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74331 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74332 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74333 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74335 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74336 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74337 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74338 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74339 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74340 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74342 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74346 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74348 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74349 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74351 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74352 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74353 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74354 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74355 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74356 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74358 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74360 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74362 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74366 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74367 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74368 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74370 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74372 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74376 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74377 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74379 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74381 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74382 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74384 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74392 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74393 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74395 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74396 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74399 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74400 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74402 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74404 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74406 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74408 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74409 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74410 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74413 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74415 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74416 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74417 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74419 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74420 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74421 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74422 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74423 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74424 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74425 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74426 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74428 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74429 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74431 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74432 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74437 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74442 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74444 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74445 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74449 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74451 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74453 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74455 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74457 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74458 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74459 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74460 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74461 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74462 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74463 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74464 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74467 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74468 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74473 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74475 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74477 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74478 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-74479 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74482 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74483 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74484 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74485 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74486 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74487 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74491 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74494 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74495 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74497 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74500 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74504 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74505 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74507 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74508 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74523 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74524 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74525 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74526 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74531 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74532 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74536 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74538 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74539 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74540 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74542 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74546 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74547 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74548 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74549 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74550 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74551 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74552 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74555 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74558 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74559 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74560 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74561 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74562 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74566 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74567 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74572 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74576 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74577 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74579 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74585 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74589 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74590 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74592 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74593 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74595 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74596 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74599 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74600 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74601 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74602 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74603 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74606 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74607 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74613 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74617 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74618 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74619 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74620 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74622 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74623 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74625 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74626 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74627 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74628 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74632 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74633 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74634 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74635 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74636 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74638 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74643 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74644 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74645 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74646 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74647 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74648 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74649 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74650 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74651 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74652 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74654 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74655 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74657 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74658 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74659 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74663 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74664 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74665 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74667 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74670 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74671 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74673 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74675 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74676 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74678 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74679 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74680 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74681 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74683 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74685 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74686 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74693 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74694 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74696 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74698 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74699 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74701 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74702 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74703 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74704 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74706 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74707 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74708 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74709 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74710 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74712 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74716 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74717 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74718 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74719 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74720 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74722 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74726 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74727 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74728 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74734 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74735 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74736 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74738 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74739 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74740 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74741 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74742 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74745 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74747 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74748 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74750 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80519 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80520 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80523 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80524 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80525 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80526 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80527 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80529 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80532 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80533 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80535 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80538 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80539 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80541 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80542 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80547 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80548 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80549 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80550 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80557 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80559 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80560 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80562 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80563 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80564 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80565 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80566 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80567 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80568 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80569 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80570 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80573 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80574 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80575 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80576 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80577 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80578 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80581 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80583 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80587 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80588 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80592 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80593 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80594 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80595 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80596 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80597 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80598 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80599 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80600 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80601 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80602 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80604 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80605 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80606 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80610 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80612 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80614 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80615 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80617 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80618 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80619 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80620 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80621 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80626 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80638 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80641 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80646 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80659 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80664 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80666 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80667 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80669 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80670 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80675 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80684 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80686 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80694 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80695 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80697 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80699 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80701 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80703 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80705 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80707 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80713 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80715 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80717 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80720 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80727 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80784 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80797 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80811 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80821 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80843 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80855 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80856 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80877 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80897 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80898 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80902 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80903 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80927 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80928 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80930 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80931 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80932 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80933 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80934 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80935 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80936 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80938 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80939 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80940 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80941 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80942 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80943 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80946 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80949 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80950 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80953 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80954 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80955 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80956 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80957 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80958 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80959 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80960 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80961 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80962 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80963 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80964 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80965 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80966 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80967 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80968 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80969 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80972 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80975 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80983 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80984 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80987 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80988 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80992 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80993 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80996 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80997 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-81004 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81006 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-81009 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81010 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81012 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-81013 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81014 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81016 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81017 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81018 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89438 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89439 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89442 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89443 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89446 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89447 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89449 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89451 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89453 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89454 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89455 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89457 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89461 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89463 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89464 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89466 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89467 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89469 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89470 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89471 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89473 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89474 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89475 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89483 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89484 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89486 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89489 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89490 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89491 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89493 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89494 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89496 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89497 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89498 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89502 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89503 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89504 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89506 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89512 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89514 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89515 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89517 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89518 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89519 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89521 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89522 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89525 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89527 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89529 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89549 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89554 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89557 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89561 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89566 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89567 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89571 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89572 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89573 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89576 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89578 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89585 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89586 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89588 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89589 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89590 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89591 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89592 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89593 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89594 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89595 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89597 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89598 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89599 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89600 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89601 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89604 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89605 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89608 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89615 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89616 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89618 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89621 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89623 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89624 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89626 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89627 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89628 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89629 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89644 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89645 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89646 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89647 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89667 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89673 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89687 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89692 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89699 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89701 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89710 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89711 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89714 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89715 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89716 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89717 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89720 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89721 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89723 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89724 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89726 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89728 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89730 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89731 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89732 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89733 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89734 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89735 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89742 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89743 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89749 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89750 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89751 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89752 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89753 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89757 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89759 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89765 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89767 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89768 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89771 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89815 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89816 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89820 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89867 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89872 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89881 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89886 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89889 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89896 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89909 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89923 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89924 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89925 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89953 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89975 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89982 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90005 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90007 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90015 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90051 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90053 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90055 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90056 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90058 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90059 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90061 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90062 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90063 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90065 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90066 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90067 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90069 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90070 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90072 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90073 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90074 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90075 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90076 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90077 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90078 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90079 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90080 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90081 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90082 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90083 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90085 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90087 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90088 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90089 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90090 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90091 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90094 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90095 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90098 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90100 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90101 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90103 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90107 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90109 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90113 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90114 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90115 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90119 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90120 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90121 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90122 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90124 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90125 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90126 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90127 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90129 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90130 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90136 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90137 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90138 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90139 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90140 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90141 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90143 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90145 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90147 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90154 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90157 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90158 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90159 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90160 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90163 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90164 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90165 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90166 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90170 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90175 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90176 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90178 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90179 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90183 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90190 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90191 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90192 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90193 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90195 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90197 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90198 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90202 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90209 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90212 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90213 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90214 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90215 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90216 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90218 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90219 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90220 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90221 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90222 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90223 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90224 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90225 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90226 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90228 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90229 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90231 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90232 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90233 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90242 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90245 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90246 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90248 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90249 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90250 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90251 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90252 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90253 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90254 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90257 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90258 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90261 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90264 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90265 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90269 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90270 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90271 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90273 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90274 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90275 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90276 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90277 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90279 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90280 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90281 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90282 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90283 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90285 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90286 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90287 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90288 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90289 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90290 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90291 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90293 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90295 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90296 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90297 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90298 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90300 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90302 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90306 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90308 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90309 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90314 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90316 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90318 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90319 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90323 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90327 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90330 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90331 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90332 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90338 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90341 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90342 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90344 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90345 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90346 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90348 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90349 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90352 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90354 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90361 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90362 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90364 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90378 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90384 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90390 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90402 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90404 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90407 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90411 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90415 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90424 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90434 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92488 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92494 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92504 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-92519 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92524 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93056 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93059 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93071 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93082 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93083 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93089 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93090 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93102 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93126 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93130 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93136 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93145 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93151 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-93159 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93161 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93185 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93188 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93190 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93191 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93193 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93194 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93195 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93198 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93201 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93203 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93204 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93225 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93228 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93261 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93264 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93265 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93266 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93267 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93268 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93269 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93270 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93271 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93273 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93274 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93275 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93276 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93278 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93279 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93280 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93281 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93284 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93286 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93287 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93782 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93785 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93789 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93791 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93793 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93794 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93795 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93798 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93799 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93801 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93802 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93803 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93804 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93805 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93807 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93808 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93811 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93815 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93816 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93819 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93820 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93821 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93822 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93823 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93825 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93826 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93830 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97407 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97408 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97411 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97413 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97416 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97418 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97419 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97420 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97421 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97430 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97432 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97433 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97434 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97435 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97436 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97437 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97438 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97439 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97440 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97441 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97443 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97444 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97446 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97448 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97451 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97455 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97456 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97472 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97475 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97481 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97482 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97483 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97484 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97485 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97486 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97487 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97488 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97489 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97490 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97491 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97492 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97498 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97500 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97502 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97506 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97507 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97508 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97509 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97510 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97511 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97514 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97515 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97516 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97517 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97518 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97522 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97523 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-97525 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97526 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97529 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97538 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97542 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97543 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97544 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97545 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97546 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97548 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97549 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97551 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97552 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97553 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97558 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97560 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97566 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97567 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97571 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97572 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97574 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97576 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97577 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97578 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97579 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97580 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97582 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97585 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97586 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97587 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97588 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97590 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97591 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97592 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97593 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97596 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97597 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97598 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97601 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97604 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97606 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97607 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97610 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97613 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97614 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97617 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97621 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97899 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97900 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97902 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97904 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97905 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97907 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97909 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97910 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97912 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97913 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97914 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97915 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97916 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97917 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97919 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97920 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97921 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97923 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97924 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97927 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97928 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97930 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97932 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97939 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97942 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97944 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97945 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97946 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97947 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97948 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97951 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97952 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97953 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97956 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97958 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97959 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97961 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97963 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97964 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97966 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97967 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97968 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97969 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97970 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97971 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97972 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97974 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97976 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97977 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97979 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97981 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97982 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97983 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97984 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97985 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97993 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97995 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97996 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97997 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97998 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98000 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98001 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98002 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98005 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98006 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98007 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98009 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98010 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98011 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98012 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98013 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98018 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98020 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98021 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98022 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98024 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98026 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98027 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98028 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98029 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98030 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98031 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98038 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98043 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98044 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98045 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98049 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98051 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98052 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98053 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98054 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98055 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98057 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98058 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98059 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98061 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98062 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98063 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98064 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98065 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98071 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98072 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98074 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98080 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98082 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98087 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98092 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98103 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98105 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98106 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98110 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98111 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98112 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98113 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98114 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98117 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98118 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98119 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98120 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98121 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98125 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98126 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98127 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98128 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98129 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98143 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98144 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98146 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98147 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98149 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98150 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98151 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98152 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98153 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98157 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98158 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98159 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98160 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98162 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98166 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98168 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98170 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98177 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98179 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98180 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98187 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98188 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98189 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98190 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98191 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98193 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98194 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98195 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98199 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98200 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98202 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98203 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98206 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98207 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98208 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98209 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98210 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98218 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98223 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98224 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98227 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98228 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98233 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98234 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98235 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98237 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98240 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98244 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98253 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98259 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98263 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98267 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98268 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98269 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98270 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98272 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98277 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98278 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98279 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98288 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98289 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98292 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98293 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98297 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98298 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98302 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98303 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98304 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98308 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98311 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98319 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98321 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98322 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98324 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98327 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98328 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98329 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98334 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98335 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98336 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98337 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98340 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98344 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98345 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98346 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98348 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98349 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98351 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98352 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98360 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98361 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98369 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98371 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98372 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98384 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98386 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98388 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98389 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98390 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98391 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98393 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98394 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98398 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98402 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98404 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98406 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98407 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98408 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98410 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98413 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98415 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98419 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98421 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98422 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98427 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-13693 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12928 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12929 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-48846 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48929 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50230 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50232 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52879 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54190 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35995 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-100072 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64574 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68102 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68104 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68105 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68107 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68116 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68150 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68153 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68207 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68210 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68211 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68233 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68238 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68240 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68258 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68286 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68287 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68288 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68291 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68305 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68330 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68353 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68382 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68396 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68436 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68441 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68454 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68466 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72028 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72031 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72062 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72071 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72075 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72090 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72100 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72106 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72108 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72134 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72144 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72147 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72150 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72154 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72179 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72286 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72303 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72312 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72314 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72324 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72335 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72336 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72337 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72341 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72344 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72352 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72384 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72397 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72410 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72425 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72439 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72454 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72476 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72482 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72487 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74262 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74264 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74272 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74273 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74291 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74307 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74312 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74313 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74324 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74361 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74365 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74371 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74373 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74374 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74375 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74380 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74383 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74389 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74397 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74401 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74403 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74407 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74412 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74448 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74450 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74466 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74481 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74490 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74512 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74514 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74519 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74521 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74527 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74543 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74544 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74553 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74571 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74605 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74653 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74687 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74689 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74711 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74713 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74725 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74729 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74733 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74754 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80556 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80572 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80579 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80580 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80607 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80608 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80611 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80616 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80622 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80623 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80624 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80625 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80627 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80628 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80629 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80635 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80636 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80639 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80640 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80642 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80643 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80645 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80647 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80648 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80649 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80650 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80651 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80652 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80653 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80654 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80655 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80657 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80658 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80660 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80661 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80662 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80676 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80677 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80678 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80679 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80680 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80685 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80687 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80688 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80689 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80690 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80696 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80704 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80706 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80708 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80709 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80711 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80712 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80723 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80724 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80948 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80974 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80990 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80999 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81011 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89437 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89441 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89452 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89462 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89468 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89472 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89539 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89552 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89556 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89568 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89574 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89718 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89722 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89738 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89740 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89744 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89756 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89762 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89763 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89764 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89824 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89862 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89877 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89912 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89944 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89996 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90021 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90060 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90084 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90097 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90105 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90106 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90112 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90116 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90144 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90174 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90182 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90184 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90186 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90187 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90188 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90194 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90196 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90208 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90247 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90259 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90267 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90301 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90311 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90322 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90328 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90335 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90337 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90422 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92493 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93072 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93116 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93186 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93202 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93272 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93285 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93786 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93788 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93809 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93814 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93818 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93829 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97409 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97410 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97412 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97414 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97423 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97424 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97426 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97428 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97473 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97474 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97477 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97478 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97479 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97480 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97499 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97501 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97503 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97512 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97519 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97521 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97534 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97535 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97536 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97537 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97539 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97540 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97541 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97554 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97556 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97559 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97599 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97600 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97609 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97616 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97619 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97908 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97918 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97922 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97925 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97929 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97950 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97962 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97973 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97978 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97987 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97989 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97992 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97994 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98003 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98008 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98046 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98067 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98073 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98124 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98131 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98142 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98148 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98161 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98169 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98172 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98182 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98192 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98198 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98212 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98248 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98285 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98294 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98307 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98309 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98317 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98325 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98326 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98338 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98355 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98387 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98399 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98400 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98409 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98423 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98424 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98425 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98431 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90086 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64538 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72348 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98300 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-20585 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-78663 | NONE0 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74502 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80793 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68081 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72178 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72219 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72316 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80534 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90262 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98109 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98301 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98354 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-0537 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2024-56568 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98181 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-15213 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2018-17977 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68337 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80531 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89460 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98078 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98363 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-14304 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98101 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98273 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-41848 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74604 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-81005 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98411 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98412 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98416 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93117 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98286 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% 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-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56857 | NONE0 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97618 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98414 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-67693 | NONE0 | libgnutls30t64 3.8.12-2ubuntu1.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-88647 | NONE0 | libgnutls30t64 3.8.12-2ubuntu1.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-95184 | NONE0 | libgnutls30t64 3.8.12-2ubuntu1.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-95209 | NONE0 | libgnutls30t64 3.8.12-2ubuntu1.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-95210 | NONE0 | libgnutls30t64 3.8.12-2ubuntu1.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-107161 | NONE0 | libsasl2-2 2.1.28+dfsg1-9ubuntu3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107161 | NONE0 | libsasl2-modules-db 2.1.28+dfsg1-9ubuntu3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90037 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93221 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64580 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68083 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68199 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80883 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80891 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80905 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89788 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89803 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89805 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89810 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89907 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89913 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89922 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90003 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90048 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90057 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90167 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90169 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90375 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90380 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90392 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90398 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90417 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92499 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92507 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92509 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92510 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-92511 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-92512 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93105 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93148 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93154 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93175 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93176 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93210 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93792 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98084 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98085 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98171 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64532 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64533 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64568 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64581 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64584 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64585 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64586 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68082 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68095 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68097 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68120 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68151 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68177 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68179 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68192 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68213 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68220 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68221 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68223 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68225 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68230 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68302 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68327 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68340 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68359 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68361 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68476 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72092 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72140 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72306 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72378 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72501 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74433 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-34.34 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74545 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74564 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74691 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80555 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80729 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80730 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80731 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80732 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80733 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80734 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80735 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80736 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80737 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80739 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80740 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80741 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80742 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80743 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80744 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80745 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80748 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80749 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80750 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80751 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80752 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80753 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80754 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80756 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80757 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80758 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80759 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80760 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80761 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80762 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80763 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80765 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80766 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80767 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80768 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80769 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80770 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80771 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80772 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80774 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80776 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80777 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80779 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80781 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80782 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80783 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80787 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80789 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80790 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80791 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80794 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80795 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80796 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80798 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80799 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80800 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80801 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80802 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80803 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80804 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80805 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80806 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80807 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80808 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80809 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80812 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80813 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80814 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80815 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80816 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80817 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80818 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80819 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80823 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80825 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80826 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80827 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80828 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80829 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80830 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80831 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80832 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80833 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80834 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80835 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80836 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80838 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80839 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80845 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80846 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80847 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80854 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80857 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80858 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80859 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80860 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80861 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80862 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80865 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80866 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80867 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80868 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80870 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80871 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80873 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80874 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80875 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80876 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80879 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80880 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80881 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80882 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80886 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80888 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80889 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80890 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80892 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80893 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80894 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80895 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80896 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80900 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80901 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80904 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80906 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80907 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80908 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80909 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80910 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80911 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80912 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80913 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80914 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80915 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80916 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80917 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80918 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80920 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80922 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80923 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80924 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80925 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80926 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-81007 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89562 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89577 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89774 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89776 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89780 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89781 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89782 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89784 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89785 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89787 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89789 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89790 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89792 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89793 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89794 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89796 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89798 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89800 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89801 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89802 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89804 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89806 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89807 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89808 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89812 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89813 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89814 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89817 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89818 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89819 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89821 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89823 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89825 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89826 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89827 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89828 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89829 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89830 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89831 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89832 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89833 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89836 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89839 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89840 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89841 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89842 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89843 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89844 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89845 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89847 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89849 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89850 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89851 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89852 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89853 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89854 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89855 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89856 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89857 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89858 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89861 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89863 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89864 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89865 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89866 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89868 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89869 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89871 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89873 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89874 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89875 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89876 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89878 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89879 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89880 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89882 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89883 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89884 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89885 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89887 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89888 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89890 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89891 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89892 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89893 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89895 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89897 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89898 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89901 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89902 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89903 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89904 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89905 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89906 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89908 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89911 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89914 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89915 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89916 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89917 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89918 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89919 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89926 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89927 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89928 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89931 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89933 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89934 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89935 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89936 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89937 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89939 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89940 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89941 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89942 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89945 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89946 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89947 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89948 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89949 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89950 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89951 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89952 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89954 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89955 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89956 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89957 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89958 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89959 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89961 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89963 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89964 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89966 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89967 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89968 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-89969 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89971 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89973 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89974 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89976 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89977 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89978 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89979 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89981 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89983 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89984 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89986 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89987 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89989 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89990 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89991 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89992 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89993 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89994 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89995 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89997 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89999 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90000 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90001 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90006 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90012 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90014 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90016 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90017 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90018 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90019 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90020 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90024 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90025 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90026 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90028 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90029 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90030 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90031 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90032 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90033 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90034 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90035 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90039 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90040 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90041 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90042 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90043 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90046 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90047 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90153 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90156 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90329 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90350 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90353 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90355 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90356 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90357 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90358 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90360 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90366 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90368 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90369 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90370 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90371 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90372 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90373 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90374 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90376 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90377 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90381 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90382 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90386 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90387 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90388 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90391 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90393 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90394 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90395 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90396 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90397 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90399 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90400 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90403 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90406 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90409 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90412 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90413 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-90416 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90419 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90420 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90423 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90425 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90426 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90428 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90429 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90430 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90431 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90435 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-92476 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92477 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92479 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92480 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92483 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92484 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92485 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92486 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92489 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-92490 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92491 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92495 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92496 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92497 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92498 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92500 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92501 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92502 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92503 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92505 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92506 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92508 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92513 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92514 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92515 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92516 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92517 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92518 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92520 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92521 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92522 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-92523 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92525 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93037 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93039 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93040 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93041 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93043 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93044 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93045 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93046 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93048 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93049 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93051 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93052 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93053 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93054 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93055 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93061 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93063 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93064 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93065 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93066 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93067 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93068 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93069 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93070 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93073 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93077 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93078 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93079 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93080 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93084 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93085 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93086 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93092 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93094 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93095 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93096 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93097 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93098 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93103 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93106 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93107 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93108 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93109 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93110 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93113 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93114 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93115 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93118 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93119 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93120 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93121 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93127 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93131 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93132 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93133 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93134 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93135 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93137 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93138 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93140 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93141 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93143 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93149 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93152 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93153 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93156 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93157 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93158 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93160 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93162 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93164 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93165 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93167 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93169 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93170 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93173 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93174 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93177 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93178 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93179 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93180 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93182 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93183 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93184 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93206 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93208 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93209 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93211 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93212 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93213 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93214 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93215 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93217 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93218 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93219 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93220 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93222 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93223 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93224 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93226 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93227 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93229 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93233 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93234 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93236 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93238 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93241 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93242 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93243 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93244 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93245 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93247 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93248 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93249 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93250 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93252 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93253 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93255 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93256 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93258 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93259 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93781 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93783 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93784 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93797 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97445 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97449 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97450 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97452 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97453 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97454 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97520 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97550 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97568 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97605 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98004 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98076 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98077 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98079 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98081 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98083 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98086 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98088 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98089 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98090 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98091 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98093 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98094 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98095 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98096 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98097 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98098 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98099 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98232 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98274 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98275 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98316 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54105 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46055 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64583 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68124 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68203 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68280 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68303 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68314 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68370 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74690 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80738 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80747 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80755 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80764 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80785 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80786 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80820 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80822 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80851 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80872 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80884 | NONE0 | linux-libc-dev 7.0.0-31.31 fixed in 7.0.0-38.38 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80899 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89795 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89797 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89799 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89809 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89822 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89834 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89835 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89838 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89848 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89859 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89860 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89870 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89899 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89920 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89921 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89929 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89938 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89960 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89962 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89988 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89998 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90002 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90013 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90022 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90023 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90027 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90044 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90045 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90351 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90359 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90363 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90365 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90367 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90379 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90383 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90385 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90389 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90401 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90408 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90410 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90418 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90421 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90433 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92481 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92482 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93042 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-93047 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93050 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93058 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93062 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93081 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93091 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93093 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93099 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93100 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93104 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93122 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93123 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93128 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93129 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93142 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93146 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93150 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93155 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93163 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93168 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93172 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93181 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93205 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93216 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93230 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93231 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93235 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93237 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93239 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93240 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93251 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93260 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93810 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97447 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98102 | NONE0 | linux-libc-dev 7.0.0-31.31 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-35341 | NONE0 | rust-coreutils 0.8.0-0ubuntu3 No fix yet | 0.1% 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-85091 | NONE0 | zlib1g 1:1.3.dfsg+really1.3.1-1ubuntu3.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-78659 | NONE0 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94440 | NONE0 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97030 | NONE0 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.2% 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.
Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.