This image poses a critical security risk and must not be used in production, especially as an internet-facing service. An attacker could exploit authentication bypass in gnutls (CVE-2026-42010) or remote code execution in lodash (CVE-2026-4800) to gain unauthorized access to sensitive data or execute arbitrary code. Upgrading lodash to version 4.18.0 would fully address CVE-2026-4800, but the overall risk remains extreme due to numerous other high-severity vulnerabilities. Additionally, CVE-2026-4800 is only exploitable if the application passes user-controlled input to template imports, so reviewing application usage may reduce exposure.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-42010 | HIGH8.33 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-8376 | HIGH8.33 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | HIGH8.33 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.19-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-8376 | HIGH8.33 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-39892 | HIGH8.33 | cryptography 46.0.3 fixed in 46.0.7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2008-4609 | HIGH8.16 | linux-libc-dev 6.1.158-1 No fix yet | 32.1% High Exploitation Risk | Directly Exposed |
| CVE-2023-31486 | HIGH8.1 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45447 | HIGH8.1 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-31486 | HIGH8.1 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-4800 | HIGH7.84 | lodash 4.17.21 fixed in 4.18.0 | 1.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2017-7245 | HIGH7.8 | libpcre3 2:8.39-15 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7246 | HIGH7.8 | libpcre3 2:8.39-15 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2013-7445 | HIGH7.8 | linux-libc-dev 6.1.158-1 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19449 | HIGH7.8 | linux-libc-dev 6.1.158-1 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19814 | HIGH7.8 | linux-libc-dev 6.1.158-1 No fix yet | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-46300 | HIGH7.8 | linux-libc-dev 6.1.158-1 fixed in 6.1.174-1 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-46333 | HIGH7.8 | linux-libc-dev 6.1.158-1 fixed in 6.1.172-1 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19378 | HIGH7.8 | linux-libc-dev 6.1.158-1 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25265 | HIGH7.8 | linux-libc-dev 6.1.158-1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33845 | HIGH7.73 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | HIGH7.73 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-7458 | HIGH7.73 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | HIGH7.73 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | HIGH7.73 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56208 | HIGH7.6 | libaom3 3.6.0-1+deb12u2 No fix yet | — | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-bin 2.36-9+deb12u13 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-bin 2.36-9+deb12u13 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-devtools 2.36-9+deb12u13 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-devtools 2.36-9+deb12u13 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6 2.36-9+deb12u13 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6 2.36-9+deb12u13 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6-dev 2.36-9+deb12u13 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6-dev 2.36-9+deb12u13 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28757 | HIGH7.5 | libexpat1 2.5.0-1+deb12u2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2018-6829 | HIGH7.5 | libgcrypt20 1.10.1-3 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libgssapi-krb5-2 1.20.1-2+deb12u4 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-36325 | HIGH7.5 | libjansson4 2.14-2 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libk5crypto3 1.20.1-2+deb12u4 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5-3 1.20.1-2+deb12u4 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5support0 1.20.1-2+deb12u4 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2953 | HIGH7.5 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2015-3276 | HIGH7.5 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | HIGH7.5 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11164 | HIGH7.5 | libpcre3 2:8.39-15 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20838 | HIGH7.5 | libpcre3 2:8.39-15 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33416 | HIGH7.5 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+deb12u4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13836 | HIGH7.5 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13836 | HIGH7.5 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-52355 | HIGH7.5 | libtiff6 4.5.0-6+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2017-16232 | HIGH7.5 | libtiff6 4.5.0-6+deb12u3 No fix yet | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19070 | HIGH7.5 | linux-libc-dev 6.1.158-1 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0400 | HIGH7.5 | linux-libc-dev 6.1.158-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-32740 | HIGH7.48 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-49463 | HIGH7.48 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-43037 | HIGH7.48 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-23395 | HIGH7.48 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56209 | HIGH7.1 | libaom3 3.6.0-1+deb12u2 No fix yet | — | Directly Exposed |
| CVE-2026-56210 | HIGH7.1 | libaom3 3.6.0-1+deb12u2 No fix yet | — | Directly Exposed |
| CVE-2026-56211 | HIGH7.1 | libaom3 3.6.0-1+deb12u2 No fix yet | — | Directly Exposed |
| CVE-2026-42013 | MEDIUM6.97 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM6.97 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-31788 | MEDIUM6.97 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-39191 | MEDIUM6.97 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc-dev-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc-devtools 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc6 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc6-dev 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41071 | MEDIUM6.88 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25646 | MEDIUM6.88 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+deb12u3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-6100 | MEDIUM6.88 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6100 | MEDIUM6.88 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.19-1~deb12u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25210 | MEDIUM6.63 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48962 | MEDIUM6.63 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22801 | MEDIUM6.63 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | libsystemd0 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4775 | MEDIUM6.63 | libtiff6 4.5.0-6+deb12u3 fixed in 4.5.0-6+deb12u4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8176 | MEDIUM6.63 | libtiff6 4.5.0-6+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8177 | MEDIUM6.63 | libtiff6 4.5.0-6+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-3847 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-52452 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52624 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-52751 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53218 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53510 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-54285 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-21803 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-26836 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26913 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26914 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26944 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35887 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38570 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38630 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41045 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42118 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44941 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44942 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44951 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46729 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46786 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46811 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46813 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47691 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50029 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50217 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50226 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50282 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53068 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53168 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53179 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53218 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56538 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56775 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57900 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-58093 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21863 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21927 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21967 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21969 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22022 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22083 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23133 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37750 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37777 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37786 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37822 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37861 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37899 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-37926 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37952 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37957 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38022 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38069 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38117 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38129 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38182 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38201 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38206 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38248 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38250 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38349 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38361 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38369 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38582 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38584 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38585 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38593 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38595 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38627 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38704 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38718 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38722 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38734 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39797 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39810 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39859 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39863 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39871 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39952 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40149 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68817 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71068 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71071 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71073 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71075 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71078 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71082 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71086 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71089 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71091 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71123 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71137 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71152 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71162 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71220 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71238 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22980 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23001 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23010 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23025 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23068 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23073 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23074 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23078 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23083 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23089 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23098 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23111 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23156 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23171 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23193 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23208 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23209 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23216 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23221 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23226 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23227 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23231 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-23234 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23319 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23343 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23359 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23361 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23378 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23408 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23410 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23411 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23422 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23428 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23447 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23448 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31399 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31402 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-31452 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31455 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31485 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31488 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31489 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31493 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31500 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31527 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31532 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31566 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31576 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31578 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31580 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31581 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31583 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31686 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31696 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31702 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31709 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31715 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31720 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31729 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31747 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31748 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31759 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31787 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43015 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43020 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43027 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43049 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43128 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43150 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43196 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43205 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43250 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43328 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43378 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43426 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43458 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45946 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45984 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45996 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46004 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46047 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46163 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46180 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46189 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46219 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46234 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46241 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46243 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.174-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46267 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46323 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46331 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40258 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40277 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46274 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-12456 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-11725 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-26934 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3238 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-26242 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-3640 | MEDIUM6.63 | linux-libc-dev 6.1.158-1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-48962 | MEDIUM6.63 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-21759 | MEDIUM6.6 | linux-libc-dev 6.1.158-1 No fix yet | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libbinutils 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libctf-nobfd0 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libctf0 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libgprofng0 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2017-9937 | MEDIUM6.5 | libjbig0 2.1-6.1 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6277 | MEDIUM6.5 | libtiff6 4.5.0-6+deb12u3 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-10126 | MEDIUM6.5 | libtiff6 4.5.0-6+deb12u3 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1210 | MEDIUM6.5 | libtiff6 4.5.0-6+deb12u3 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2004-0230 | MEDIUM6.5 | linux-libc-dev 6.1.158-1 No fix yet | 80.9% Actively Exploited | Directly Exposed |
| CVE-2026-33636 | MEDIUM6.46 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+deb12u4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-39616 | MEDIUM6.38 | libaom3 3.6.0-1+deb12u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33164 | MEDIUM6.38 | libde265-0 1.0.11-1+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45186 | MEDIUM6.38 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-41989 | MEDIUM6.38 | libgcrypt20 1.10.1-3 fixed in 1.10.1-3+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-33846 | MEDIUM6.38 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-42009 | MEDIUM6.38 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-32316 | MEDIUM6.38 | libjq1 1.6-2.1+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40164 | MEDIUM6.38 | libjq1 1.6-2.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27135 | MEDIUM6.38 | libnghttp2-14 1.52.0-1+deb12u2 fixed in 1.52.0-1+deb12u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42497 | MEDIUM6.38 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM6.38 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69534 | MEDIUM6.38 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.38 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-8194 | MEDIUM6.38 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69534 | MEDIUM6.38 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.38 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-8194 | MEDIUM6.38 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM6.38 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.19-1~deb12u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM6.38 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.19-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.38 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.19-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22998 | MEDIUM6.38 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-43501 | MEDIUM6.38 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46195 | MEDIUM6.38 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-68349 | MEDIUM6.38 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31669 | MEDIUM6.38 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43110 | MEDIUM6.38 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43186 | MEDIUM6.38 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-43190 | MEDIUM6.38 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42497 | MEDIUM6.38 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM6.38 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69873 | MEDIUM6.38 | ajv 8.17.1 fixed in 8.18.0, 6.14.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33750 | MEDIUM6.38 | brace-expansion 1.1.12 fixed in 5.0.5, 3.0.2, 2.0.3, 1.1.13 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33750 | MEDIUM6.38 | brace-expansion 2.0.2 fixed in 5.0.5, 3.0.2, 2.0.3, 1.1.13 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6321 | MEDIUM6.38 | fast-uri 3.1.0 fixed in 3.1.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6322 | MEDIUM6.38 | fast-uri 3.1.0 fixed in 3.1.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-65945 | MEDIUM6.38 | jws 3.2.2 fixed in 3.2.3, 4.0.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-30952 | MEDIUM6.38 | liquidjs 10.6.1 fixed in 10.25.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-35525 | MEDIUM6.38 | liquidjs 10.6.1 fixed in 10.25.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39412 | MEDIUM6.38 | liquidjs 10.6.1 fixed in 10.25.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-26996 | MEDIUM6.38 | minimatch 3.1.2 fixed in 10.2.1, 9.0.6, 8.0.5, 7.4.7, 6.2.1, 5.1.7, 4.2.4, 3.1.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-26996 | MEDIUM6.38 | minimatch 5.1.6 fixed in 10.2.1, 9.0.6, 8.0.5, 7.4.7, 6.2.1, 5.1.7, 4.2.4, 3.1.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15284 | MEDIUM6.38 | qs 6.13.0 fixed in 6.14.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2391 | MEDIUM6.38 | qs 6.13.0 fixed in 6.14.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-41907 | MEDIUM6.38 | uuid 3.4.0 fixed in 11.1.1, 12.0.1, 13.0.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28356 | MEDIUM6.38 | multipart 1.3.0 fixed in 1.3.1, 1.2.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66418 | MEDIUM6.38 | urllib3 2.5.0 fixed in 2.6.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-66471 | MEDIUM6.38 | urllib3 2.5.0 fixed in 2.6.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-21441 | MEDIUM6.38 | urllib3 2.5.0 fixed in 2.6.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-65637 | MEDIUM6.38 | github.com/sirupsen/logrus v1.9.0 fixed in 1.8.3, 1.9.1, 1.9.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-22037 | MEDIUM6.32 | linux-libc-dev 6.1.158-1 No fix yet | 23.3% High Exploitation Risk | Directly Exposed |
| CVE-2026-3833 | MEDIUM6.29 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM6.29 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40170 | MEDIUM6.29 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-61144 | MEDIUM6.21 | libtiff6 4.5.0-6+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31607 | MEDIUM6.21 | linux-libc-dev 6.1.158-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-43038 | MEDIUM6.21 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-53781 | MEDIUM6.21 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39981 | MEDIUM6.21 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40269 | MEDIUM6.21 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40294 | MEDIUM6.21 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40304 | MEDIUM6.21 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68800 | MEDIUM6.21 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23243 | MEDIUM6.21 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43078 | MEDIUM6.21 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43248 | MEDIUM6.21 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM6.03 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68431 | MEDIUM6.03 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32741 | MEDIUM6.03 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32882 | MEDIUM6.03 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-64720 | MEDIUM6.03 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+deb12u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-65018 | MEDIUM6.03 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66293 | MEDIUM6.03 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+deb12u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22695 | MEDIUM6.03 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1299 | MEDIUM6.03 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1299 | MEDIUM6.03 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-26669 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41935 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53147 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57982 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21946 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21985 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22039 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22104 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22107 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22121 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38081 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38204 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38556 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38616 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38636 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39744 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39901 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40082 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71093 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71112 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71116 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71133 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71136 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22984 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23076 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23099 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23102 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23187 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23204 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23235 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23315 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23318 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23327 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23388 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23397 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31568 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31778 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43040 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43052 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43141 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43241 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43281 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43380 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43386 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43427 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43449 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43450 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43453 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45957 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45994 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46022 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46033 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46191 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-25742 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-25743 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36013 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-53216 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40064 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40301 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40322 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68168 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68183 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68324 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68347 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68366 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68724 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23455 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31613 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31685 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31786 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43051 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43126 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43414 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46053 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46056 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46120 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46135 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46150 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46209 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46259 | MEDIUM6.03 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4878 | MEDIUM5.95 | libcap2 1:2.66-4+deb12u2 fixed in 1:2.66-4+deb12u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-3864 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-52586 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42162 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37776 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40248 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68287 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71221 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23191 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23454 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31419 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31663 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43050 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43125 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43198 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43329 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43494 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43503 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.174-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45852 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45858 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45972 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46054 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46090 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46099 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46116 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46125 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46181 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46227 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46319 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46330 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53762 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57984 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40135 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40158 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40168 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40259 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40271 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-40318 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40328 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68285 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68301 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23050 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23270 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23392 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31408 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31508 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31586 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31694 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43023 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43116 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43158 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43226 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43233 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43303 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43304 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43334 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43339 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43341 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43491 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43493 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45840 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45856 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45859 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45860 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45886 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45892 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45894 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45899 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45912 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45934 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45942 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45970 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46015 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46043 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46052 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46069 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46119 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46123 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46132 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46133 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-46149 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46173 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46174 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.174-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46185 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46242 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46251 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46266 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46275 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46294 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46306 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46324 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-1247 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-2961 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-45884 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-45885 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23054 | MEDIUM5.95 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libbinutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libctf-nobfd0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libctf0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt20 1.10.1-3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libgprofng0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libgssapi-krb5-2 1.20.1-2+deb12u4 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libk5crypto3 1.20.1-2+deb12u4 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5-3 1.20.1-2+deb12u4 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5support0 1.20.1-2+deb12u4 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1-6 4.19.0-2+deb12u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-1121 | MEDIUM5.9 | linux-libc-dev 6.1.158-1 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3714 | MEDIUM5.9 | linux-libc-dev 6.1.158-1 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40345 | MEDIUM5.78 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68346 | MEDIUM5.78 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | libsystemd0 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2020-36694 | MEDIUM5.7 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-21264 | MEDIUM5.7 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53095 | MEDIUM5.7 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57795 | MEDIUM5.7 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21714 | MEDIUM5.7 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21739 | MEDIUM5.7 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40257 | MEDIUM5.7 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68237 | MEDIUM5.7 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.61 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-40261 | MEDIUM5.61 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45991 | MEDIUM5.61 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls30 3.7.9-2+deb12u5 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libbinutils 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.36-9+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc-dev-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc-devtools 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-devtools 2.36-9+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc6 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.36-9+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc6-dev 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6-dev 2.36-9+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libctf-nobfd0 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libctf0 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libgprofng0 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-32738 | MEDIUM5.52 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32739 | MEDIUM5.52 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32814 | MEDIUM5.52 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39979 | MEDIUM5.52 | libjq1 1.6-2.1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-23337 | MEDIUM5.52 | libjq1 1.6-2.1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15649 | MEDIUM5.52 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7774 | MEDIUM5.52 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7774 | MEDIUM5.52 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-68284 | MEDIUM5.52 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-6240 | MEDIUM5.52 | linux-libc-dev 6.1.158-1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-36968 | MEDIUM5.52 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40273 | MEDIUM5.52 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68354 | MEDIUM5.52 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68362 | MEDIUM5.52 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68380 | MEDIUM5.52 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31588 | MEDIUM5.52 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43239 | MEDIUM5.52 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-0564 | MEDIUM5.52 | linux-libc-dev 6.1.158-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-15649 | MEDIUM5.52 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-41311 | MEDIUM5.52 | liquidjs 10.6.1 fixed in 10.25.7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27904 | MEDIUM5.52 | minimatch 3.1.2 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-27904 | MEDIUM5.52 | minimatch 5.1.6 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-26007 | MEDIUM5.52 | cryptography 46.0.3 fixed in 46.0.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68146 | MEDIUM5.52 | filelock 3.20.0 fixed in 3.20.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libbinutils 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libbinutils 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libbinutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf-nobfd0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libctf-nobfd0 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libctf-nobfd0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libctf0 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libctf0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libgprofng0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libgprofng0 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libgprofng0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-4367 | MEDIUM5.5 | libxpm4 1:3.5.12-1.1+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2024-2193 | MEDIUM5.5 | linux-libc-dev 6.1.158-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-40225 | MEDIUM5.44 | libsystemd0 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | MEDIUM5.44 | libsystemd0 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40074 | MEDIUM5.44 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40309 | MEDIUM5.44 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40321 | MEDIUM5.44 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68371 | MEDIUM5.44 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23178 | MEDIUM5.44 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23383 | MEDIUM5.44 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23450 | MEDIUM5.44 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-23456 | MEDIUM5.44 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31502 | MEDIUM5.44 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31516 | MEDIUM5.44 | linux-libc-dev 6.1.158-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-44032 | MEDIUM5.44 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-44033 | MEDIUM5.44 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-44034 | MEDIUM5.44 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-3397 | MEDIUM5.35 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40307 | MEDIUM5.35 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68282 | MEDIUM5.35 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31504 | MEDIUM5.35 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-40918 | MEDIUM5.35 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-bin 2.36-9+deb12u13 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-bin 2.36-9+deb12u13 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-devtools 2.36-9+deb12u13 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-devtools 2.36-9+deb12u13 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6 2.36-9+deb12u13 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6 2.36-9+deb12u13 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6-dev 2.36-9+deb12u13 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6-dev 2.36-9+deb12u13 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-59375 | MEDIUM5.3 | libexpat1 2.5.0-1+deb12u2 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-28162 | MEDIUM5.27 | libpng16-16 1.6.39-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40146 | MEDIUM5.27 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68757 | MEDIUM5.27 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71066 | MEDIUM5.27 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23253 | MEDIUM5.27 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39956 | MEDIUM5.18 | libjq1 1.6-2.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-64506 | MEDIUM5.18 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+deb12u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-1916 | MEDIUM5.18 | libtiff6 4.5.0-6+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40071 | MEDIUM5.18 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40279 | MEDIUM5.18 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40355 | MEDIUM5.18 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68245 | MEDIUM5.18 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68342 | MEDIUM5.18 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68343 | MEDIUM5.18 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68736 | MEDIUM5.18 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68764 | MEDIUM5.18 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68815 | MEDIUM5.18 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68819 | MEDIUM5.18 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31449 | MEDIUM5.18 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31464 | MEDIUM5.18 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31505 | MEDIUM5.18 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31570 | MEDIUM5.18 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31700 | MEDIUM5.18 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31708 | MEDIUM5.18 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43134 | MEDIUM5.18 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42338 | MEDIUM5.18 | ip-address 10.0.1 fixed in 10.1.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31649 | MEDIUM5.1 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc-dev-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-devtools 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc-devtools 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc6 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6-dev 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc6-dev 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-32570 | MEDIUM5.02 | libdav1d6 1.0.0-2+deb12u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | MEDIUM5.02 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM5.02 | libgssapi-krb5-2 1.20.1-2+deb12u4 fixed in 1.20.1-2+deb12u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libgssapi-krb5-2 1.20.1-2+deb12u4 fixed in 1.20.1-2+deb12u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssapi-krb5-2 1.20.1-2+deb12u4 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM5.02 | libk5crypto3 1.20.1-2+deb12u4 fixed in 1.20.1-2+deb12u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libk5crypto3 1.20.1-2+deb12u4 fixed in 1.20.1-2+deb12u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libk5crypto3 1.20.1-2+deb12u4 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM5.02 | libkrb5-3 1.20.1-2+deb12u4 fixed in 1.20.1-2+deb12u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libkrb5-3 1.20.1-2+deb12u4 fixed in 1.20.1-2+deb12u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-3 1.20.1-2+deb12u4 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM5.02 | libkrb5support0 1.20.1-2+deb12u4 fixed in 1.20.1-2+deb12u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libkrb5support0 1.20.1-2+deb12u4 fixed in 1.20.1-2+deb12u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5support0 1.20.1-2+deb12u4 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.02 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.19-1~deb12u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-40083 | MEDIUM5.02 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40242 | MEDIUM5.02 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40324 | MEDIUM5.02 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-21717 | MEDIUM5.02 | nodejs 22.21.0-1nodesource1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41324 | MEDIUM5.02 | basic-ftp 5.0.5 fixed in 5.3.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27903 | MEDIUM5.02 | minimatch 3.1.2 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-27903 | MEDIUM5.02 | minimatch 5.1.6 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2010-4563 | MEDIUM5 | linux-libc-dev 6.1.158-1 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-53706 | MEDIUM4.93 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54107 | MEDIUM4.93 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54141 | MEDIUM4.93 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40214 | MEDIUM4.93 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40272 | MEDIUM4.93 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40323 | MEDIUM4.93 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68742 | MEDIUM4.93 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23239 | MEDIUM4.93 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23240 | MEDIUM4.93 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-23271 | MEDIUM4.93 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23317 | MEDIUM4.93 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31392 | MEDIUM4.93 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31414 | MEDIUM4.93 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31426 | MEDIUM4.93 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43279 | MEDIUM4.93 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46065 | MEDIUM4.93 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46113 | MEDIUM4.93 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6357 | MEDIUM4.93 | python3-pip-whl 23.0.1+dfsg-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45447 | MEDIUM4.86 | openssl 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | MEDIUM4.86 | perl-base 5.36.0-7+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-49569 | MEDIUM4.84 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40319 | MEDIUM4.84 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46024 | MEDIUM4.84 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-23039 | MEDIUM4.84 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-48384 | MEDIUM4.8 | git 1:2.39.5-0+deb12u2 fixed in 1:2.39.5-0+deb12u3 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1178 | MEDIUM4.76 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-68801 | MEDIUM4.76 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68816 | MEDIUM4.76 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-0630 | MEDIUM4.7 | linux-libc-dev 6.1.158-1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6110 | MEDIUM4.69 | openssh-client 1:9.2p1-2+deb12u7 No fix yet | 20.9% High Exploitation Risk | Post-Exploit |
| CVE-2007-0086 | MEDIUM4.68 | apache2-utils 2.4.65-1~deb12u1 No fix yet | 9.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27943 | MEDIUM4.67 | libasan8 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libatomic1 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libcc1-0 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32776 | MEDIUM4.67 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | MEDIUM4.67 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | MEDIUM4.67 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52426 | MEDIUM4.67 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc-12-dev 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgomp1 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libitm1 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-33947 | MEDIUM4.67 | libjq1 1.6-2.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41256 | MEDIUM4.67 | libjq1 1.6-2.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41257 | MEDIUM4.67 | libjq1 1.6-2.1+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43894 | MEDIUM4.67 | libjq1 1.6-2.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43896 | MEDIUM4.67 | libjq1 1.6-2.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44777 | MEDIUM4.67 | libjq1 1.6-2.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9403 | MEDIUM4.67 | libjq1 1.6-2.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40612 | MEDIUM4.67 | libjq1 1.6-2.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | liblsan0 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-16231 | MEDIUM4.67 | libpcre3 2:8.39-15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | MEDIUM4.67 | libpng16-16 1.6.39-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM4.67 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6075 | MEDIUM4.67 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM4.67 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6075 | MEDIUM4.67 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libquadmath0 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-29088 | MEDIUM4.67 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM4.67 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libstdc++-12-dev 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-3164 | MEDIUM4.67 | libtiff6 4.5.0-6+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6228 | MEDIUM4.67 | libtiff6 4.5.0-6+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61143 | MEDIUM4.67 | libtiff6 4.5.0-6+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libtsan2 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libubsan1 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40347 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68192 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68291 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68307 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-0597 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-23005 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31082 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-37454 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-4133 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52485 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52590 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52591 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52625 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52629 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52648 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52658 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52671 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52676 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52761 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52770 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52797 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52888 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52920 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53149 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53228 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53231 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53261 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53292 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53336 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53353 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53367 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53394 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53421 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53424 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53429 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53460 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53491 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53523 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53529 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53538 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53545 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53574 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53627 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53846 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53989 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53999 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54013 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54271 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54280 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-6039 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-25740 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26670 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26677 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26691 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26740 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26756 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26799 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26822 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26841 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26866 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26876 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26902 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26947 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26948 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26953 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26962 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27010 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27011 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27012 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27041 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27057 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27062 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27079 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35784 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35794 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35799 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35808 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35860 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35904 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35924 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35931 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35942 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35945 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35946 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35951 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35961 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36911 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36922 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36951 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38557 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38564 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38594 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38608 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38620 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38622 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38625 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40965 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40969 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40975 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40998 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40999 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41008 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41023 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41031 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41082 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42079 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42128 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42139 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42239 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42241 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42243 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42279 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42317 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43819 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43824 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43850 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43872 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-43899 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43901 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43913 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44963 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45015 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46678 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46681 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46698 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46727 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46728 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46730 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46754 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46760 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46765 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46775 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46776 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46806 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46808 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46834 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46860 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47141 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47658 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47661 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47662 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47664 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47666 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47703 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47736 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47752 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47794 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47809 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49568 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49893 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49901 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49906 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49908 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49910 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49914 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49916 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49918 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49919 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49920 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49921 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49922 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49923 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49926 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49940 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49945 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49968 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49970 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49988 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50009 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50017 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50028 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50111 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50166 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50285 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50289 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50298 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-52559 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-52560 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53051 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53056 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53079 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53085 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53089 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53090 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53091 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53094 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53114 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53134 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53187 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53195 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53219 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53221 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53224 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53687 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-54683 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56544 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56565 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56566 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56583 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56588 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56591 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56592 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56611 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56641 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56647 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56657 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56692 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56712 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56719 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56742 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57804 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57809 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57872 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57888 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57895 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57975 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57976 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57999 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58006 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58012 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58053 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58089 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58094 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58095 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58096 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58097 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58098 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58100 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58237 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58241 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21634 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21635 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21649 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21656 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21658 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21673 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21676 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21682 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21693 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21696 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21723 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21729 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21768 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21801 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21831 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21836 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21870 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21872 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21885 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21888 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21894 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21907 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21949 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21955 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21961 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21972 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21976 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22026 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22028 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22043 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22048 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22053 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22057 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22070 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22090 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22103 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22105 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22109 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22111 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22113 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22125 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22127 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23129 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23130 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23131 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23132 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23155 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37747 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37800 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37802 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37806 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37807 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37833 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37834 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37842 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37853 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37856 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37860 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37864 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37880 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37893 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37945 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37956 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37977 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37980 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38006 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38014 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38029 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38038 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38039 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38041 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38042 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38045 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38057 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38059 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38064 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38080 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38096 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38105 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38125 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38127 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38132 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38140 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38162 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38192 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38195 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38203 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38207 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38237 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38244 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38246 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38261 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38264 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38272 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38283 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38303 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38311 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38333 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38359 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38408 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38426 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38429 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38436 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38438 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38449 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38507 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38531 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38544 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38590 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38591 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38597 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38615 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38626 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38643 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38659 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38678 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38692 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38705 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38709 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38710 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38716 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39677 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39705 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39707 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39720 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39721 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39732 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39746 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39747 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39748 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39762 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39763 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39764 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39767 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39779 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39789 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39805 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39829 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39833 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39850 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39851 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39886 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39910 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39925 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39932 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39933 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39940 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39947 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39989 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40005 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40075 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40102 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40160 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40164 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40211 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40251 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40264 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40280 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40283 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40284 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40292 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40293 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40297 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40325 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40339 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40363 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68176 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68185 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68188 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68209 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68211 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68223 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68229 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68231 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68236 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68259 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68261 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68265 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68283 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68304 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68310 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68331 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68337 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68340 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68358 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68365 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68372 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68379 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68725 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68774 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68776 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68803 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68814 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68821 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68823 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71064 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71077 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71079 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71081 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71083 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71084 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71085 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71087 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71088 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71094 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71095 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71096 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71097 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71098 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71102 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71104 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71105 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71108 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71109 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71113 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71114 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71118 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71119 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71120 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71121 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71125 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71126 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71127 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71129 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71130 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71131 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71132 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71138 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71144 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71147 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71150 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71154 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71160 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71161 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71163 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71180 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71182 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71183 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71184 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71185 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71186 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71188 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71189 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71190 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71191 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71200 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71202 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71222 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71227 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71232 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71233 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71235 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71236 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71237 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71265 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71266 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71267 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71268 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71269 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71272 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71273 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71285 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71287 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71288 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71289 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71291 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71292 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71295 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71297 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71305 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71313 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22976 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22977 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22979 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22982 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22990 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22991 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-22992 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22994 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22996 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22997 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-22999 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23000 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23003 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-23005 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23006 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23011 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23019 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23020 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23021 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23026 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23031 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23038 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23047 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23058 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23060 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23061 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23063 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23064 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23066 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23069 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23075 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23080 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23084 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23085 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23086 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23087 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23088 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23090 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23091 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23093 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23095 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23096 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23097 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23100 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23103 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23105 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23107 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23108 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23113 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23116 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23119 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23120 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23121 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23124 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23125 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23128 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23133 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23137 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23138 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23139 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23140 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23141 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23142 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23144 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23145 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23146 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23150 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23154 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23157 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23164 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23168 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23170 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23172 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23190 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23198 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23202 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23205 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23206 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23213 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23214 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23220 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23222 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23228 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23229 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23230 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23236 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23237 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23238 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23242 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23247 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23255 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23256 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23257 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23258 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23262 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23264 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23265 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23266 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23267 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23272 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23273 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23274 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23276 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23277 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23278 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23279 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23284 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23286 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23287 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23289 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23290 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23291 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23292 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23293 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23296 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23298 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23300 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23303 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23304 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23306 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23307 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23310 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23312 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23321 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23324 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23330 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23335 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23336 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23339 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23340 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23346 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23351 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23352 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23356 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23357 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23362 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23365 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23367 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23368 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23370 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23371 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23374 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23379 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23381 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23382 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23389 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23391 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23396 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23398 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23399 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23401 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23403 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23404 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23405 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23409 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23414 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23419 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23420 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23426 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23434 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23438 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23439 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23442 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23444 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23446 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23449 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23460 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23462 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23465 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23468 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23472 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23474 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23475 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31391 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31400 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31403 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31407 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31410 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31411 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31412 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31415 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31416 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31418 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31420 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31421 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31422 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31423 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31424 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31425 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31427 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31428 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31434 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31441 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31446 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31447 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31448 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31450 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31451 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31453 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31454 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31458 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31462 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31467 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31469 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31473 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31480 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31483 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31487 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31492 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31495 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31496 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31497 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31498 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31503 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31507 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31509 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31510 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31512 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31515 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31518 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31519 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31520 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31521 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31522 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31524 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31531 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31533 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31537 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31540 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31545 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31546 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31548 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31549 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31550 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31551 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31552 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31555 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31557 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31560 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31565 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31577 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31579 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31585 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31590 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31592 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31594 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31595 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31596 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31599 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31603 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31605 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31606 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31610 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31615 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31616 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31617 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31618 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31619 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31623 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31624 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31625 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31628 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31630 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31634 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31637 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31642 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31648 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31651 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31655 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31658 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31660 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31661 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31662 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31664 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31665 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31667 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31670 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31671 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31672 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31673 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31674 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31675 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31676 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31677 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31678 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31679 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31680 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31681 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31682 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31684 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31687 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31689 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31692 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31698 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31699 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31701 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31704 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31721 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31722 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31723 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31724 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31725 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31726 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31737 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31738 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31749 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31752 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31754 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31755 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31756 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31758 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31762 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31763 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31767 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31770 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31771 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31773 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31777 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31779 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31781 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43009 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43010 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43013 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43014 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43016 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43017 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43018 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43022 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43024 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43025 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43026 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43028 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43032 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43033 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43035 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43036 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43041 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43042 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43043 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43046 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43048 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43054 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43057 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43058 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43060 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43061 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43062 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43064 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43065 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43066 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43068 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43069 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43071 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43072 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43073 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43077 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43079 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43080 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43083 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43085 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43088 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43089 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43091 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43093 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43094 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43098 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43099 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43101 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43103 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43104 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43105 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43107 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43111 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43112 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43113 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43114 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43115 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43118 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43119 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43123 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43124 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43129 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43130 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43132 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43133 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43135 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43136 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43137 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43139 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43140 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43143 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43145 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43147 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43148 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43149 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43152 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43153 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43156 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43157 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43159 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43161 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43162 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43167 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43168 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43170 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43171 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43172 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43173 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43180 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43182 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43183 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43187 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43200 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43202 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43204 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43209 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43213 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43214 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43215 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43216 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43218 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43219 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43221 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43223 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43225 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43227 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43230 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43231 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43234 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43238 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43240 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43242 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43244 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43246 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43251 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43252 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43255 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43257 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43261 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43262 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43264 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43265 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43266 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43268 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43269 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43270 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43271 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43273 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43277 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43278 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43287 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43288 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43289 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43295 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43296 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43299 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43302 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43308 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43309 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43310 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43312 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43313 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43314 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43315 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43316 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43317 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43318 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43327 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43333 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43338 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43340 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43343 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43344 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43350 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43352 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43353 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43355 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43357 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43359 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43360 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43361 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43362 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43363 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43365 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43366 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43381 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43382 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43387 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43405 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43406 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43407 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43409 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43411 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43412 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43413 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43416 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43420 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43421 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43424 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43425 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43428 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43429 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43432 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43436 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43437 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43441 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43443 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43445 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43451 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43452 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43455 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43456 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43457 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43459 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43466 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43468 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43469 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43472 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43473 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43475 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43492 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43502 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45834 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45835 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45836 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45838 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45841 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45842 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45843 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45844 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45846 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45855 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45857 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45862 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45891 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45914 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45943 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45944 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45948 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45954 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45960 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45961 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45962 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45963 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45964 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45965 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45968 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45969 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45974 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45978 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45981 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45982 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45983 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45985 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45986 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45987 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45988 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45993 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45997 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45999 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46000 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46002 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46003 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46005 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46009 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46012 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46014 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46018 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46019 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46021 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46023 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46026 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46027 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46028 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46032 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46037 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46038 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46040 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46044 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46046 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46049 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46050 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46051 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46059 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46064 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46070 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46078 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46079 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46082 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46086 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46102 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46107 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46111 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46127 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46130 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46137 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46146 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46147 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46148 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46151 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46153 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46156 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46157 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46158 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46160 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46161 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46165 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46167 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46168 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46169 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46170 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46172 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46179 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46184 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46186 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46190 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46193 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46196 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46200 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46214 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46220 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46225 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46226 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46229 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46231 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46233 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46235 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46236 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46245 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46247 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46249 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46252 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46253 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46254 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46262 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46273 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46280 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46291 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46304 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46307 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46312 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46320 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46321 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46322 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2008-2544 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2011-4915 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2011-4916 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2011-4917 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2014-9892 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2014-9900 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2016-10723 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-8660 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-13693 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-13694 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-12928 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12378 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12379 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12380 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-12381 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12382 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-12455 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-4543 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-31081 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31085 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-4134 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52653 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-53823 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53857 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54030 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-54088 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35843 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39990 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40057 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40196 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40219 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40253 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40360 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68171 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68173 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68194 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68200 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68204 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68206 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68218 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68219 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68227 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68233 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68244 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68288 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68295 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68308 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68321 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68334 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68336 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68345 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68363 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68378 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68732 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68734 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68753 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68758 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68778 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68780 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68783 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68785 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68794 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68795 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68798 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68813 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68818 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68820 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68822 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71194 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71315 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31486 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43030 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43194 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43211 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43253 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43419 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43483 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43484 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43496 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45847 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45868 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45870 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45871 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45872 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45873 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45877 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45897 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45901 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45904 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45905 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45911 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45915 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45917 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45919 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45920 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45923 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45941 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46068 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46071 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46083 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46088 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46092 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46101 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46103 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46136 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46178 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46292 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46299 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46302 | MEDIUM4.67 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-8643 | MEDIUM4.67 | python3-pip-whl 23.0.1+dfsg-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25645 | MEDIUM4.67 | requests 2.32.5 fixed in 2.33.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7598 | MEDIUM4.64 | libssh2-1 1.10.0-3+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | MEDIUM4.64 | openssl 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-49975 | MEDIUM4.5 | apache2-utils 2.4.65-1~deb12u1 fixed in 2.4.67-1~deb12u3 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-24975 | MEDIUM4.5 | git 1:2.39.5-0+deb12u2 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3497 | MEDIUM4.5 | openssh-client 1:9.2p1-2+deb12u7 fixed in 1:9.2p1-2+deb12u9 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6951 | MEDIUM4.5 | patch 2.7.6-7 No fix yet | 8.9% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6952 | MEDIUM4.5 | patch 2.7.6-7 No fix yet | 8.7% Low-Moderate Risk | Post-Exploit |
| CVE-2025-13836 | MEDIUM4.5 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-13836 | MEDIUM4.5 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-13836 | MEDIUM4.5 | python3.11-venv 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1147 | MEDIUM4.5 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc-dev-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-dev-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc-devtools 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-devtools 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc6 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc6-dev 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6-dev 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-14831 | MEDIUM4.5 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM4.5 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33948 | MEDIUM4.5 | libjq1 1.6-2.1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | liblzma5 5.4.1-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-12087 | MEDIUM4.5 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3713 | MEDIUM4.5 | libpng16-16 1.6.39-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12084 | MEDIUM4.5 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3446 | MEDIUM4.5 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-12084 | MEDIUM4.5 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3446 | MEDIUM4.5 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | libssl3 3.0.17-1~deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 252.39-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 252.39-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 252.39-1~deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-8851 | MEDIUM4.5 | libtiff6 4.5.0-6+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-36881 | MEDIUM4.5 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68367 | MEDIUM4.5 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71225 | MEDIUM4.5 | linux-libc-dev 6.1.158-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23457 | MEDIUM4.5 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-12087 | MEDIUM4.5 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8869 | MEDIUM4.5 | python3-pip-whl 23.0.1+dfsg-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34166 | MEDIUM4.5 | liquidjs 10.6.1 fixed in 10.25.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-13465 | MEDIUM4.5 | lodash 4.17.21 fixed in 4.17.23 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-2950 | MEDIUM4.5 | lodash 4.17.21 fixed in 4.18.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4867 | MEDIUM4.5 | path-to-regexp 0.1.12 fixed in 0.1.13 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34073 | MEDIUM4.5 | cryptography 46.0.3 fixed in 46.0.6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22701 | MEDIUM4.5 | filelock 3.20.0 fixed in 3.20.3 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45409 | MEDIUM4.5 | idna 3.11 fixed in 3.15 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27448 | MEDIUM4.5 | pyOpenSSL 25.3.0 fixed in 26.0.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44431 | MEDIUM4.5 | urllib3 2.5.0 fixed in 2.7.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-52005 | MEDIUM4.49 | git 1:2.39.5-0+deb12u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-40338 | MEDIUM4.42 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40343 | MEDIUM4.42 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4516 | MEDIUM4.33 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4516 | MEDIUM4.33 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71193 | MEDIUM4.33 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23035 | MEDIUM4.33 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-45346 | MEDIUM4.3 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-58098 | MEDIUM4.26 | apache2-utils 2.4.65-1~deb12u1 fixed in 2.4.66-1~deb12u1 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-57360 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.36-9+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.36-9+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-devtools 2.36-9+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-devtools 2.36-9+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.36-9+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.36-9+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6-dev 2.36-9+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6-dev 2.36-9+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33165 | MEDIUM4.25 | libde265-0 1.0.11-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libgssapi-krb5-2 1.20.1-2+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libk5crypto3 1.20.1-2+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5-3 1.20.1-2+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5support0 1.20.1-2+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48959 | MEDIUM4.25 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48961 | MEDIUM4.25 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-28164 | MEDIUM4.25 | libpng16-16 1.6.39-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM4.25 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61145 | MEDIUM4.25 | libtiff6 4.5.0-6+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23180 | MEDIUM4.25 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48959 | MEDIUM4.25 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48961 | MEDIUM4.25 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3219 | MEDIUM4.25 | python3-pip-whl 23.0.1+dfsg-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-48385 | MEDIUM4.23 | git 1:2.39.5-0+deb12u2 fixed in 1:2.39.5-0+deb12u3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2020-15719 | MEDIUM4.2 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34032 | MEDIUM4.18 | apache2-utils 2.4.65-1~deb12u1 fixed in 2.4.67-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34059 | MEDIUM4.18 | apache2-utils 2.4.65-1~deb12u1 fixed in 2.4.67-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-24842 | MEDIUM4.18 | tar 6.2.1 fixed in 7.5.7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2005-3660 | MEDIUM4.17 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-28780 | MEDIUM4.13 | apache2-utils 2.4.65-1~deb12u1 fixed in 2.4.67-1~deb12u2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | curl 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-35385 | MEDIUM4.13 | openssh-client 1:9.2p1-2+deb12u7 fixed in 1:9.2p1-2+deb12u10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-35386 | MEDIUM4.13 | openssh-client 1:9.2p1-2+deb12u7 fixed in 1:9.2p1-2+deb12u10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-35414 | MEDIUM4.13 | openssh-client 1:9.2p1-2+deb12u7 fixed in 1:9.2p1-2+deb12u10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-28387 | MEDIUM4.13 | openssl 3.0.17-1~deb12u3 fixed in 3.0.19-1~deb12u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | MEDIUM4.13 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | MEDIUM4.13 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | MEDIUM4.13 | python3.11-venv 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | MEDIUM4.08 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.08 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | MEDIUM4.08 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.08 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15467 | MEDIUM4.06 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 48.7% High Exploitation Risk | Post-Exploit |
| CVE-2025-15467 | MEDIUM4.06 | openssl 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 48.7% High Exploitation Risk | Post-Exploit |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | MEDIUM4 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-20794 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-52771 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53447 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-24864 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26869 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27408 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36024 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36949 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39508 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42107 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46787 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46870 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-49998 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50135 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53176 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53178 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56729 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57857 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57974 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21651 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21732 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21825 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21892 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22115 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37920 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38104 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38232 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38234 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38524 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38717 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39726 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39754 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39927 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39961 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40016 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40039 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40110 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40139 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40215 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40252 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40254 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40331 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40342 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68214 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68239 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68241 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68296 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68312 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68745 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71074 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71111 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71274 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23004 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23071 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23101 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23110 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23118 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23126 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23167 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23169 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23207 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23212 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23302 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23348 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23394 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23452 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23463 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31389 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31393 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31466 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31523 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31697 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31728 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31751 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43047 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43053 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43163 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43275 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43342 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43383 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43430 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43439 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43448 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45949 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46017 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46159 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46187 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-16230 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16234 | MEDIUM4 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-68264 | MEDIUM4 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-bin 2.36-9+deb12u13 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-devtools 2.36-9+deb12u13 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.36-9+deb12u13 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6-dev 2.36-9+deb12u13 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-11082 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-44631 | LOW3.93 | apache2-utils 2.4.65-1~deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2019-15213 | LOW3.91 | linux-libc-dev 6.1.158-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4010 | LOW3.91 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2012-4542 | LOW3.91 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | LOW3.9 | binutils 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20712 | LOW3.9 | binutils-common 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20712 | LOW3.9 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2008-3234 | LOW3.9 | openssh-client 1:9.2p1-2+deb12u7 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2025-55753 | LOW3.82 | apache2-utils 2.4.65-1~deb12u1 fixed in 2.4.66-1~deb12u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34355 | LOW3.82 | apache2-utils 2.4.65-1~deb12u1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42536 | LOW3.82 | apache2-utils 2.4.65-1~deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-29168 | LOW3.82 | apache2-utils 2.4.65-1~deb12u1 fixed in 2.4.67-1~deb12u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-33857 | LOW3.82 | apache2-utils 2.4.65-1~deb12u1 fixed in 2.4.67-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34356 | LOW3.82 | apache2-utils 2.4.65-1~deb12u1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-29169 | LOW3.82 | apache2-utils 2.4.65-1~deb12u1 fixed in 2.4.67-1~deb12u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-0840 | LOW3.82 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW3.82 | binutils 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-0840 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-0840 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | curl 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | curl 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-32316 | LOW3.82 | jq 1.6-2.1+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-40164 | LOW3.82 | jq 1.6-2.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69421 | LOW3.82 | openssl 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28388 | LOW3.82 | openssl 3.0.17-1~deb12u3 fixed in 3.0.19-1~deb12u2 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-28389 | LOW3.82 | openssl 3.0.17-1~deb12u3 fixed in 3.0.19-1~deb12u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28390 | LOW3.82 | openssl 3.0.17-1~deb12u3 fixed in 3.0.19-1~deb12u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69534 | LOW3.82 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3644 | LOW3.82 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW3.82 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW3.82 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-8194 | LOW3.82 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-69534 | LOW3.82 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3644 | LOW3.82 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW3.82 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW3.82 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-8194 | LOW3.82 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-69534 | LOW3.82 | python3.11-venv 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3644 | LOW3.82 | python3.11-venv 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW3.82 | python3.11-venv 3.11.2-6+deb12u6 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW3.82 | python3.11-venv 3.11.2-6+deb12u6 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-8194 | LOW3.82 | python3.11-venv 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-11468 | LOW3.82 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0865 | LOW3.82 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | LOW3.82 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0865 | LOW3.82 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-40308 | LOW3.82 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40312 | LOW3.82 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | LOW3.77 | openssl 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW3.77 | openssl 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43895 | LOW3.74 | libjq1 1.6-2.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-64505 | LOW3.74 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34757 | LOW3.74 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+deb12u5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2020-14304 | LOW3.74 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-54263 | LOW3.74 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42123 | LOW3.74 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40206 | LOW3.74 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40281 | LOW3.74 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68768 | LOW3.74 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-17977 | LOW3.74 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26661 | LOW3.74 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26662 | LOW3.74 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26672 | LOW3.74 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26757 | LOW3.74 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26758 | LOW3.74 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26768 | LOW3.74 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23458 | LOW3.74 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-44185 | LOW3.72 | apache2-utils 2.4.65-1~deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW3.7 | libapt-pkg6.0 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31431 | LOW3.65 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 75.5% Actively Exploited | Post-Exploit |
| CVE-2026-43284 | LOW3.65 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-3 | 92.2% Actively Exploited | Post-Exploit |
| CVE-2026-43500 | LOW3.65 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-3 | 94.0% Actively Exploited | Post-Exploit |
| CVE-2025-6069 | LOW3.65 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-8291 | LOW3.65 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6069 | LOW3.65 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-8291 | LOW3.65 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2010-5321 | LOW3.65 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40275 | LOW3.65 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | LOW3.62 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW3.62 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW3.62 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1299 | LOW3.62 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW3.62 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW3.62 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1299 | LOW3.62 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW3.62 | python3.11-venv 3.11.2-6+deb12u6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW3.62 | python3.11-venv 3.11.2-6+deb12u6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1299 | LOW3.62 | python3.11-venv 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-26960 | LOW3.62 | tar 6.2.1 fixed in 7.5.8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2005-2541 | LOW3.6 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | dirmngr 2.2.40-1.1+deb12u1 fixed in 2.2.40-1.1+deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gnupg 2.2.40-1.1+deb12u1 fixed in 2.2.40-1.1+deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gnupg-utils 2.2.40-1.1+deb12u1 fixed in 2.2.40-1.1+deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gpg 2.2.40-1.1+deb12u1 fixed in 2.2.40-1.1+deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gpg-agent 2.2.40-1.1+deb12u1 fixed in 2.2.40-1.1+deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gpg-wks-client 2.2.40-1.1+deb12u1 fixed in 2.2.40-1.1+deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gpg-wks-server 2.2.40-1.1+deb12u1 fixed in 2.2.40-1.1+deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gpgconf 2.2.40-1.1+deb12u1 fixed in 2.2.40-1.1+deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gpgsm 2.2.40-1.1+deb12u1 fixed in 2.2.40-1.1+deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gpgv 2.2.40-1.1+deb12u1 fixed in 2.2.40-1.1+deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-41848 | LOW3.57 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | LOW3.54 | binutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils-common 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2020-14145 | LOW3.54 | openssh-client 1:9.2p1-2+deb12u7 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2023-6879 | LOW3.53 | libaom3 3.6.0-1+deb12u2 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-bin 2.36-9+deb12u13 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-devtools 2.36-9+deb12u13 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6 2.36-9+deb12u13 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6-dev 2.36-9+deb12u13 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-45853 | LOW3.53 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2010-4651 | LOW3.48 | patch 2.7.6-7 No fix yet | 4.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-16089 | LOW3.48 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-42156 | LOW3.48 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42158 | LOW3.48 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-16229 | LOW3.48 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16231 | LOW3.48 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16232 | LOW3.48 | linux-libc-dev 6.1.158-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-16233 | LOW3.48 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-1965 | LOW3.47 | curl 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | curl 7.88.1-10+deb12u14 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-4438 | LOW3.4 | libc-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc-dev-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc-devtools 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc6 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc6-dev 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9820 | LOW3.4 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW3.4 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3449 | LOW3.4 | @tootallnate/once 1.1.2 fixed in 3.0.1, 2.0.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | LOW3.37 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53589 | LOW3.37 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53589 | LOW3.37 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-65082 | LOW3.31 | apache2-utils 2.4.65-1~deb12u1 fixed in 2.4.66-1~deb12u1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-33523 | LOW3.31 | apache2-utils 2.4.65-1~deb12u1 fixed in 2.4.67-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42535 | LOW3.31 | apache2-utils 2.4.65-1~deb12u1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-43951 | LOW3.31 | apache2-utils 2.4.65-1~deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils 2.40-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2016-2781 | LOW3.31 | coreutils 9.1-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | curl 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | curl 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | curl 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | curl 7.88.1-10+deb12u14 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-39979 | LOW3.31 | jq 1.6-2.1+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-23337 | LOW3.31 | jq 1.6-2.1+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-35387 | LOW3.31 | openssh-client 1:9.2p1-2+deb12u7 fixed in 1:9.2p1-2+deb12u10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl 5.36.0-7+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-7774 | LOW3.31 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7774 | LOW3.31 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7774 | LOW3.31 | python3.11-venv 3.11.2-6+deb12u6 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-1703 | LOW3.31 | python3-pip-whl 23.0.1+dfsg-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | LOW3.3 | binutils 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-common 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils-common 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils-common 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2379 | LOW3.24 | curl 7.88.1-10+deb12u14 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2379 | LOW3.24 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2379 | LOW3.24 | libcurl4 7.88.1-10+deb12u14 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-5958 | LOW3.21 | sed 4.9-1 fixed in 4.9-1+deb12u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-29786 | LOW3.21 | tar 6.2.1 fixed in 7.5.10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2016-20012 | LOW3.18 | openssh-client 1:9.2p1-2+deb12u7 No fix yet | 5.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-15919 | LOW3.18 | openssh-client 1:9.2p1-2+deb12u7 No fix yet | 3.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-23918 | LOW3.17 | apache2-utils 2.4.65-1~deb12u1 fixed in 2.4.67-1~deb12u2 | 6.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-bin 2.36-9+deb12u13 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-dev-bin 2.36-9+deb12u13 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-devtools 2.36-9+deb12u13 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6 2.36-9+deb12u13 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6-dev 2.36-9+deb12u13 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-6345 | LOW3.17 | setuptools 66.1.1 fixed in 70.0.0 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2025-47273 | LOW3.17 | setuptools 66.1.1 fixed in 78.1.1 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1152 | LOW3.15 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-41080 | LOW3.15 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5419 | LOW3.15 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.11 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-39956 | LOW3.11 | jq 1.6-2.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.11 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.11 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.11 | python3.11-venv 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23745 | LOW3.11 | tar 6.2.1 fixed in 7.5.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2020-15778 | LOW3.07 | openssh-client 1:9.2p1-2+deb12u7 No fix yet | 13.0% High Exploitation Risk | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | curl 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31790 | LOW3.01 | openssl 3.0.17-1~deb12u3 fixed in 3.0.19-1~deb12u2 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2025-69420 | LOW3.01 | openssl 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-22796 | LOW3.01 | openssl 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW3.01 | openssl 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.01 | openssl 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9669 | LOW3.01 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9669 | LOW3.01 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9669 | LOW3.01 | python3.11-venv 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-23950 | LOW3.01 | tar 6.2.1 fixed in 7.5.4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23112 | LOW3 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31789 | LOW3 | openssl 3.0.17-1~deb12u3 fixed in 3.0.19-1~deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-27699 | LOW3 | basic-ftp 5.0.5 fixed in 5.2.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-27459 | LOW3 | pyOpenSSL 25.3.0 fixed in 26.0.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2018-1000021 | LOW3 | git 1:2.39.5-0+deb12u2 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2007-2243 | LOW3 | openssh-client 1:9.2p1-2+deb12u7 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-6357 | LOW2.96 | pip 25.3 fixed in 26.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-31486 | LOW2.92 | perl 5.36.0-7+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | curl 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2020-35501 | LOW2.89 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68740 | LOW2.89 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | LOW2.86 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-24072 | LOW2.8 | apache2-utils 2.4.65-1~deb12u1 fixed in 2.4.67-1~deb12u2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-44119 | LOW2.8 | apache2-utils 2.4.65-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | cpp-12 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | g++-12 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | gcc-12 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-33947 | LOW2.8 | jq 1.6-2.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41256 | LOW2.8 | jq 1.6-2.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41257 | LOW2.8 | jq 1.6-2.1+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43894 | LOW2.8 | jq 1.6-2.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43896 | LOW2.8 | jq 1.6-2.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-44777 | LOW2.8 | jq 1.6-2.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-9403 | LOW2.8 | jq 1.6-2.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-40612 | LOW2.8 | jq 1.6-2.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-22795 | LOW2.8 | openssl 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW2.8 | openssl 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-45261 | LOW2.8 | patch 2.7.6-7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-13837 | LOW2.8 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6075 | LOW2.8 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-13837 | LOW2.8 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6075 | LOW2.8 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-13837 | LOW2.8 | python3.11-venv 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6075 | LOW2.8 | python3.11-venv 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31802 | LOW2.8 | tar 6.2.1 fixed in 7.5.11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-24049 | LOW2.8 | wheel 0.45.1 fixed in 0.46.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3949 | LOW2.8 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW2.8 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.8 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.8 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 252.39-1~deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 252.39-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8961 | LOW2.8 | libtiff6 4.5.0-6+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9165 | LOW2.8 | libtiff6 4.5.0-6+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68191 | LOW2.8 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2015-2877 | LOW2.8 | linux-libc-dev 6.1.158-1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-54227 | LOW2.8 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54233 | LOW2.8 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54322 | LOW2.8 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50057 | LOW2.8 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50211 | LOW2.8 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40268 | LOW2.8 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40303 | LOW2.8 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40341 | LOW2.8 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68746 | LOW2.8 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68782 | LOW2.8 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71224 | LOW2.8 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22978 | LOW2.8 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31668 | LOW2.8 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW2.8 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-5752 | LOW2.8 | python3-pip-whl 23.0.1+dfsg-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-66200 | LOW2.75 | apache2-utils 2.4.65-1~deb12u1 fixed in 2.4.66-1~deb12u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-29170 | LOW2.75 | apache2-utils 2.4.65-1~deb12u1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-33007 | LOW2.7 | apache2-utils 2.4.65-1~deb12u1 fixed in 2.4.67-1~deb12u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | curl 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | curl 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | curl 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-33948 | LOW2.7 | jq 1.6-2.1+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-61984 | LOW2.7 | openssh-client 1:9.2p1-2+deb12u7 fixed in 1:9.2p1-2+deb12u8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-61985 | LOW2.7 | openssh-client 1:9.2p1-2+deb12u7 fixed in 1:9.2p1-2+deb12u8 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-42766 | LOW2.7 | openssl 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42767 | LOW2.7 | openssl 3.0.17-1~deb12u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-12084 | LOW2.7 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW2.7 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW2.7 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3446 | LOW2.7 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-12084 | LOW2.7 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW2.7 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW2.7 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3446 | LOW2.7 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-12084 | LOW2.7 | python3.11-venv 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW2.7 | python3.11-venv 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW2.7 | python3.11-venv 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3446 | LOW2.7 | python3.11-venv 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-54661 | LOW2.7 | socat 1.7.4.4-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34743 | LOW2.7 | xz-utils 5.4.1-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4516 | LOW2.6 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-4516 | LOW2.6 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-4516 | LOW2.6 | python3.11-venv 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2003-1307 | LOW2.58 | apache2-utils 2.4.65-1~deb12u1 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2003-1580 | LOW2.58 | apache2-utils 2.4.65-1~deb12u1 No fix yet | 3.7% Low-Moderate Risk | Post-Exploit |
| CVE-2007-2768 | LOW2.58 | openssh-client 1:9.2p1-2+deb12u7 No fix yet | 8.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-34180 | LOW2.55 | openssl 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3219 | LOW2.55 | pip 25.3 fixed in 26.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2007-3303 | LOW2.5 | apache2-utils 2.4.65-1~deb12u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | login 1:4.13+dfsg1-1+deb12u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.13+dfsg1-1+deb12u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-33006 | LOW2.45 | apache2-utils 2.4.65-1~deb12u1 fixed in 2.4.67-1~deb12u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-10148 | LOW2.45 | curl 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | curl 7.88.1-10+deb12u14 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-10148 | LOW2.45 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-10148 | LOW2.45 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | LOW2.45 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.45 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | LOW2.45 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.45 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | LOW2.45 | python3.11-venv 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.45 | python3.11-venv 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 9.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | dirmngr 2.2.40-1.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | dirmngr 2.2.40-1.1+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gnupg 2.2.40-1.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gnupg 2.2.40-1.1+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gnupg-utils 2.2.40-1.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gnupg-utils 2.2.40-1.1+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg 2.2.40-1.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg 2.2.40-1.1+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg-agent 2.2.40-1.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg-agent 2.2.40-1.1+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg-wks-client 2.2.40-1.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg-wks-client 2.2.40-1.1+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg-wks-server 2.2.40-1.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg-wks-server 2.2.40-1.1+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgconf 2.2.40-1.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgconf 2.2.40-1.1+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgsm 2.2.40-1.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgsm 2.2.40-1.1+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgv 2.2.40-1.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgv 2.2.40-1.1+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68160 | LOW2.4 | openssl 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-0725 | LOW2.4 | curl 7.88.1-10+deb12u14 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0725 | LOW2.4 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0725 | LOW2.4 | libcurl4 7.88.1-10+deb12u14 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-69644 | LOW2.38 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | LOW2.29 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0865 | LOW2.29 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW2.29 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-11468 | LOW2.29 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0865 | LOW2.29 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW2.29 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-11468 | LOW2.29 | python3.11-venv 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0865 | LOW2.29 | python3.11-venv 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW2.29 | python3.11-venv 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2007-1743 | LOW2.24 | apache2-utils 2.4.65-1~deb12u1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils 9.1-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43895 | LOW2.24 | jq 1.6-2.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt-transport-https 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-27613 | LOW2.19 | git 1:2.39.5-0+deb12u2 fixed in 1:2.39.5-0+deb12u3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-6069 | LOW2.19 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8291 | LOW2.19 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-6069 | LOW2.19 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8291 | LOW2.19 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-6069 | LOW2.19 | python3.11-venv 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8291 | LOW2.19 | python3.11-venv 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-24515 | LOW2.12 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-13978 | LOW2.12 | libtiff6 4.5.0-6+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8534 | LOW2.12 | libtiff6 4.5.0-6+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-11191 | LOW2.12 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-68788 | LOW2.12 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW2.04 | openssl 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-1703 | LOW1.99 | pip 25.3 fixed in 26.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-45446 | LOW1.89 | openssl 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | login 1:4.13+dfsg1-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.13+dfsg1-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2008-0456 | LOW1.79 | apache2-utils 2.4.65-1~deb12u1 No fix yet | 19.0% High Exploitation Risk | Post-Exploit |
| CVE-2007-3719 | LOW1.78 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW1.68 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | dirmngr 2.2.40-1.1+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gnupg 2.2.40-1.1+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gnupg-utils 2.2.40-1.1+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg 2.2.40-1.1+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg-agent 2.2.40-1.1+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg-wks-client 2.2.40-1.1+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg-wks-server 2.2.40-1.1+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgconf 2.2.40-1.1+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgsm 2.2.40-1.1+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgv 2.2.40-1.1+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW1.68 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.68 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4519 | LOW1.68 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW1.68 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.68 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4519 | LOW1.68 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW1.68 | python3.11-venv 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.68 | python3.11-venv 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3.11-venv 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4519 | LOW1.68 | python3.11-venv 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-4217 | LOW1.68 | unzip 6.0-28 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-42155 | LOW1.61 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-common 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-46835 | LOW1.58 | git 1:2.39.5-0+deb12u2 fixed in 1:2.39.5-0+deb12u3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2003-1581 | LOW1.56 | apache2-utils 2.4.65-1~deb12u1 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-35388 | LOW1.27 | openssh-client 1:9.2p1-2+deb12u7 fixed in 1:9.2p1-2+deb12u10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2001-1534 | LOW1.07 | apache2-utils 2.4.65-1~deb12u1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-68121 | NONE0 | stdlib v1.19.3 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-24538 | NONE0 | stdlib v1.19.3 fixed in 1.19.8, 1.20.3 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-24540 | NONE0 | stdlib v1.19.3 fixed in 1.19.9, 1.20.4 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2024-24790 | NONE0 | stdlib v1.19.3 fixed in 1.21.11, 1.22.4 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2024-52005 | NONE0 | git-man 1:2.39.5-0+deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-48385 | NONE0 | git-man 1:2.39.5-0+deb12u2 fixed in 1:2.39.5-0+deb12u3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-48384 | NONE0 | git-man 1:2.39.5-0+deb12u2 fixed in 1:2.39.5-0+deb12u3 | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2025-69720 | NONE0 | libncurses6 6.4-4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncursesw6 6.4-4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6020 | NONE0 | libpam-modules 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6020 | NONE0 | libpam-modules-bin 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6020 | NONE0 | libpam-runtime 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6020 | NONE0 | libpam0g 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.4-4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-29111 | NONE0 | libudev1 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.4-4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.4-4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-29403 | NONE0 | stdlib v1.19.3 fixed in 1.19.10, 1.20.5 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-24975 | NONE0 | git-man 1:2.39.5-0+deb12u2 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-41720 | NONE0 | stdlib v1.19.3 fixed in 1.18.9, 1.19.4 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-41722 | NONE0 | stdlib v1.19.3 fixed in 1.19.6, 1.20.1 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2022-41723 | NONE0 | stdlib v1.19.3 fixed in 1.19.6, 1.20.1 | 4.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-41724 | NONE0 | stdlib v1.19.3 fixed in 1.19.6, 1.20.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-41725 | NONE0 | stdlib v1.19.3 fixed in 1.19.6, 1.20.1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-24534 | NONE0 | stdlib v1.19.3 fixed in 1.19.8, 1.20.3 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2023-24536 | NONE0 | stdlib v1.19.3 fixed in 1.19.8, 1.20.3 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-24537 | NONE0 | stdlib v1.19.3 fixed in 1.19.8, 1.20.3 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-39325 | NONE0 | stdlib v1.19.3 fixed in 1.20.10, 1.21.3 | 3.8% Low-Moderate Risk | Not Applicable |
| CVE-2023-45283 | NONE0 | stdlib v1.19.3 fixed in 1.20.11, 1.21.4, 1.20.12, 1.21.5 | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2023-45287 | NONE0 | stdlib v1.19.3 fixed in 1.20.0 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-45288 | NONE0 | stdlib v1.19.3 fixed in 1.21.9, 1.22.2 | 92.0% Actively Exploited | Not Applicable |
| CVE-2024-34156 | NONE0 | stdlib v1.19.3 fixed in 1.22.7, 1.23.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-61726 | NONE0 | stdlib v1.19.3 fixed in 1.24.12, 1.25.6 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-61729 | NONE0 | stdlib v1.19.3 fixed in 1.24.11, 1.25.5 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-25679 | NONE0 | stdlib v1.19.3 fixed in 1.25.8, 1.26.1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-32280 | NONE0 | stdlib v1.19.3 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32281 | NONE0 | stdlib v1.19.3 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-32283 | NONE0 | stdlib v1.19.3 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-33811 | NONE0 | stdlib v1.19.3 fixed in 1.25.10, 1.26.3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-33814 | NONE0 | stdlib v1.19.3 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-39820 | NONE0 | stdlib v1.19.3 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-39836 | NONE0 | stdlib v1.19.3 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-58183 | NONE0 | stdlib v1.19.3 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61728 | NONE0 | stdlib v1.19.3 fixed in 1.24.12, 1.25.6 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-24539 | NONE0 | stdlib v1.19.3 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-29400 | NONE0 | stdlib v1.19.3 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-68973 | NONE0 | gnupg-l10n 2.2.40-1.1+deb12u1 fixed in 2.2.40-1.1+deb12u2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-47907 | NONE0 | stdlib v1.19.3 fixed in 1.23.12, 1.24.6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-4673 | NONE0 | stdlib v1.19.3 fixed in 1.23.10, 1.24.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4105 | NONE0 | libudev1 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libncurses6 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libncursesw6 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libtinfo6 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-bin 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-29406 | NONE0 | stdlib v1.19.3 fixed in 1.19.11, 1.20.6 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-24785 | NONE0 | stdlib v1.19.3 fixed in 1.21.8, 1.22.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-47906 | NONE0 | stdlib v1.19.3 fixed in 1.23.12, 1.24.6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61727 | NONE0 | stdlib v1.19.3 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-40225 | NONE0 | libudev1 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40226 | NONE0 | libudev1 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-32282 | NONE0 | stdlib v1.19.3 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-39318 | NONE0 | stdlib v1.19.3 fixed in 1.20.8, 1.21.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-39319 | NONE0 | stdlib v1.19.3 fixed in 1.20.8, 1.21.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-32289 | NONE0 | stdlib v1.19.3 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-24783 | NONE0 | stdlib v1.19.3 fixed in 1.21.8, 1.22.1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-24791 | NONE0 | stdlib v1.19.3 fixed in 1.21.12, 1.22.5 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2024-34155 | NONE0 | stdlib v1.19.3 fixed in 1.22.7, 1.23.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-34158 | NONE0 | stdlib v1.19.3 fixed in 1.22.7, 1.23.1 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2024-45336 | NONE0 | stdlib v1.19.3 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam-modules 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam-modules-bin 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam-runtime 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam0g 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-24789 | NONE0 | stdlib v1.19.3 fixed in 1.21.11, 1.22.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32288 | NONE0 | stdlib v1.19.3 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-24784 | NONE0 | stdlib v1.19.3 fixed in 1.21.8, 1.22.1 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-22871 | NONE0 | stdlib v1.19.3 fixed in 1.23.8, 1.24.2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-27142 | NONE0 | stdlib v1.19.3 fixed in 1.25.8, 1.26.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39826 | NONE0 | stdlib v1.19.3 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31437 | NONE0 | libudev1 252.39-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | libudev1 252.39-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | libudev1 252.39-1~deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-41717 | NONE0 | stdlib v1.19.3 fixed in 1.18.9, 1.19.4 | 5.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-24532 | NONE0 | stdlib v1.19.3 fixed in 1.19.7, 1.20.2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-29409 | NONE0 | stdlib v1.19.3 fixed in 1.19.12, 1.20.7, 1.21.0-rc.4 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-39326 | NONE0 | stdlib v1.19.3 fixed in 1.20.12, 1.21.5 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-45284 | NONE0 | stdlib v1.19.3 fixed in 1.20.11, 1.21.4 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45289 | NONE0 | stdlib v1.19.3 fixed in 1.21.8, 1.22.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-45290 | NONE0 | stdlib v1.19.3 fixed in 1.21.8, 1.22.1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-22866 | NONE0 | stdlib v1.19.3 fixed in 1.22.12, 1.23.6, 1.24.0-rc.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22873 | NONE0 | stdlib v1.19.3 fixed in 1.23.9, 1.24.3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-47912 | NONE0 | stdlib v1.19.3 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58185 | NONE0 | stdlib v1.19.3 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-58187 | NONE0 | stdlib v1.19.3 fixed in 1.24.9, 1.25.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58188 | NONE0 | stdlib v1.19.3 fixed in 1.24.8, 1.25.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-58189 | NONE0 | stdlib v1.19.3 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61723 | NONE0 | stdlib v1.19.3 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61724 | NONE0 | stdlib v1.19.3 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61725 | NONE0 | stdlib v1.19.3 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61730 | NONE0 | stdlib v1.19.3 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42507 | NONE0 | stdlib v1.19.3 fixed in 1.25.11, 1.26.4 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-58186 | NONE0 | stdlib v1.19.3 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-1000021 | NONE0 | git-man 1:2.39.5-0+deb12u2 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-42250 | NONE0 | libbz2-1.0 1.0.8-5+b1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules 1.5.2-6+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules-bin 1.5.2-6+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-runtime 1.5.2-6+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam0g 1.5.2-6+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-30258 | NONE0 | gnupg-l10n 2.2.40-1.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68972 | NONE0 | gnupg-l10n 2.2.40-1.1+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-modules 1.5.2-6+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-modules-bin 1.5.2-6+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-runtime 1.5.2-6+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam0g 1.5.2-6+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22870 | NONE0 | stdlib v1.19.3 fixed in 1.23.7, 1.24.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-27613 | NONE0 | git-man 1:2.39.5-0+deb12u2 fixed in 1:2.39.5-0+deb12u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-45341 | NONE0 | stdlib v1.19.3 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-3219 | NONE0 | gnupg-l10n 2.2.40-1.1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncurses6 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncursesw6 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | libudev1 252.39-1~deb12u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | libudev1 252.39-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-bin 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-46835 | NONE0 | git-man 1:2.39.5-0+deb12u2 fixed in 1:2.39.5-0+deb12u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-27139 | NONE0 | stdlib v1.19.3 fixed in 1.25.8, 1.26.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-29167 | NONE0 | apache2-utils 2.4.65-1~deb12u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-44186 | NONE0 | apache2-utils 2.4.65-1~deb12u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-48913 | NONE0 | apache2-utils 2.4.65-1~deb12u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.2.15-2+b9 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-2219 | NONE0 | dpkg 1.21.22 fixed in 1.21.23 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6297 | NONE0 | dpkg 1.21.22 fixed in 1.21.23 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-47770 | NONE0 | jq 1.6-2.1+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-49839 | NONE0 | jq 1.6-2.1+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libblkid1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2023-51792 | NONE0 | libde265-0 1.0.11-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38949 | NONE0 | libde265-0 1.0.11-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-38950 | NONE0 | libde265-0 1.0.11-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61147 | NONE0 | libde265-0 1.0.11-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-49295 | NONE0 | libde265-0 1.0.11-1+deb12u2 No fix yet | — | Not Applicable |
| CVE-2026-49337 | NONE0 | libde265-0 1.0.11-1+deb12u2 No fix yet | — | Not Applicable |
| CVE-2026-49346 | NONE0 | libde265-0 1.0.11-1+deb12u2 No fix yet | — | Not Applicable |
| CVE-2026-56131 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | — | Not Applicable |
| CVE-2026-56132 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | — | Not Applicable |
| CVE-2026-41069 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-25269 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-47178 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-49271 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-47770 | NONE0 | libjq1 1.6-2.1+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-49839 | NONE0 | libjq1 1.6-2.1+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libmount1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | — | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-11822 | NONE0 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-7709 | NONE0 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-15661 | NONE0 | libssh2-1 1.10.0-3+b1 No fix yet | — | Not Applicable |
| CVE-2026-55199 | NONE0 | libssh2-1 1.10.0-3+b1 No fix yet | — | Not Applicable |
| CVE-2026-55200 | NONE0 | libssh2-1 1.10.0-3+b1 No fix yet | — | Not Applicable |
| CVE-2025-27587 | NONE0 | libssl3 3.0.17-1~deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-36849 | NONE0 | libtiff6 4.5.0-6+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libuuid1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libuuid1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-43011 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23268 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31405 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31478 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31657 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31659 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31705 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43258 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54125 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40003 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40077 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40097 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40137 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40180 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40262 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40263 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40266 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40278 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40282 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40285 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40286 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40288 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40289 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40306 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40311 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40313 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40314 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40315 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40317 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40333 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40337 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40354 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40358 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68177 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68190 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68201 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68217 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68220 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68238 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68246 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68254 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68255 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68256 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68257 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68258 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68263 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68266 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68286 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68289 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68290 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68302 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68303 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68315 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68320 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68322 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68325 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68327 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68328 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68330 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68332 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68335 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68339 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68344 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68364 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68369 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68727 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68728 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68733 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68759 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68765 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68766 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68767 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68769 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68771 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68772 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68773 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68777 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68781 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68786 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68787 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68796 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68797 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68799 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68804 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68806 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68808 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68809 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71065 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71067 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71069 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71192 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71196 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71197 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71198 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71199 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71304 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23030 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23033 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23037 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23049 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23056 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23176 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23182 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23245 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23269 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23281 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23364 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23372 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23393 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23406 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23407 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31396 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31409 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31417 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31432 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31433 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31476 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31477 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31494 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31563 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31587 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31597 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31598 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31602 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31611 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31612 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31622 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31626 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31627 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31629 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31656 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31683 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31695 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31706 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31707 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31711 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31712 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31716 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31761 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31768 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31780 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43075 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43076 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43117 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43184 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43203 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43206 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43207 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43232 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43236 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43249 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43256 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43283 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43291 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43324 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43336 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43370 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43373 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43377 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43476 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43480 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43490 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43495 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43497 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43499 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45839 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45848 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45849 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45850 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45864 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45865 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45866 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45867 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45869 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45875 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45879 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45881 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45883 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45885 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45890 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45893 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45902 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45916 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45924 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45930 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45935 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45936 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45958 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46006 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46031 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46058 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46062 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46072 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46075 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46077 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46080 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46091 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46098 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46108 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46109 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46110 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46112 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46122 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46124 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46128 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46129 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46143 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46164 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46177 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46197 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46198 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46199 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46204 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46205 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46206 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46208 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46212 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46218 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46230 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46238 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46303 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46314 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46328 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46250 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46265 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46270 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46276 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46282 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46285 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46293 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46296 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46301 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | — | Not Applicable |
| CVE-2023-53851 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43212 | NONE0 | linux-libc-dev 6.1.158-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52909 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | — | Not Applicable |
| CVE-2026-52910 | NONE0 | linux-libc-dev 6.1.158-1 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login 1:4.13+dfsg1-1+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | mount 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | mount 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-48615 | NONE0 | nodejs 22.21.0-1nodesource1 No fix yet | — | Not Applicable |
| CVE-2026-48617 | NONE0 | nodejs 22.21.0-1nodesource1 No fix yet | — | Not Applicable |
| CVE-2026-48618 | NONE0 | nodejs 22.21.0-1nodesource1 No fix yet | — | Not Applicable |
| CVE-2026-48619 | NONE0 | nodejs 22.21.0-1nodesource1 No fix yet | — | Not Applicable |
| CVE-2026-48928 | NONE0 | nodejs 22.21.0-1nodesource1 No fix yet | — | Not Applicable |
| CVE-2026-48930 | NONE0 | nodejs 22.21.0-1nodesource1 No fix yet | — | Not Applicable |
| CVE-2026-48931 | NONE0 | nodejs 22.21.0-1nodesource1 No fix yet | — | Not Applicable |
| CVE-2026-48933 | NONE0 | nodejs 22.21.0-1nodesource1 No fix yet | — | Not Applicable |
| CVE-2026-48934 | NONE0 | nodejs 22.21.0-1nodesource1 No fix yet | — | Not Applicable |
| CVE-2026-48935 | NONE0 | nodejs 22.21.0-1nodesource1 No fix yet | — | Not Applicable |
| CVE-2026-48937 | NONE0 | nodejs 22.21.0-1nodesource1 No fix yet | — | Not Applicable |
| CVE-2025-27587 | NONE0 | openssl 3.0.17-1~deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.13+dfsg1-1+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | python3.11 3.11.2-6+deb12u6 No fix yet | — | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | — | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.11-venv 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | python3.11-venv 3.11.2-6+deb12u6 No fix yet | — | Not Applicable |
| TEMP-0517018-A83CE6 | NONE0 | sysvinit-utils 3.06-4 No fix yet | — | Not Applicable |
| TEMP-0290435-0B57B5 | NONE0 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | util-linux 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | util-linux 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-44240 | NONE0 | basic-ftp 5.0.5 fixed in 5.3.1 | 0.5% Theoretical Threat | Not Applicable |
| GHSA-6v7q-wjvx-w8wg | NONE0 | basic-ftp 5.0.5 fixed in 5.2.2 | — | Not Applicable |
| CVE-2026-53550 | NONE0 | js-yaml 4.1.1 fixed in 4.2.0 | — | Not Applicable |
| CVE-2026-45618 | NONE0 | liquidjs 10.6.1 fixed in 10.26.0 | — | Not Applicable |
| CVE-2026-33285 | NONE0 | liquidjs 10.6.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-33287 | NONE0 | liquidjs 10.6.1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45357 | NONE0 | liquidjs 10.6.1 No fix yet | — | Not Applicable |
| CVE-2026-45617 | NONE0 | liquidjs 10.6.1 fixed in 10.26.0 | — | Not Applicable |
| CVE-2026-39859 | NONE0 | liquidjs 10.6.1 fixed in 10.25.5 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-44644 | NONE0 | liquidjs 10.6.1 No fix yet | — | Not Applicable |
| CVE-2026-44645 | NONE0 | liquidjs 10.6.1 No fix yet | — | Not Applicable |
| CVE-2026-44646 | NONE0 | liquidjs 10.6.1 No fix yet | — | Not Applicable |
| CVE-2026-8723 | NONE0 | qs 6.13.0 fixed in 6.15.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53655 | NONE0 | tar 6.2.1 fixed in 7.5.16 | — | Not Applicable |
| CVE-2026-44889 | NONE0 | WebOb 1.8.9 fixed in 1.8.10 | — | Not Applicable |
| GHSA-537c-gmf6-5ccf | NONE0 | cryptography 46.0.3 fixed in 48.0.1 | — | Not Applicable |
| CVE-2026-39823 | NONE0 | stdlib v1.19.3 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39825 | NONE0 | stdlib v1.19.3 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42499 | NONE0 | stdlib v1.19.3 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42504 | NONE0 | stdlib v1.19.3 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-0913 | NONE0 | stdlib v1.19.3 fixed in 1.23.10, 1.24.4 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-27145 | NONE0 | stdlib v1.19.3 fixed in 1.25.11, 1.26.4 | 0.3% Theoretical Threat | Not Applicable |