This image poses a critical security risk and must not be used in production, especially as an internet-facing service. An attacker could exploit critical vulnerabilities, such as CVE-2025-6965, to achieve arbitrary code execution or denial of service by processing crafted SQL queries. Another high-severity vulnerability, CVE-2025-68121, impacts TLS certificate validation within the Go standard library, though it requires specific configuration mutations to be exploitable. The presence of 116 exposed vulnerabilities with severity 7.0 or higher, including several with high context importance and severe consequences, necessitates immediate remediation or replacement before any production deployment.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2025-6965 | CRITICAL9.8 | libsqlite3-0 3.40.1-2+deb12u1 fixed in 3.40.1-2+deb12u2 | 1.6% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2025-68121 | HIGH8.5 | stdlib v1.22.12 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | <0.1% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-7210 | HIGH8.33 | libpython3.11-minimal 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | HIGH8.33 | libpython3.11-stdlib 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42013 | HIGH8.2 | libgnutls30 3.7.9-2+deb12u3 fixed in 3.7.9-2+deb12u7 | — | Directly Exposed |
| CVE-2026-5260 | HIGH8.2 | libgnutls30 3.7.9-2+deb12u3 fixed in 3.7.9-2+deb12u7 | — | Directly Exposed |
| CVE-2023-31484 | HIGH8.1 | libperl5.36 5.36.0-7+deb12u1 fixed in 5.36.0-7+deb12u3 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-15467 | HIGH7.84 | libssl3 3.0.15-1~deb12u1 fixed in 3.0.18-1~deb12u2 | 2.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2025-15467 | HIGH7.84 | openssl 3.0.15-1~deb12u1 fixed in 3.0.18-1~deb12u2 | 2.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-48962 | HIGH7.8 | libperl5.36 5.36.0-7+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2013-7445 | HIGH7.8 | linux-libc-dev 6.1.124-1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31431 | HIGH7.8 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-46243 | HIGH7.8 | linux-libc-dev 6.1.124-1 fixed in 6.1.174-1 | — | Directly Exposed |
| CVE-2026-46300 | HIGH7.8 | linux-libc-dev 6.1.124-1 fixed in 6.1.174-1 | — | Directly Exposed |
| CVE-2026-46333 | HIGH7.8 | linux-libc-dev 6.1.124-1 fixed in 6.1.172-1 | — | Directly Exposed |
| CVE-2026-46274 | HIGH7.8 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-33845 | HIGH7.73 | libgnutls30 3.7.9-2+deb12u3 fixed in 3.7.9-2+deb12u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7458 | HIGH7.73 | libsqlite3-0 3.40.1-2+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7598 | HIGH7.73 | libssh2-1 1.10.0-3+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-bin 2.36-9+deb12u9 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-dev-bin 2.36-9+deb12u9 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6 2.36-9+deb12u9 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6-dev 2.36-9+deb12u9 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-52425 | HIGH7.5 | libexpat1 2.5.0-1+deb12u1 fixed in 2.5.0-1+deb12u2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28757 | HIGH7.5 | libexpat1 2.5.0-1+deb12u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42009 | HIGH7.5 | libgnutls30 3.7.9-2+deb12u3 fixed in 3.7.9-2+deb12u7 | — | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libgssapi-krb5-2 1.20.1-2+deb12u2 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libk5crypto3 1.20.1-2+deb12u2 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5-3 1.20.1-2+deb12u2 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5support0 1.20.1-2+deb12u2 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2953 | HIGH7.5 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2015-3276 | HIGH7.5 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | HIGH7.5 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 6.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42497 | HIGH7.5 | libperl5.36 5.36.0-7+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2026-9538 | HIGH7.5 | libperl5.36 5.36.0-7+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2026-43501 | HIGH7.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2019-1010023 | HIGH7.48 | libc-bin 2.36-9+deb12u9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2019-1010023 | HIGH7.48 | libc-dev-bin 2.36-9+deb12u9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2019-1010023 | HIGH7.48 | libc6 2.36-9+deb12u9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2019-1010023 | HIGH7.48 | libc6-dev 2.36-9+deb12u9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23395 | HIGH7.48 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | HIGH7.1 | libgnutls30 3.7.9-2+deb12u3 fixed in 3.7.9-2+deb12u7 | — | Directly Exposed |
| CVE-2026-46056 | HIGH7.1 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46120 | HIGH7.1 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46135 | HIGH7.1 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46150 | HIGH7.1 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46209 | HIGH7.1 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46259 | HIGH7.1 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2008-4609 | HIGH7.1 | linux-libc-dev 6.1.124-1 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-43494 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-43503 | HIGH7 | linux-libc-dev 6.1.124-1 fixed in 6.1.174-1 | — | Directly Exposed |
| CVE-2026-45852 | HIGH7 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45858 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45972 | HIGH7 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45984 | HIGH7 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45991 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46033 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46053 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46054 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46090 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46099 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46116 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46125 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46181 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46189 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46195 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46227 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2025-40271 | HIGH7 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-43491 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-43493 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45840 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45856 | HIGH7 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45859 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45860 | HIGH7 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45886 | HIGH7 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45892 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45894 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45899 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45912 | HIGH7 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45934 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45942 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45962 | HIGH7 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45970 | HIGH7 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45983 | HIGH7 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45985 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46004 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46015 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46017 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46021 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46023 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46028 | HIGH7 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-46032 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46043 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46047 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46052 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46069 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46119 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46123 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46132 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46133 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46149 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46158 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46160 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46170 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46172 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46173 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46174 | HIGH7 | linux-libc-dev 6.1.124-1 fixed in 6.1.174-1 | — | Directly Exposed |
| CVE-2026-46185 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46186 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46193 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46251 | HIGH7 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-46266 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46275 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46294 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46306 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2025-71313 | HIGH7 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2025-32988 | MEDIUM6.97 | libgnutls30 3.7.9-2+deb12u3 fixed in 3.7.9-2+deb12u5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-32990 | MEDIUM6.97 | libgnutls30 3.7.9-2+deb12u3 fixed in 3.7.9-2+deb12u5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31788 | MEDIUM6.97 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-39191 | MEDIUM6.97 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc-bin 2.36-9+deb12u9 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc-dev-bin 2.36-9+deb12u9 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc6 2.36-9+deb12u9 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc6-dev 2.36-9+deb12u9 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | MEDIUM6.88 | libcurl3-gnutls 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | MEDIUM6.88 | libcurl4 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31486 | MEDIUM6.88 | libperl5.36 5.36.0-7+deb12u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-6100 | MEDIUM6.88 | libpython3.11-minimal 3.11.2-6+deb12u5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6100 | MEDIUM6.88 | libpython3.11-stdlib 3.11.2-6+deb12u5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | libssl3 3.0.15-1~deb12u1 fixed in 3.0.19-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-0938 | MEDIUM6.8 | libpython3.11-minimal 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u6 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-0938 | MEDIUM6.8 | libpython3.11-stdlib 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u6 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42010 | MEDIUM6.66 | libgnutls30 3.7.9-2+deb12u3 fixed in 3.7.9-2+deb12u7 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-11082 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-25210 | MEDIUM6.63 | libexpat1 2.5.0-1+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | MEDIUM6.63 | libncursesw6 6.4-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6020 | MEDIUM6.63 | libpam-modules 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6020 | MEDIUM6.63 | libpam-runtime 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6020 | MEDIUM6.63 | libpam0g 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | libsystemd0 252.33-1~deb12u1 fixed in 252.39-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | MEDIUM6.63 | libtinfo6 6.4-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | libudev1 252.33-1~deb12u1 fixed in 252.39-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-19449 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-19814 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-3847 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52452 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52624 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52751 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52927 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53218 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53363 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53510 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-54285 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-21803 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26739 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26836 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26913 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26914 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26944 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-35866 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-35887 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-38570 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-38630 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-41045 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-42118 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-44941 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-44942 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-44951 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-46729 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-46786 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-46811 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-46813 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-47691 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-49989 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-50029 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-50047 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-50063 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-50217 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-50226 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-50246 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-50282 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53068 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53166 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53168 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53170 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53179 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53203 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53218 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56538 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56551 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56608 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56609 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56631 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56775 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57887 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57892 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57900 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57904 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57917 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57951 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57980 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57998 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58002 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58034 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58055 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58069 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58072 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58093 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58240 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21631 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21671 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21680 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21687 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21692 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21704 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21715 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21724 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21734 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21735 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21756 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21772 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21780 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21785 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21791 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21811 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21812 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21855 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21858 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21863 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21914 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21919 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21927 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21928 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21934 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21945 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21967 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21968 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21969 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21979 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21991 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22020 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22022 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22040 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22041 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22056 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22083 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22088 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22126 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23133 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23142 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23158 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37738 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37750 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37752 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37777 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37778 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37786 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37789 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37796 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37797 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37798 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37803 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37810 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37817 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37819 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37822 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37823 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37839 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37840 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37849 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37854 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37861 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37885 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37890 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37892 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37899 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37903 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37913 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37914 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37921 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37923 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37924 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37926 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37927 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37928 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-37947 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37952 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37957 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37979 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37991 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38000 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38022 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38024 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38052 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38068 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38069 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38077 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38079 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38117 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38118 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38129 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38131 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38146 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38154 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38157 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38180 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38182 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38183 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38198 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38201 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38206 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38211 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38212 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38226 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38227 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38230 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38236 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38239 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38245 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38248 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38250 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38257 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38259 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38280 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38298 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38313 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38323 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38346 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38348 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38349 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38350 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38352 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38361 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38369 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38375 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38377 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38385 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38389 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38396 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38401 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38403 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38415 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38416 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38422 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38425 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38428 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38437 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38443 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38456 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38459 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38464 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38471 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38476 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38485 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38488 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38494 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38500 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38512 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38527 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38535 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38538 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38548 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38550 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38552 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38555 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38563 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38565 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38572 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38574 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38579 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38582 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38584 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38585 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38593 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38595 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38618 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38627 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38653 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38666 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38676 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38685 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38697 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38699 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38702 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38704 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38707 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38708 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38718 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38722 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38724 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38729 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38734 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39686 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39689 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39691 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39701 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39730 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39738 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39743 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39766 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39776 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39783 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39788 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39790 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39797 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39810 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39823 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39824 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39828 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39835 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39841 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39849 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39859 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39860 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39863 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39864 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39866 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39870 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39871 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39873 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39877 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39880 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39881 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39911 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39913 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39944 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39945 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39951 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39952 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39955 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39957 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39967 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40149 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40364 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68817 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71068 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71071 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71073 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71075 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71078 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71082 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71086 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71089 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71091 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71123 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71137 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71152 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71162 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71220 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71238 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22980 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23001 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23010 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23025 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23068 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23073 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23074 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23078 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23083 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23089 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23098 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23111 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23156 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23171 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23193 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23208 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23209 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23216 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23221 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23226 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23227 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23231 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-23234 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23319 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23343 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23359 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23361 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23378 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23408 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23410 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23411 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23422 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23428 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23447 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23448 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31399 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31402 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31452 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31455 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31485 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31488 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31489 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31493 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31500 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31527 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31532 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31566 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31576 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31578 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31580 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31581 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31583 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31686 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31688 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31696 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31702 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31709 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31715 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31720 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31729 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31747 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31748 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31759 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31787 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43015 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43020 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43027 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43049 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43128 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43150 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43196 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43205 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43250 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43284 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43328 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43378 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43426 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43458 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43500 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40258 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40277 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-12456 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-19378 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-11725 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-26934 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-25265 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3238 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-26242 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-3640 | MEDIUM6.63 | linux-libc-dev 6.1.124-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | MEDIUM6.63 | ncurses-base 6.4-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46012 | MEDIUM6.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2025-39971 | MEDIUM6.46 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-9192 | MEDIUM6.38 | libc-bin 2.36-9+deb12u9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2019-9192 | MEDIUM6.38 | libc-dev-bin 2.36-9+deb12u9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2019-9192 | MEDIUM6.38 | libc6 2.36-9+deb12u9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2019-9192 | MEDIUM6.38 | libc6-dev 2.36-9+deb12u9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5773 | MEDIUM6.38 | libcurl3-gnutls 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6276 | MEDIUM6.38 | libcurl3-gnutls 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5773 | MEDIUM6.38 | libcurl4 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6276 | MEDIUM6.38 | libcurl4 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45186 | MEDIUM6.38 | libexpat1 2.5.0-1+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-8176 | MEDIUM6.38 | libexpat1 2.5.0-1+deb12u1 fixed in 2.5.0-1+deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-41989 | MEDIUM6.38 | libgcrypt20 1.10.1-3 fixed in 1.10.1-3+deb12u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-6829 | MEDIUM6.38 | libgcrypt20 1.10.1-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33846 | MEDIUM6.38 | libgnutls30 3.7.9-2+deb12u3 fixed in 3.7.9-2+deb12u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2020-36325 | MEDIUM6.38 | libjansson4 2.14-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-31115 | MEDIUM6.38 | liblzma5 5.4.1-0.2 fixed in 5.4.1-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27135 | MEDIUM6.38 | libnghttp2-14 1.52.0-1+deb12u2 fixed in 1.52.0-1+deb12u3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13836 | MEDIUM6.38 | libpython3.11-minimal 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69534 | MEDIUM6.38 | libpython3.11-minimal 3.11.2-6+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | libpython3.11-minimal 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.38 | libpython3.11-minimal 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8194 | MEDIUM6.38 | libpython3.11-minimal 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-13836 | MEDIUM6.38 | libpython3.11-stdlib 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69534 | MEDIUM6.38 | libpython3.11-stdlib 3.11.2-6+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | libpython3.11-stdlib 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.38 | libpython3.11-stdlib 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8194 | MEDIUM6.38 | libpython3.11-stdlib 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | libssl3 3.0.15-1~deb12u1 fixed in 3.0.18-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM6.38 | libssl3 3.0.15-1~deb12u1 fixed in 3.0.19-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM6.38 | libssl3 3.0.15-1~deb12u1 fixed in 3.0.19-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.38 | libssl3 3.0.15-1~deb12u1 fixed in 3.0.19-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38501 | MEDIUM6.38 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22998 | MEDIUM6.38 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39973 | MEDIUM6.38 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39982 | MEDIUM6.38 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40240 | MEDIUM6.38 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68349 | MEDIUM6.38 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31669 | MEDIUM6.38 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43110 | MEDIUM6.38 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43186 | MEDIUM6.38 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43190 | MEDIUM6.38 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-19070 | MEDIUM6.38 | linux-libc-dev 6.1.124-1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-0400 | MEDIUM6.38 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61726 | MEDIUM6.38 | stdlib v1.22.12 fixed in 1.24.12, 1.25.6 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61729 | MEDIUM6.38 | stdlib v1.22.12 fixed in 1.24.11, 1.25.5 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-25679 | MEDIUM6.38 | stdlib v1.22.12 fixed in 1.25.8, 1.26.1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32280 | MEDIUM6.38 | stdlib v1.22.12 fixed in 1.25.9, 1.26.2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32281 | MEDIUM6.38 | stdlib v1.22.12 fixed in 1.25.9, 1.26.2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32283 | MEDIUM6.38 | stdlib v1.22.12 fixed in 1.25.9, 1.26.2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33811 | MEDIUM6.38 | stdlib v1.22.12 fixed in 1.25.10, 1.26.3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM6.38 | stdlib v1.22.12 fixed in 1.25.10, 1.26.3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-39820 | MEDIUM6.38 | stdlib v1.22.12 fixed in 1.25.10, 1.26.3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-39836 | MEDIUM6.38 | stdlib v1.22.12 fixed in 1.25.10, 1.26.3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-58183 | MEDIUM6.38 | stdlib v1.22.12 fixed in 1.24.8, 1.25.2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61728 | MEDIUM6.38 | stdlib v1.22.12 fixed in 1.24.12, 1.25.6 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3833 | MEDIUM6.29 | libgnutls30 3.7.9-2+deb12u3 fixed in 3.7.9-2+deb12u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM6.29 | libgnutls30 3.7.9-2+deb12u3 fixed in 3.7.9-2+deb12u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | libssl3 3.0.15-1~deb12u1 fixed in 3.0.18-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40170 | MEDIUM6.29 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56406 | MEDIUM6.21 | libperl5.36 5.36.0-7+deb12u1 fixed in 5.36.0-7+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31607 | MEDIUM6.21 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43038 | MEDIUM6.21 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53781 | MEDIUM6.21 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39981 | MEDIUM6.21 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40141 | MEDIUM6.21 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40176 | MEDIUM6.21 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40269 | MEDIUM6.21 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40294 | MEDIUM6.21 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40304 | MEDIUM6.21 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68800 | MEDIUM6.21 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23243 | MEDIUM6.21 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43078 | MEDIUM6.21 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43248 | MEDIUM6.21 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.11-minimal 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.11-minimal 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1299 | MEDIUM6.03 | libpython3.11-minimal 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.11-stdlib 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.11-stdlib 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1299 | MEDIUM6.03 | libpython3.11-stdlib 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53034 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26669 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26982 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-41013 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-41935 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-46774 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-50164 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53147 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57906 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57907 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57908 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57910 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57911 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57912 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57925 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57929 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57945 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57982 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58007 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58014 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58054 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21647 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21719 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21782 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21794 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21905 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21920 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21946 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21950 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21985 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21993 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22038 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22039 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22079 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22104 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22107 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22121 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23156 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23157 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37739 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37749 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37780 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37785 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37879 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38004 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38027 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38081 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38088 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38103 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38111 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38153 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38159 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38204 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38249 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38286 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38320 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38342 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38395 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38445 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38482 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38483 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38497 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38502 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38529 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38530 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38556 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38616 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38636 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38652 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38670 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38677 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38679 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38680 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38713 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38714 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38715 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38728 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38736 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39682 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39683 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39685 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39687 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39710 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39719 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39735 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39744 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39757 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39760 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39806 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39817 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39839 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39853 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39869 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39883 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39891 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39901 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39943 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40082 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71093 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71112 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71116 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71133 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71136 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22984 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23076 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23099 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23102 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23187 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23204 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23235 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23315 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23318 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23327 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23388 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23397 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31568 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31778 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43040 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43052 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43141 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43241 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43281 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43380 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43386 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43427 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43449 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43450 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43453 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-25742 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-25743 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-36013 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53216 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58013 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21753 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21762 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21887 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40064 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40301 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40322 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40349 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40351 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68168 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68183 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68324 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68347 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68366 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68724 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23455 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31613 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31685 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31786 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43051 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43126 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43414 | MEDIUM6.03 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc-bin 2.36-9+deb12u9 fixed in 2.36-9+deb12u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc-dev-bin 2.36-9+deb12u9 fixed in 2.36-9+deb12u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc6 2.36-9+deb12u9 fixed in 2.36-9+deb12u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc6-dev 2.36-9+deb12u9 fixed in 2.36-9+deb12u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4878 | MEDIUM5.95 | libcap2 1:2.66-4 fixed in 1:2.66-4+deb12u3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-3864 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-52586 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-36899 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-42162 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-50061 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56664 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21702 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21718 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37776 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37915 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38051 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38102 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38107 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38108 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39702 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39749 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39759 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39826 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40186 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40248 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68287 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71221 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23191 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23454 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31419 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31663 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43037 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43050 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43125 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43198 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43329 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53762 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57984 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21703 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21726 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21727 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21761 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21764 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21867 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22004 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39993 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40096 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40135 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40154 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40158 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40168 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40259 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40318 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40328 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68285 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68301 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23050 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23270 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23392 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31408 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31508 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31586 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31694 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43023 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43116 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43158 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43226 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43233 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43303 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43304 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43334 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43339 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43341 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-1247 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-2961 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-45884 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-45885 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23054 | MEDIUM5.95 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-47907 | MEDIUM5.95 | stdlib v1.22.12 fixed in 1.23.12, 1.24.6 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-11053 | MEDIUM5.9 | libcurl3-gnutls 7.88.1-10+deb12u8 fixed in 7.88.1-10+deb12u10 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-11053 | MEDIUM5.9 | libcurl4 7.88.1-10+deb12u8 fixed in 7.88.1-10+deb12u10 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-50219 | MEDIUM5.9 | libexpat1 2.5.0-1+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2018-1121 | MEDIUM5.9 | linux-libc-dev 6.1.124-1 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-46065 | MEDIUM5.8 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46113 | MEDIUM5.8 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-1965 | MEDIUM5.78 | libcurl3-gnutls 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14819 | MEDIUM5.78 | libcurl3-gnutls 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1965 | MEDIUM5.78 | libcurl4 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14819 | MEDIUM5.78 | libcurl4 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | 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.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68346 | MEDIUM5.78 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-4673 | MEDIUM5.78 | stdlib v1.22.12 fixed in 1.23.10, 1.24.4 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2020-15778 | MEDIUM5.77 | openssh-client 1:9.2p1-2+deb12u4 No fix yet | 64.3% Actively Exploited | Post-Exploit |
| CVE-2026-4105 | MEDIUM5.7 | libsystemd0 252.33-1~deb12u1 fixed in 252.39-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | libudev1 252.33-1~deb12u1 fixed in 252.39-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2020-36694 | MEDIUM5.7 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-21264 | MEDIUM5.7 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53095 | MEDIUM5.7 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57795 | MEDIUM5.7 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21714 | MEDIUM5.7 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21731 | MEDIUM5.7 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21739 | MEDIUM5.7 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22035 | MEDIUM5.7 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22097 | MEDIUM5.7 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40257 | MEDIUM5.7 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68237 | MEDIUM5.7 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21759 | MEDIUM5.61 | linux-libc-dev 6.1.124-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-40018 | MEDIUM5.61 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40261 | MEDIUM5.61 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | MEDIUM5.52 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc-bin 2.36-9+deb12u9 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.36-9+deb12u9 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc-dev-bin 2.36-9+deb12u9 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-dev-bin 2.36-9+deb12u9 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc6 2.36-9+deb12u9 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.36-9+deb12u9 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc6-dev 2.36-9+deb12u9 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6-dev 2.36-9+deb12u9 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | MEDIUM5.52 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | MEDIUM5.52 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-9681 | MEDIUM5.52 | libcurl3-gnutls 7.88.1-10+deb12u8 fixed in 7.88.1-10+deb12u9 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-3784 | MEDIUM5.52 | libcurl3-gnutls 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5545 | MEDIUM5.52 | libcurl3-gnutls 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6429 | MEDIUM5.52 | libcurl3-gnutls 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14524 | MEDIUM5.52 | libcurl3-gnutls 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-9681 | MEDIUM5.52 | libcurl4 7.88.1-10+deb12u8 fixed in 7.88.1-10+deb12u9 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-3784 | MEDIUM5.52 | libcurl4 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5545 | MEDIUM5.52 | libcurl4 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6429 | MEDIUM5.52 | libcurl4 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14524 | MEDIUM5.52 | libcurl4 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6395 | MEDIUM5.52 | libgnutls30 3.7.9-2+deb12u3 fixed in 3.7.9-2+deb12u5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | MEDIUM5.52 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libgssapi-krb5-2 1.20.1-2+deb12u2 fixed in 1.20.1-2+deb12u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libk5crypto3 1.20.1-2+deb12u2 fixed in 1.20.1-2+deb12u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libkrb5-3 1.20.1-2+deb12u2 fixed in 1.20.1-2+deb12u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libkrb5support0 1.20.1-2+deb12u2 fixed in 1.20.1-2+deb12u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | MEDIUM5.52 | libncursesw6 6.4-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | MEDIUM5.52 | libtinfo6 6.4-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68284 | MEDIUM5.52 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-6240 | MEDIUM5.52 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-36968 | MEDIUM5.52 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-47726 | MEDIUM5.52 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39969 | MEDIUM5.52 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40273 | MEDIUM5.52 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68354 | MEDIUM5.52 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68362 | MEDIUM5.52 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68380 | MEDIUM5.52 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31588 | MEDIUM5.52 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43239 | MEDIUM5.52 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-0564 | MEDIUM5.52 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | MEDIUM5.52 | ncurses-base 6.4-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-47906 | MEDIUM5.52 | stdlib v1.22.12 fixed in 1.23.12, 1.24.6 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61727 | MEDIUM5.52 | stdlib v1.22.12 fixed in 1.24.11, 1.25.5 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71305 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-43492 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-43502 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45834 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45835 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45836 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45838 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45841 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45842 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45843 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45844 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45846 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45855 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45857 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45862 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45891 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45914 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45943 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45944 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45949 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45960 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45974 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45981 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45988 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45994 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45996 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45999 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46000 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46022 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46024 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46027 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46037 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46050 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46051 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46064 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46070 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46078 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46079 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46082 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46086 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46102 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46107 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46111 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46127 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46130 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46137 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46146 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46151 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46157 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46159 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46168 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46169 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46180 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46190 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46191 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46214 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46234 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46252 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46253 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-46273 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46280 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46291 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46304 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46307 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46312 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2025-71315 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-43483 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-43484 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-43496 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45847 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45868 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45870 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45871 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45872 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45873 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45877 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45897 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45901 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45904 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45905 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45911 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45915 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45917 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45919 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45920 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45923 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45941 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45948 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45961 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45963 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45964 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45968 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45982 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-45987 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-45997 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46002 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46003 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46005 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46014 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46018 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46026 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46038 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46040 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46046 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46049 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46059 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46068 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46071 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46083 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46088 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46092 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46101 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46103 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46136 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46153 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46161 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46165 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46167 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46178 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46184 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46196 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46235 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46247 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-46249 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-46262 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Directly Exposed |
| CVE-2026-46292 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46299 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-46302 | MEDIUM5.5 | linux-libc-dev 6.1.124-1 No fix yet | — | Directly Exposed |
| CVE-2026-42496 | MEDIUM5.46 | perl 5.36.0-7+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2026-42496 | MEDIUM5.46 | perl-base 5.36.0-7+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2026-42496 | MEDIUM5.46 | perl-modules-5.36 5.36.0-7+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2026-40225 | MEDIUM5.44 | libsystemd0 252.33-1~deb12u1 fixed in 252.39-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | MEDIUM5.44 | libsystemd0 252.33-1~deb12u1 fixed in 252.39-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40225 | MEDIUM5.44 | libudev1 252.33-1~deb12u1 fixed in 252.39-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | MEDIUM5.44 | libudev1 252.33-1~deb12u1 fixed in 252.39-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57979 | MEDIUM5.44 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21700 | MEDIUM5.44 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21999 | MEDIUM5.44 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39978 | MEDIUM5.44 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40074 | MEDIUM5.44 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40309 | MEDIUM5.44 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40321 | MEDIUM5.44 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68371 | MEDIUM5.44 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23178 | MEDIUM5.44 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23383 | MEDIUM5.44 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23450 | MEDIUM5.44 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23456 | MEDIUM5.44 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31502 | MEDIUM5.44 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31516 | MEDIUM5.44 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-44032 | MEDIUM5.44 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-44033 | MEDIUM5.44 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-44034 | MEDIUM5.44 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32282 | MEDIUM5.44 | stdlib v1.22.12 fixed in 1.25.9, 1.26.2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-3397 | MEDIUM5.35 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40307 | MEDIUM5.35 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68282 | MEDIUM5.35 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31504 | MEDIUM5.35 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-40918 | MEDIUM5.35 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-26465 | MEDIUM5.3 | openssh-client 1:9.2p1-2+deb12u4 fixed in 1:9.2p1-2+deb12u5 | 61.2% Actively Exploited | Post-Exploit |
| CVE-2019-6110 | MEDIUM5.3 | openssh-client 1:9.2p1-2+deb12u4 No fix yet | 57.6% Actively Exploited | Post-Exploit |
| CVE-2024-12243 | MEDIUM5.3 | libgnutls30 3.7.9-2+deb12u3 fixed in 3.7.9-2+deb12u4 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42015 | MEDIUM5.3 | libgnutls30 3.7.9-2+deb12u3 fixed in 3.7.9-2+deb12u7 | — | Directly Exposed |
| CVE-2026-3276 | MEDIUM5.3 | libpython3.11-minimal 3.11.2-6+deb12u5 No fix yet | — | Directly Exposed |
| CVE-2026-3276 | MEDIUM5.3 | libpython3.11-stdlib 3.11.2-6+deb12u5 No fix yet | — | Directly Exposed |
| CVE-2025-21722 | MEDIUM5.27 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40048 | MEDIUM5.27 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40146 | MEDIUM5.27 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68757 | MEDIUM5.27 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71066 | MEDIUM5.27 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23253 | MEDIUM5.27 | linux-libc-dev 6.1.124-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.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid1 2.38.1-5+deb12u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1390 | MEDIUM5.18 | libcap2 1:2.66-4 fixed in 1:2.66-4+deb12u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount1 2.38.1-5+deb12u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | libpython3.11-minimal 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | libpython3.11-stdlib 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid1 2.38.1-5+deb12u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40019 | MEDIUM5.18 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40071 | MEDIUM5.18 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40080 | MEDIUM5.18 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40190 | MEDIUM5.18 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40279 | MEDIUM5.18 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40355 | MEDIUM5.18 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68245 | MEDIUM5.18 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68342 | MEDIUM5.18 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68343 | MEDIUM5.18 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68736 | MEDIUM5.18 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68764 | MEDIUM5.18 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68815 | MEDIUM5.18 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68819 | MEDIUM5.18 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31449 | MEDIUM5.18 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31464 | MEDIUM5.18 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31505 | MEDIUM5.18 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31570 | MEDIUM5.18 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31700 | MEDIUM5.18 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31708 | MEDIUM5.18 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43134 | MEDIUM5.18 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32289 | MEDIUM5.18 | stdlib v1.22.12 fixed in 1.25.9, 1.26.2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31649 | MEDIUM5.1 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.02 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.36-9+deb12u9 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc-bin 2.36-9+deb12u9 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-dev-bin 2.36-9+deb12u9 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc-dev-bin 2.36-9+deb12u9 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.36-9+deb12u9 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc6 2.36-9+deb12u9 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6-dev 2.36-9+deb12u9 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc6-dev 2.36-9+deb12u9 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.02 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.02 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-10966 | MEDIUM5.02 | libcurl3-gnutls 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-10966 | MEDIUM5.02 | libcurl4 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-50602 | MEDIUM5.02 | libexpat1 2.5.0-1+deb12u1 fixed in 2.5.0-1+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.02 | libgcrypt20 1.10.1-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.02 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libgssapi-krb5-2 1.20.1-2+deb12u2 fixed in 1.20.1-2+deb12u4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM5.02 | libgssapi-krb5-2 1.20.1-2+deb12u2 fixed in 1.20.1-2+deb12u5 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libgssapi-krb5-2 1.20.1-2+deb12u2 fixed in 1.20.1-2+deb12u5 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssapi-krb5-2 1.20.1-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.02 | libgssapi-krb5-2 1.20.1-2+deb12u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libk5crypto3 1.20.1-2+deb12u2 fixed in 1.20.1-2+deb12u4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM5.02 | libk5crypto3 1.20.1-2+deb12u2 fixed in 1.20.1-2+deb12u5 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libk5crypto3 1.20.1-2+deb12u2 fixed in 1.20.1-2+deb12u5 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libk5crypto3 1.20.1-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.02 | libk5crypto3 1.20.1-2+deb12u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libkrb5-3 1.20.1-2+deb12u2 fixed in 1.20.1-2+deb12u4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM5.02 | libkrb5-3 1.20.1-2+deb12u2 fixed in 1.20.1-2+deb12u5 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libkrb5-3 1.20.1-2+deb12u2 fixed in 1.20.1-2+deb12u5 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-3 1.20.1-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.02 | libkrb5-3 1.20.1-2+deb12u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libkrb5support0 1.20.1-2+deb12u2 fixed in 1.20.1-2+deb12u4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM5.02 | libkrb5support0 1.20.1-2+deb12u2 fixed in 1.20.1-2+deb12u5 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libkrb5support0 1.20.1-2+deb12u2 fixed in 1.20.1-2+deb12u5 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5support0 1.20.1-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.02 | libkrb5support0 1.20.1-2+deb12u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40909 | MEDIUM5.02 | libperl5.36 5.36.0-7+deb12u1 fixed in 5.36.0-7+deb12u3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.02 | libssl3 3.0.15-1~deb12u1 fixed in 3.0.19-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | libssl3 3.0.15-1~deb12u1 fixed in 3.0.18-1~deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | libssl3 3.0.15-1~deb12u1 fixed in 3.0.18-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.02 | libtasn1-6 4.19.0-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40083 | MEDIUM5.02 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40242 | MEDIUM5.02 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40324 | MEDIUM5.02 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-3714 | MEDIUM5.02 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | MEDIUM5 | openssl 3.0.15-1~deb12u1 fixed in 3.0.19-1~deb12u2 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | MEDIUM5 | python3.11 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | MEDIUM5 | python3.11 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | MEDIUM5 | python3.11-minimal 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | MEDIUM5 | python3.11-minimal 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-42250 | MEDIUM5 | libbz2-1.0 1.0.8-5+b1 No fix yet | — | Directly Exposed |
| CVE-2004-0230 | MEDIUM5 | linux-libc-dev 6.1.124-1 No fix yet | 9.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-53706 | MEDIUM4.93 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-54107 | MEDIUM4.93 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-54141 | MEDIUM4.93 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39994 | MEDIUM4.93 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39998 | MEDIUM4.93 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40111 | MEDIUM4.93 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40118 | MEDIUM4.93 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40167 | MEDIUM4.93 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40194 | MEDIUM4.93 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40201 | MEDIUM4.93 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40214 | MEDIUM4.93 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40272 | MEDIUM4.93 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40323 | MEDIUM4.93 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68742 | MEDIUM4.93 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23239 | MEDIUM4.93 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23240 | MEDIUM4.93 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23271 | MEDIUM4.93 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23317 | MEDIUM4.93 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31392 | MEDIUM4.93 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31414 | MEDIUM4.93 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31426 | MEDIUM4.93 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43279 | MEDIUM4.93 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31484 | MEDIUM4.86 | perl 5.36.0-7+deb12u1 fixed in 5.36.0-7+deb12u3 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31484 | MEDIUM4.86 | perl-base 5.36.0-7+deb12u1 fixed in 5.36.0-7+deb12u3 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31484 | MEDIUM4.86 | perl-modules-5.36 5.36.0-7+deb12u1 fixed in 5.36.0-7+deb12u3 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3783 | MEDIUM4.84 | libcurl3-gnutls 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3783 | MEDIUM4.84 | libcurl4 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-49569 | MEDIUM4.84 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40319 | MEDIUM4.84 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-23039 | MEDIUM4.84 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-2541 | MEDIUM4.8 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 3.8% Low-Moderate Risk | Post-ExploitContext importance: MEDIUM |
| CVE-2025-1178 | MEDIUM4.76 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-9230 | MEDIUM4.76 | libssl3 3.0.15-1~deb12u1 fixed in 3.0.17-1~deb12u3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-28956 | MEDIUM4.76 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36350 | MEDIUM4.76 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-36357 | MEDIUM4.76 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68801 | MEDIUM4.76 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68816 | MEDIUM4.76 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48962 | MEDIUM4.68 | perl 5.36.0-7+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2026-48962 | MEDIUM4.68 | perl-base 5.36.0-7+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2026-48962 | MEDIUM4.68 | perl-modules-5.36 5.36.0-7+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2022-27943 | MEDIUM4.67 | libasan8 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libatomic1 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-20673 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-9996 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | <0.1% 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.1% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc-bin 2.36-9+deb12u9 fixed in 2.36-9+deb12u10 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc-dev-bin 2.36-9+deb12u9 fixed in 2.36-9+deb12u10 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc6 2.36-9+deb12u9 fixed in 2.36-9+deb12u10 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc6-dev 2.36-9+deb12u9 fixed in 2.36-9+deb12u10 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libcc1-0 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-20673 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-9996 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-20673 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-9996 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | <0.1% 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+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32776 | MEDIUM4.67 | libexpat1 2.5.0-1+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | MEDIUM4.67 | libexpat1 2.5.0-1+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | MEDIUM4.67 | libexpat1 2.5.0-1+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52426 | MEDIUM4.67 | libexpat1 2.5.0-1+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc-12-dev 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc-s1 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgomp1 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-20673 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-9996 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26462 | MEDIUM4.67 | libgssapi-krb5-2 1.20.1-2+deb12u2 fixed in 1.20.1-2+deb12u3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libitm1 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26462 | MEDIUM4.67 | libk5crypto3 1.20.1-2+deb12u2 fixed in 1.20.1-2+deb12u3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26462 | MEDIUM4.67 | libkrb5-3 1.20.1-2+deb12u2 fixed in 1.20.1-2+deb12u3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26462 | MEDIUM4.67 | libkrb5support0 1.20.1-2+deb12u2 fixed in 1.20.1-2+deb12u3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | liblsan0 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount1 2.38.1-5+deb12u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-22365 | MEDIUM4.67 | libpam-modules 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-22365 | MEDIUM4.67 | libpam-runtime 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-22365 | MEDIUM4.67 | libpam0g 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM4.67 | libpython3.11-minimal 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6075 | MEDIUM4.67 | libpython3.11-minimal 3.11.2-6+deb12u5 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+deb12u5 fixed in 3.11.2-6+deb12u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6075 | MEDIUM4.67 | libpython3.11-stdlib 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libquadmath0 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-29088 | MEDIUM4.67 | libsqlite3-0 3.40.1-2+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM4.67 | libssl3 3.0.15-1~deb12u1 fixed in 3.0.18-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libstdc++-12-dev 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libstdc++6 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libtsan2 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libubsan1 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.38.1-5+deb12u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40347 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68192 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68291 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68307 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-0597 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-23005 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31082 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-37454 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-4133 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52485 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52590 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52591 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52625 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52629 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52648 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52658 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52671 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52676 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52761 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52770 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52797 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52857 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52888 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52920 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53149 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53228 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53231 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53261 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53292 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53336 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53353 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53367 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53394 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53421 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53424 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53429 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53460 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53491 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53523 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53529 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53538 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53545 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53574 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53627 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53846 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53989 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53999 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-54013 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-54271 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-54280 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-6039 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-2193 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-25740 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26596 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26618 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26656 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26670 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26677 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26691 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26740 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26756 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26767 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26783 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26799 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26807 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26822 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26841 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26866 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26876 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26902 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26947 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26948 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26953 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26962 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-27010 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-27011 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-27012 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-27041 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-27056 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-27057 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-27062 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-27079 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-35784 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-35790 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-35794 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-35799 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-35808 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-35860 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-35904 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-35924 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-35931 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-35942 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-35945 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-35946 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-35951 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-35961 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-36903 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-36908 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-36911 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-36922 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-36951 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-38557 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-38564 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-38594 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-38608 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-38611 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-38620 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-38622 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-38625 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-40945 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-40965 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-40969 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-40973 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-40975 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-40998 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-40999 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-41008 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-41023 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-41031 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-41082 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-42069 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-42079 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-42122 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-42128 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-42129 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-42139 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-42239 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-42241 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-42243 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-42279 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-42317 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-43819 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-43824 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-43831 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-43840 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-43850 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-43872 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-43899 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-43901 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-43913 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-44963 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-45001 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-45015 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-46678 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-46681 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-46698 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-46727 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-46728 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-46730 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-46733 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-46742 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-46751 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-46753 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-46754 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-46760 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-46765 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-46772 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-46775 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-46776 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-46806 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-46808 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-46816 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-46834 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-46860 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-47141 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-47658 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-47661 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-47662 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-47664 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-47666 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-47703 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-47704 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-47736 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-47752 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-47753 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-47754 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-47794 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-47809 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-49568 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-49893 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-49901 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-49906 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-49908 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-49910 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-49914 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-49916 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-49918 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-49919 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-49920 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-49921 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-49922 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-49923 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-49926 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-49940 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-49945 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-49968 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-49970 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-49988 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-49994 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-50009 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-50017 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-50028 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-50056 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-50111 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-50166 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-50285 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-50289 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-50298 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-50304 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-52559 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-52560 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53051 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53056 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53079 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53085 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53089 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53090 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53091 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53094 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53114 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53128 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53134 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53187 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53195 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53209 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53219 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53221 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53224 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53229 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53234 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53685 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53687 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-54683 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56544 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56549 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56565 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56566 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56583 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56588 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56591 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56592 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56599 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56611 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56641 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56647 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56657 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56692 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56703 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56712 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56719 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56742 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56758 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57804 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57809 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57834 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57872 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57883 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57888 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57895 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57916 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57922 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57924 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57939 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57940 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57948 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57949 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57973 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57975 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57976 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57977 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57978 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57981 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57986 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57993 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57996 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57997 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57999 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58001 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58005 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58006 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58009 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58010 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58011 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58012 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58016 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58017 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58020 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58051 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58052 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58053 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58056 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58058 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58061 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58063 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58068 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58071 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58076 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58079 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58080 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58083 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58085 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58086 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58089 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58090 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58094 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58095 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58096 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58097 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58098 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58100 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58237 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58241 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21634 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21635 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21636 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21637 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21638 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21639 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21640 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21645 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21646 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21648 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21649 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21653 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21656 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21658 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21660 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21662 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21664 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21665 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21666 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21667 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21668 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21669 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21673 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21675 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21676 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21678 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21681 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21682 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21683 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21684 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21689 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21690 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21693 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21694 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21696 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21697 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21699 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21705 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21706 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21707 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21708 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21711 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21712 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21716 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21721 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21723 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21725 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21728 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21729 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21736 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21738 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21744 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21745 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21748 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21749 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21750 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21758 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21760 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21763 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21765 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21766 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21767 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21768 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21775 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21776 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21779 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21781 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21787 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21790 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21792 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21795 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21796 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21799 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21801 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21802 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21804 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21806 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21814 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21816 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21819 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21820 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21821 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21823 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21826 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21829 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21830 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21831 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21832 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21835 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21836 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21838 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21839 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21844 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21846 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21848 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21853 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21859 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21861 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21862 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21864 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21865 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21866 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21870 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21871 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21872 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21875 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21877 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21878 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21881 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21885 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21888 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21891 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21894 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21898 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21899 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21904 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21907 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21909 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21910 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21912 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21913 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21916 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21917 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21918 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21922 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21924 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21925 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21926 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21931 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21935 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21936 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21937 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21941 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21944 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21948 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21949 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21951 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21955 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21956 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21957 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21959 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21960 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21961 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21962 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21963 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21964 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21970 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21971 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21972 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21975 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21976 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21978 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21980 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21981 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21986 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21992 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21994 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21996 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21997 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22005 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22007 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22008 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22010 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22014 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22015 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22018 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22021 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22025 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22026 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22028 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22033 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22037 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22042 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22043 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22044 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22045 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22048 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22049 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22053 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22054 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22055 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22057 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22058 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22062 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22063 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22066 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22070 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22071 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22072 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22073 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22075 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22081 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22086 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22089 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22090 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22093 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22095 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22103 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22105 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22109 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22111 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22113 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22119 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22125 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22127 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23129 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23130 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23131 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23132 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23136 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23138 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23140 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23141 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23143 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23144 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23145 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23146 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23147 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23148 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23150 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23155 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23159 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23160 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23161 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23163 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37740 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37741 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37742 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37747 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37748 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37756 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37757 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37758 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37765 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37766 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37767 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37768 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37769 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37770 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37771 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37772 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37773 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37775 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37781 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37787 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37788 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37790 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37792 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37794 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37800 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37801 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37802 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37805 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37806 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37807 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37808 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37811 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37812 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37815 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37818 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37820 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37824 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37829 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37830 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37833 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37834 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37836 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37841 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37842 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37844 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37850 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37851 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37852 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37853 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37856 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37857 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37858 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37859 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37860 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37862 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37864 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37865 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37867 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37871 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37875 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37880 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37881 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37883 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37889 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37893 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37897 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37901 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37905 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37909 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37911 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37912 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37917 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37925 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37929 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37930 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37931 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37932 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37936 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37937 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37938 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37940 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37945 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37948 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37949 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37951 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37953 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37956 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37958 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37959 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37961 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37962 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37963 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37964 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37967 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37968 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37969 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37970 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37972 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37977 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37980 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37982 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37983 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37989 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37990 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37992 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37994 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.139-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37995 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.139-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37997 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.139-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37998 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.139-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38001 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38003 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38005 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38006 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38007 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38009 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38014 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38015 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38018 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38020 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38023 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38029 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38031 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38034 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38035 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38037 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38038 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38039 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38040 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38041 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38042 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38043 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38044 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38045 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38057 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38058 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38059 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38061 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38062 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38063 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38064 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38065 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38066 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38067 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38071 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38072 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38074 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38075 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38080 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38084 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38086 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38090 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38094 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38095 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38096 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38097 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38100 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38105 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38113 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38115 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38119 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38120 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38122 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38124 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38125 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38126 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38127 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38132 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38135 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38136 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38138 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38140 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38142 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38143 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38145 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38147 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38148 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38151 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38152 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38158 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38160 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38161 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38162 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38163 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38165 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38166 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38167 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38170 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38173 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38174 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38177 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.139-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38181 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38184 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38185 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38190 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38191 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38192 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38193 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38194 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38195 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38197 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38200 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38202 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38203 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38207 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38214 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38215 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38218 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38219 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38222 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38225 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38229 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38231 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38237 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38244 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38246 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38251 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38260 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38261 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38262 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38263 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38264 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38272 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38273 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38275 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38277 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38282 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38283 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38285 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38293 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38300 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38303 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38304 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38305 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38310 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38311 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38312 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38319 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38322 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38324 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38326 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38328 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38331 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38332 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38333 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38334 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38335 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38336 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38337 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38344 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38345 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38347 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38354 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38359 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38362 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38363 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38364 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38371 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38382 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38384 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38386 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38387 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38391 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38399 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38400 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38404 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38406 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38408 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38409 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38410 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38412 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38418 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38419 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38420 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38424 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38426 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38429 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38430 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38436 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38438 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38439 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38441 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38444 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38449 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38451 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38455 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38457 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38458 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38460 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38465 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38466 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38467 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38468 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38470 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38472 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38473 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38474 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38478 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38480 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38481 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38487 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38491 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38495 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38498 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38499 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38503 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38507 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38510 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38513 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38514 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38516 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38520 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38528 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38531 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38539 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38540 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38542 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38543 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38544 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38546 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38553 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38560 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38562 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38569 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38575 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38576 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38577 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38578 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38581 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38583 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38587 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38588 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38590 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38591 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38597 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38601 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38602 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38604 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38608 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38609 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38610 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38612 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38614 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38615 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38622 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38623 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38624 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38626 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38630 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38634 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38635 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38637 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38639 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38643 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38644 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38645 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38650 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38659 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38663 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38664 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38665 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38668 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38671 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38678 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38683 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38684 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38691 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38692 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38693 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38694 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38695 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38696 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38698 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38700 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38701 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38705 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38706 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38709 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38710 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38711 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38712 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38716 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38721 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38723 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38725 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38727 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38732 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38735 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39675 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39676 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39677 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39681 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39684 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39692 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39693 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39694 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39703 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39705 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39706 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39707 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39709 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39714 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39715 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39716 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39718 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39720 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39721 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39724 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39728 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39731 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39732 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39734 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39736 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39737 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39742 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39746 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39747 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39748 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39752 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39756 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39762 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39763 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39764 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39767 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39770 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39772 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39773 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39779 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39782 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39787 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39789 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39794 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39795 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39798 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39800 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39801 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39805 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39808 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39812 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39819 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39827 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39829 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39833 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39838 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39842 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39843 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39844 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39845 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39846 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39847 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39848 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39850 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39851 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39857 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39865 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39876 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39885 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39886 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39889 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39894 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39902 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39907 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39909 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39910 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39914 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39916 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39920 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39923 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39925 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39929 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39931 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39932 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39933 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39934 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39937 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39938 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39940 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39942 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39946 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39947 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39949 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39953 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39989 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40005 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40020 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40026 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40027 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40029 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40030 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40040 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40044 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40051 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40053 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40070 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40075 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40078 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40102 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40104 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40109 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40115 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40140 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40153 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40160 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40164 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40171 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40211 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40231 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40251 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40264 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40280 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40283 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40284 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40292 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40293 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40297 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40300 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40325 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40339 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40363 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68176 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68185 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68188 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68209 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68211 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68223 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68229 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68231 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68236 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68259 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68261 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68265 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68283 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68304 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68310 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68331 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68337 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68340 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68358 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68365 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68372 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68379 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68725 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68774 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68776 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68803 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68814 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68821 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68823 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71064 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71077 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71079 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71081 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71083 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71084 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71085 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71087 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71088 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71094 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71095 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71096 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71097 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71098 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71102 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71104 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71105 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71108 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71109 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71113 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71114 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71118 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71119 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71120 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71121 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71125 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71126 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71127 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71129 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71130 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71131 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71132 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71138 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71144 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71147 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71150 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71154 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71160 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71161 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71163 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71180 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71182 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71183 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71184 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71185 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71186 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71188 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71189 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71190 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71191 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71200 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71202 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71222 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71227 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71232 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71233 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71235 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71236 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71237 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71265 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71266 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71267 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71268 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71269 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71272 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71273 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71285 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71287 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71288 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71289 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71291 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71292 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71295 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71297 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22976 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22977 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22979 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22982 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22990 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22991 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22992 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22994 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22996 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22997 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22999 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23000 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23003 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23005 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23006 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23011 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23019 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23020 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23021 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23026 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23031 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23038 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23047 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23058 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23060 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23061 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23063 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23064 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23066 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23069 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23075 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23080 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23084 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23085 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23086 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23087 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23088 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23090 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23091 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23093 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23095 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23096 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23097 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23100 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23103 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23105 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23107 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23108 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23113 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23116 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23119 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23120 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23121 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23124 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23125 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23128 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23133 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23137 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23138 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23139 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23140 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23141 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23142 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23144 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23145 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23146 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23150 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23154 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23157 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23164 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23168 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23170 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23172 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23190 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23198 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23202 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23205 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23206 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23213 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23214 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23220 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23222 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23228 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23229 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23230 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23236 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23237 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23238 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23242 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23247 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23255 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23256 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23257 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23258 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23262 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23264 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23265 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23266 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23267 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23272 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23273 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23274 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23276 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23277 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23278 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23279 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23284 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23286 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23287 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23289 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23290 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23291 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23292 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23293 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23296 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23298 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23300 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23303 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23304 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23306 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23307 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23310 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23312 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23321 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23324 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23330 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23335 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23336 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23339 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23340 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23346 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23351 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23352 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23356 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23357 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23362 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23365 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23367 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23368 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23370 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23371 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23374 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23379 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23381 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23382 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23389 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23391 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23396 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23398 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23399 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23401 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23403 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23404 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23405 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23409 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23414 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23419 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23420 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23426 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23434 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23438 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23439 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23442 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23444 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23446 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23449 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23460 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23462 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23465 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23468 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23472 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23474 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23475 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31391 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31400 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31403 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31407 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31410 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31411 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31412 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31415 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31416 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31418 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31420 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31421 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31422 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31423 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31424 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31425 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31427 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31428 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31434 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31441 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31446 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31447 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31448 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31450 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31451 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31453 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31454 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31458 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31462 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31467 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31469 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31473 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31480 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31483 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31487 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31492 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31495 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31496 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31497 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31498 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31503 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31507 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31509 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31510 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31512 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31515 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31518 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31519 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31520 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31521 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31522 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31524 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31531 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31533 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31537 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31540 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31545 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31546 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31548 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31549 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31550 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31551 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31552 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31555 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31557 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31560 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31565 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31577 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31579 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31585 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31590 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31592 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31594 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31595 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31596 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31599 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31603 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31605 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31606 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31610 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31615 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31616 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31617 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31618 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31619 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31623 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31624 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31625 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31628 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31630 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31634 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31637 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31642 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31648 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31651 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31655 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31658 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31660 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31661 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31662 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31664 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31665 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31667 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31670 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31671 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31672 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31673 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31674 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31675 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31676 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31677 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31678 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31679 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31680 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31681 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31682 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31684 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31687 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31689 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31692 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31698 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31699 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31701 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31704 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31721 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31722 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31723 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31724 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31725 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31726 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31737 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31738 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31749 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31752 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31754 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31755 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31756 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31758 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31762 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31763 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31767 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31770 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31771 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31773 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31777 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31779 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31781 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43009 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43010 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43013 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43014 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43016 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43017 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43018 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43022 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43024 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43025 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43026 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43028 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43032 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43033 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43035 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43036 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43041 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43042 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43043 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43046 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43048 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43054 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43057 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43058 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43060 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43061 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43062 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43064 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43065 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43066 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43068 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43069 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43071 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43072 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43073 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43077 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43079 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43080 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43083 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43085 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43088 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43089 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43091 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43093 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43094 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43098 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43099 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43101 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43103 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43104 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43105 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43107 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43111 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43112 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43113 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43114 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43115 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43118 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43119 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43123 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43124 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43129 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43130 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43132 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43133 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43135 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43136 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43137 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43139 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43140 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43143 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43145 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43147 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43148 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43149 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43152 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43153 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43156 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43157 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43159 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43161 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43162 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43167 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43168 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43170 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43171 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43172 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43173 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43180 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43182 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43183 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43187 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43200 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43202 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43204 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43209 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43213 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43214 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43215 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43216 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43218 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43219 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43221 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43223 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43225 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43227 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43230 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43231 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43234 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43238 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43240 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43242 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43244 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43246 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43251 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43252 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43255 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43257 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43261 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43262 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43264 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43265 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43266 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43268 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43269 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43270 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43271 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43273 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43277 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43278 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43287 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43288 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43289 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43295 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43296 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43299 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43302 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43308 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43309 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43310 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43312 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43313 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43314 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43315 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43316 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43317 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43318 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43327 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43333 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43338 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43340 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43343 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43344 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43350 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43352 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43353 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43355 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43357 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43359 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43360 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43361 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43362 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43363 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43365 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43366 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43381 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43382 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43387 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43405 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43406 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43407 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43409 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43411 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43412 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43413 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43416 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43420 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43421 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43424 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43425 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43428 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43429 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43432 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43436 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43437 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43441 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43443 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43445 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43451 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43452 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43455 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43456 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43457 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43459 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43466 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43468 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43469 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43472 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43473 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43475 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2008-2544 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-4915 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-4916 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-4917 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2014-9892 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2014-9900 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2016-10723 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2016-8660 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-13693 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-13694 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-12928 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-12378 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-12379 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-12380 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-12381 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-12382 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-12455 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-4543 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31081 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31085 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-4134 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52653 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53823 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53857 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-54030 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-54088 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-35843 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-54458 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39990 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40010 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40042 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40049 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40057 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40088 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40092 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40094 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40099 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40100 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40103 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40105 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40125 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40196 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40205 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40219 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40253 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40346 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40360 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68171 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68173 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68194 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68200 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68204 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68206 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68218 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68219 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68227 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68233 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68244 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68288 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68295 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68308 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68321 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68334 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68336 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68345 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68363 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68378 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68732 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68734 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68753 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68758 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68778 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68780 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68783 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68785 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68794 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68795 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68798 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68813 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68818 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68820 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68822 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71194 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31486 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43030 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43194 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43211 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43253 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43419 | MEDIUM4.67 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g 1:1.2.13.dfsg-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32288 | MEDIUM4.67 | stdlib v1.22.12 fixed in 1.25.9, 1.26.2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-38428 | MEDIUM4.64 | wget 1.21.3-1+b2 fixed in 1.21.3-1+deb12u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-2379 | MEDIUM4.59 | libcurl3-gnutls 7.88.1-10+deb12u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-2379 | MEDIUM4.59 | libcurl4 7.88.1-10+deb12u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22871 | MEDIUM4.59 | stdlib v1.22.12 fixed in 1.23.8, 1.24.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27142 | MEDIUM4.59 | stdlib v1.22.12 fixed in 1.25.8, 1.26.1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-39826 | MEDIUM4.59 | stdlib v1.22.12 fixed in 1.25.10, 1.26.3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42497 | MEDIUM4.5 | perl 5.36.0-7+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2026-9538 | MEDIUM4.5 | perl 5.36.0-7+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2026-42497 | MEDIUM4.5 | perl-base 5.36.0-7+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2026-9538 | MEDIUM4.5 | perl-base 5.36.0-7+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2026-42497 | MEDIUM4.5 | perl-modules-5.36 5.36.0-7+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2026-9538 | MEDIUM4.5 | perl-modules-5.36 5.36.0-7+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2025-1147 | MEDIUM4.5 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid1 2.38.1-5+deb12u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc-bin 2.36-9+deb12u9 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-bin 2.36-9+deb12u9 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM4.5 | libc-bin 2.36-9+deb12u9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-1010025 | MEDIUM4.5 | libc-bin 2.36-9+deb12u9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc-dev-bin 2.36-9+deb12u9 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-dev-bin 2.36-9+deb12u9 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM4.5 | libc-dev-bin 2.36-9+deb12u9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-1010025 | MEDIUM4.5 | libc-dev-bin 2.36-9+deb12u9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc6 2.36-9+deb12u9 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6 2.36-9+deb12u9 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM4.5 | libc6 2.36-9+deb12u9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-1010025 | MEDIUM4.5 | libc6 2.36-9+deb12u9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc6-dev 2.36-9+deb12u9 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6-dev 2.36-9+deb12u9 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM4.5 | libc6-dev 2.36-9+deb12u9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-1010025 | MEDIUM4.5 | libc6-dev 2.36-9+deb12u9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4873 | MEDIUM4.5 | libcurl3-gnutls 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6253 | MEDIUM4.5 | libcurl3-gnutls 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7168 | MEDIUM4.5 | libcurl3-gnutls 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4873 | MEDIUM4.5 | libcurl4 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6253 | MEDIUM4.5 | libcurl4 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7168 | MEDIUM4.5 | libcurl4 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-59375 | MEDIUM4.5 | libexpat1 2.5.0-1+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14831 | MEDIUM4.5 | libgnutls30 3.7.9-2+deb12u3 fixed in 3.7.9-2+deb12u6 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-32989 | MEDIUM4.5 | libgnutls30 3.7.9-2+deb12u3 fixed in 3.7.9-2+deb12u5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | liblzma5 5.4.1-0.2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount1 2.38.1-5+deb12u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12084 | MEDIUM4.5 | libpython3.11-minimal 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.11-minimal 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3446 | MEDIUM4.5 | libpython3.11-minimal 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12084 | MEDIUM4.5 | libpython3.11-stdlib 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.11-stdlib 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3446 | MEDIUM4.5 | libpython3.11-stdlib 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 252.33-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 252.33-1~deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 252.33-1~deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-12133 | MEDIUM4.5 | libtasn1-6 4.19.0-2 fixed in 4.19.0-2+deb12u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libudev1 252.33-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libudev1 252.33-1~deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libudev1 252.33-1~deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.38.1-5+deb12u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-36881 | MEDIUM4.5 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39968 | MEDIUM4.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39972 | MEDIUM4.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40204 | MEDIUM4.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68367 | MEDIUM4.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71225 | MEDIUM4.5 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23457 | MEDIUM4.5 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22873 | MEDIUM4.5 | stdlib v1.22.12 fixed in 1.23.9, 1.24.3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-47912 | MEDIUM4.5 | stdlib v1.22.12 fixed in 1.24.8, 1.25.2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-58185 | MEDIUM4.5 | stdlib v1.22.12 fixed in 1.24.8, 1.25.2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-58187 | MEDIUM4.5 | stdlib v1.22.12 fixed in 1.24.9, 1.25.3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-58188 | MEDIUM4.5 | stdlib v1.22.12 fixed in 1.24.8, 1.25.2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-58189 | MEDIUM4.5 | stdlib v1.22.12 fixed in 1.24.8, 1.25.2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61723 | MEDIUM4.5 | stdlib v1.22.12 fixed in 1.24.8, 1.25.2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61724 | MEDIUM4.5 | stdlib v1.22.12 fixed in 1.24.8, 1.25.2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61725 | MEDIUM4.5 | stdlib v1.22.12 fixed in 1.24.8, 1.25.2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61730 | MEDIUM4.5 | stdlib v1.22.12 fixed in 1.24.12, 1.25.6 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-58186 | MEDIUM4.5 | stdlib v1.22.12 fixed in 1.24.8, 1.25.2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-52005 | MEDIUM4.49 | git 1:2.39.5-0+deb12u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-39970 | MEDIUM4.42 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40338 | MEDIUM4.42 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40343 | MEDIUM4.42 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-4516 | MEDIUM4.33 | libpython3.11-minimal 3.11.2-6+deb12u5 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+deb12u5 fixed in 3.11.2-6+deb12u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40178 | MEDIUM4.33 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71193 | MEDIUM4.33 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23035 | MEDIUM4.33 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-3389 | MEDIUM4.3 | libgnutls30 3.7.9-2+deb12u3 No fix yet | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-46901 | MEDIUM4.3 | libsvn1 1.14.2-4+b2 fixed in 1.14.2-4+deb12u1 | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.1% 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+deb12u9 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.36-9+deb12u9 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-dev-bin 2.36-9+deb12u9 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-dev-bin 2.36-9+deb12u9 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.36-9+deb12u9 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.36-9+deb12u9 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6-dev 2.36-9+deb12u9 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6-dev 2.36-9+deb12u9 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.1% 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.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40121 | MEDIUM4.25 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23180 | MEDIUM4.25 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2010-4563 | MEDIUM4.25 | linux-libc-dev 6.1.124-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.2% Theoretical Threat | Post-Exploit |
| CVE-2005-3660 | MEDIUM4.17 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | MEDIUM4.13 | curl 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-35385 | MEDIUM4.13 | openssh-client 1:9.2p1-2+deb12u4 fixed in 1:9.2p1-2+deb12u10 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-35386 | MEDIUM4.13 | openssh-client 1:9.2p1-2+deb12u4 fixed in 1:9.2p1-2+deb12u10 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-35414 | MEDIUM4.13 | openssh-client 1:9.2p1-2+deb12u4 fixed in 1:9.2p1-2+deb12u10 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-28387 | MEDIUM4.13 | openssl 3.0.15-1~deb12u1 fixed in 3.0.19-1~deb12u2 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-31486 | MEDIUM4.13 | perl 5.36.0-7+deb12u1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-31486 | MEDIUM4.13 | perl-base 5.36.0-7+deb12u1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-31486 | MEDIUM4.13 | perl-modules-5.36 5.36.0-7+deb12u1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | MEDIUM4.13 | python3.11 3.11.2-6+deb12u5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | MEDIUM4.13 | python3.11-minimal 3.11.2-6+deb12u5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-48384 | MEDIUM4.08 | git 1:2.39.5-0+deb12u2 fixed in 1:2.39.5-0+deb12u3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-0938 | MEDIUM4.08 | python3.11 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u6 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0938 | MEDIUM4.08 | python3.11-minimal 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u6 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-4039 | MEDIUM4.08 | libasan8 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libatomic1 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libcc1-0 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-10148 | MEDIUM4.08 | libcurl3-gnutls 7.88.1-10+deb12u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14017 | MEDIUM4.08 | libcurl3-gnutls 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-10148 | MEDIUM4.08 | libcurl4 7.88.1-10+deb12u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14017 | MEDIUM4.08 | libcurl4 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libgcc-12-dev 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libgcc-s1 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libgomp1 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libitm1 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | liblsan0 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | MEDIUM4.08 | libpython3.11-minimal 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.08 | libpython3.11-minimal 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | MEDIUM4.08 | libpython3.11-stdlib 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.08 | libpython3.11-stdlib 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libquadmath0 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libstdc++-12-dev 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libstdc++6 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libtsan2 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libubsan1 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.38.1-5+deb12u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15224 | MEDIUM4 | libcurl3-gnutls 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15224 | MEDIUM4 | libcurl4 7.88.1-10+deb12u8 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.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount1 2.38.1-5+deb12u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-10041 | MEDIUM4 | libpam-modules 1.5.2-6+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-10041 | MEDIUM4 | libpam-runtime 1.5.2-6+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-10041 | MEDIUM4 | libpam0g 1.5.2-6+deb12u1 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-2024-13176 | MEDIUM4 | libssl3 3.0.15-1~deb12u1 fixed in 3.0.16-1~deb12u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4 | libssl3 3.0.15-1~deb12u1 fixed in 3.0.18-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-4598 | MEDIUM4 | libsystemd0 252.33-1~deb12u1 fixed in 252.38-1~deb12u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-4598 | MEDIUM4 | libudev1 252.33-1~deb12u1 fixed in 252.38-1~deb12u1 | 0.1% 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.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52771 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53447 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-24855 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-24864 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26869 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-27408 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-36024 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-36927 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-36949 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-39508 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-42107 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-46787 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-46870 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-49998 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-50135 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53124 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53176 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53178 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56729 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57857 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57913 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57974 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21651 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21655 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21688 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21701 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21732 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21825 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21892 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21938 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21943 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21947 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.133-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22027 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22050 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22060 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22115 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23151 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37920 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37985 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38048 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38078 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38083 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38085 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38104 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38112 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38232 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38234 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38365 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38393 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38448 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38461 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38462 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38477 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38515 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38524 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38561 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38617 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38681 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38687 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38717 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39673 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39697 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39713 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39726 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39754 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39813 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39825 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39927 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39961 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39977 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39980 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39996 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40006 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40011 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40016 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40039 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40056 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40085 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40110 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40120 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40134 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40139 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40179 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40187 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40197 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40215 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40220 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40244 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40252 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40254 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40331 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40342 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68214 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68239 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68241 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68296 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68312 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68745 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71074 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71111 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71274 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23004 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23071 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23101 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23110 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23118 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23126 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23167 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23169 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23207 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23212 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23302 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23348 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23394 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23452 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23463 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31389 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31393 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31466 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31523 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31697 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31728 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31751 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43047 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43053 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43163 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43275 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43342 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43383 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43430 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43439 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43448 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-0630 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2019-16230 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-16234 | MEDIUM4 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68264 | MEDIUM4 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | LOW3.98 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-6020 | LOW3.98 | libpam-modules-bin 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW3.98 | ncurses-bin 6.4-4 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-15213 | LOW3.91 | linux-libc-dev 6.1.124-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4010 | LOW3.91 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2012-4542 | LOW3.91 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2008-3234 | LOW3.9 | openssh-client 1:9.2p1-2+deb12u4 No fix yet | 4.6% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0840 | LOW3.82 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW3.82 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-0840 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-0840 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | curl 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | curl 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-24975 | LOW3.82 | git 1:2.39.5-0+deb12u2 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-3497 | LOW3.82 | openssh-client 1:9.2p1-2+deb12u4 fixed in 1:9.2p1-2+deb12u9 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69421 | LOW3.82 | openssl 3.0.15-1~deb12u1 fixed in 3.0.18-1~deb12u2 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-28388 | LOW3.82 | openssl 3.0.15-1~deb12u1 fixed in 3.0.19-1~deb12u2 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-28389 | LOW3.82 | openssl 3.0.15-1~deb12u1 fixed in 3.0.19-1~deb12u2 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-28390 | LOW3.82 | openssl 3.0.15-1~deb12u1 fixed in 3.0.19-1~deb12u2 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-13836 | LOW3.82 | python3.11 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69534 | LOW3.82 | python3.11 3.11.2-6+deb12u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3644 | LOW3.82 | python3.11 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW3.82 | python3.11 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8194 | LOW3.82 | python3.11 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-13836 | LOW3.82 | python3.11-minimal 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69534 | LOW3.82 | python3.11-minimal 3.11.2-6+deb12u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3644 | LOW3.82 | python3.11-minimal 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW3.82 | python3.11-minimal 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8194 | LOW3.82 | python3.11-minimal 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11468 | LOW3.82 | libpython3.11-minimal 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0865 | LOW3.82 | libpython3.11-minimal 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | libpython3.11-minimal 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | LOW3.82 | libpython3.11-stdlib 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0865 | LOW3.82 | libpython3.11-stdlib 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | libpython3.11-stdlib 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40308 | LOW3.82 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40312 | LOW3.82 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | LOW3.77 | openssl 3.0.15-1~deb12u1 fixed in 3.0.18-1~deb12u2 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2020-14304 | LOW3.74 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-54263 | LOW3.74 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-38541 | LOW3.74 | linux-libc-dev 6.1.124-1 fixed in 6.1.137-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-42123 | LOW3.74 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40001 | LOW3.74 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40081 | LOW3.74 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40206 | LOW3.74 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40281 | LOW3.74 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68768 | LOW3.74 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-17977 | LOW3.74 | linux-libc-dev 6.1.124-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26661 | LOW3.74 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26662 | LOW3.74 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26672 | LOW3.74 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26757 | LOW3.74 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26758 | LOW3.74 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26768 | LOW3.74 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-36913 | LOW3.74 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40021 | LOW3.74 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40123 | LOW3.74 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40183 | LOW3.74 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40198 | LOW3.74 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40200 | LOW3.74 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23458 | LOW3.74 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22870 | LOW3.74 | stdlib v1.22.12 fixed in 1.23.7, 1.24.1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56406 | LOW3.72 | perl 5.36.0-7+deb12u1 fixed in 5.36.0-7+deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56406 | LOW3.72 | perl-base 5.36.0-7+deb12u1 fixed in 5.36.0-7+deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56406 | LOW3.72 | perl-modules-5.36 5.36.0-7+deb12u1 fixed in 5.36.0-7+deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW3.7 | libapt-pkg6.0 2.6.1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5419 | LOW3.7 | libgnutls30 3.7.9-2+deb12u3 fixed in 3.7.9-2+deb12u7 | — | Directly Exposed |
| CVE-2016-20012 | LOW3.66 | openssh-client 1:9.2p1-2+deb12u4 No fix yet | 14.6% High Exploitation Risk | Post-Exploit |
| CVE-2025-6069 | LOW3.65 | libpython3.11-minimal 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-8291 | LOW3.65 | libpython3.11-minimal 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6069 | LOW3.65 | libpython3.11-stdlib 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-8291 | LOW3.65 | libpython3.11-stdlib 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-45346 | LOW3.65 | libsqlite3-0 3.40.1-2+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2010-5321 | LOW3.65 | linux-libc-dev 6.1.124-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40275 | LOW3.65 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | LOW3.62 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW3.62 | python3.11 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW3.62 | python3.11 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-1299 | LOW3.62 | python3.11 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW3.62 | python3.11-minimal 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW3.62 | python3.11-minimal 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-1299 | LOW3.62 | python3.11-minimal 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | dirmngr 2.2.40-1.1 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 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 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 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 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 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 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 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 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 fixed in 2.2.40-1.1+deb12u2 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8058 | LOW3.57 | libc-bin 2.36-9+deb12u9 fixed in 2.36-9+deb12u13 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | libc-dev-bin 2.36-9+deb12u9 fixed in 2.36-9+deb12u13 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | libc6 2.36-9+deb12u9 fixed in 2.36-9+deb12u13 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | libc6-dev 2.36-9+deb12u9 fixed in 2.36-9+deb12u13 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2020-15719 | LOW3.57 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-41848 | LOW3.57 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-11053 | LOW3.54 | curl 7.88.1-10+deb12u8 fixed in 7.88.1-10+deb12u10 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2020-14145 | LOW3.54 | openssh-client 1:9.2p1-2+deb12u4 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-8376 | LOW3.53 | libperl5.36 5.36.0-7+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2026-8376 | LOW3.53 | perl 5.36.0-7+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2026-8376 | LOW3.53 | perl-base 5.36.0-7+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2026-8376 | LOW3.53 | perl-modules-5.36 5.36.0-7+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2023-45853 | LOW3.53 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2019-16089 | LOW3.48 | linux-libc-dev 6.1.124-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-42156 | LOW3.48 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-42158 | LOW3.48 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40173 | LOW3.48 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-16229 | LOW3.48 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-16231 | LOW3.48 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-16232 | LOW3.48 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-16233 | LOW3.48 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1965 | LOW3.47 | curl 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | curl 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2010-4756 | LOW3.4 | libc-bin 2.36-9+deb12u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc-bin 2.36-9+deb12u9 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | LOW3.4 | libc-dev-bin 2.36-9+deb12u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc-dev-bin 2.36-9+deb12u9 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | LOW3.4 | libc6 2.36-9+deb12u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc6 2.36-9+deb12u9 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | LOW3.4 | libc6-dev 2.36-9+deb12u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc6-dev 2.36-9+deb12u9 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-0725 | LOW3.4 | libcurl3-gnutls 7.88.1-10+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-0725 | LOW3.4 | libcurl4 7.88.1-10+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-9820 | LOW3.4 | libgnutls30 3.7.9-2+deb12u3 fixed in 3.7.9-2+deb12u6 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW3.4 | libssl3 3.0.15-1~deb12u1 fixed in 3.0.18-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | LOW3.37 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53589 | LOW3.37 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53589 | LOW3.37 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2018-20712 | LOW3.31 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-20712 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-20712 | LOW3.31 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2016-2781 | LOW3.31 | coreutils 9.1-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-9681 | LOW3.31 | curl 7.88.1-10+deb12u8 fixed in 7.88.1-10+deb12u9 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | curl 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | curl 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | curl 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | curl 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-50495 | LOW3.31 | ncurses-bin 6.4-4 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-35387 | LOW3.31 | openssh-client 1:9.2p1-2+deb12u4 fixed in 1:9.2p1-2+deb12u10 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-10524 | LOW3.31 | wget 1.21.3-1+b2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | LOW3.28 | libperl5.36 5.36.0-7+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2026-5958 | LOW3.21 | sed 4.9-1 fixed in 4.9-1+deb12u1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-15919 | LOW3.18 | openssh-client 1:9.2p1-2+deb12u4 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3276 | LOW3.18 | python3.11 3.11.2-6+deb12u5 No fix yet | — | Post-Exploit |
| CVE-2026-3276 | LOW3.18 | python3.11-minimal 3.11.2-6+deb12u5 No fix yet | — | Post-Exploit |
| CVE-2025-1152 | LOW3.15 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-41080 | LOW3.15 | libexpat1 2.5.0-1+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.11 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.38.1-5+deb12u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.11 | python3.11 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.11 | python3.11-minimal 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.38.1-5+deb12u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-31879 | LOW3.11 | wget 1.21.3-1+b2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1153 | LOW3.01 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1153 | LOW3.01 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1153 | LOW3.01 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | curl 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31790 | LOW3.01 | openssl 3.0.15-1~deb12u1 fixed in 3.0.19-1~deb12u2 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69420 | LOW3.01 | openssl 3.0.15-1~deb12u1 fixed in 3.0.18-1~deb12u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-22796 | LOW3.01 | openssl 3.0.15-1~deb12u1 fixed in 3.0.18-1~deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40909 | LOW3.01 | perl 5.36.0-7+deb12u1 fixed in 5.36.0-7+deb12u3 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40909 | LOW3.01 | perl-base 5.36.0-7+deb12u1 fixed in 5.36.0-7+deb12u3 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40909 | LOW3.01 | perl-modules-5.36 5.36.0-7+deb12u1 fixed in 5.36.0-7+deb12u3 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-1010022 | LOW3 | libc-bin 2.36-9+deb12u9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-1010022 | LOW3 | libc-dev-bin 2.36-9+deb12u9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-1010022 | LOW3 | libc6 2.36-9+deb12u9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-1010022 | LOW3 | libc6-dev 2.36-9+deb12u9 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW3 | libpython3.11-minimal 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW3 | libpython3.11-stdlib 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31789 | LOW3 | libssl3 3.0.15-1~deb12u1 fixed in 3.0.19-1~deb12u2 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23112 | LOW3 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | curl 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2020-35501 | LOW2.89 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68740 | LOW2.89 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | LOW2.86 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-9230 | LOW2.86 | openssl 3.0.15-1~deb12u1 fixed in 3.0.17-1~deb12u3 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2018-20673 | LOW2.8 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-9996 | LOW2.8 | binutils 2.40-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW2.8 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2018-20673 | LOW2.8 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-9996 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW2.8 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2018-20673 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-9996 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% 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.1% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | cpp-12 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | g++-12 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | gcc-12 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | gcc-12-base 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-22365 | LOW2.8 | libpam-modules-bin 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-4641 | LOW2.8 | login 1:4.13+dfsg1-1+b1 fixed in 1:4.13+dfsg1-1+deb12u1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.38.1-5+deb12u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22795 | LOW2.8 | openssl 3.0.15-1~deb12u1 fixed in 3.0.18-1~deb12u2 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-4641 | LOW2.8 | passwd 1:4.13+dfsg1-1+b1 fixed in 1:4.13+dfsg1-1+deb12u1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-13837 | LOW2.8 | python3.11 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-6075 | LOW2.8 | python3.11 3.11.2-6+deb12u5 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+deb12u5 fixed in 3.11.2-6+deb12u7 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-6075 | LOW2.8 | python3.11-minimal 3.11.2-6+deb12u5 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.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.38.1-5+deb12u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | <0.1% 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.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libbinutils 2.40-2 No fix yet | <0.1% 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.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | <0.1% 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.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf0 2.40-2 No fix yet | <0.1% 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.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW2.8 | libncursesw6 6.4-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW2.8 | libperl5.36 5.36.0-7+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4016 | LOW2.8 | libproc2-0 2:4.0.2-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | libpython3.11-minimal 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.11-minimal 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | libpython3.11-minimal 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | libpython3.11-stdlib 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.11-stdlib 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | libpython3.11-stdlib 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | libsqlite3-0 3.40.1-2+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 252.33-1~deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 252.33-1~deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW2.8 | libtinfo6 6.4-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 252.33-1~deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 252.33-1~deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68191 | LOW2.8 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2015-2877 | LOW2.8 | linux-libc-dev 6.1.124-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-54227 | LOW2.8 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-54233 | LOW2.8 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-54322 | LOW2.8 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-50057 | LOW2.8 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-50211 | LOW2.8 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39964 | LOW2.8 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40035 | LOW2.8 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40268 | LOW2.8 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40303 | LOW2.8 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40341 | LOW2.8 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68746 | LOW2.8 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68782 | LOW2.8 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71224 | LOW2.8 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22978 | LOW2.8 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31668 | LOW2.8 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW2.8 | ncurses-base 6.4-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-2379 | LOW2.75 | curl 7.88.1-10+deb12u8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | curl 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | curl 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | curl 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.38.1-5+deb12u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-61984 | LOW2.7 | openssh-client 1:9.2p1-2+deb12u4 fixed in 1:9.2p1-2+deb12u8 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-61985 | LOW2.7 | openssh-client 1:9.2p1-2+deb12u4 fixed in 1:9.2p1-2+deb12u8 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-12084 | LOW2.7 | python3.11 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW2.7 | python3.11 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3446 | LOW2.7 | python3.11 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-12084 | LOW2.7 | python3.11-minimal 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW2.7 | python3.11-minimal 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3446 | LOW2.7 | python3.11-minimal 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.38.1-5+deb12u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW2.63 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1795 | LOW2.63 | libpython3.11-minimal 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1795 | LOW2.63 | libpython3.11-stdlib 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-9232 | LOW2.63 | libssl3 3.0.15-1~deb12u1 fixed in 3.0.17-1~deb12u3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-4516 | LOW2.6 | python3.11 3.11.2-6+deb12u5 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+deb12u5 fixed in 3.11.2-6+deb12u7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46901 | LOW2.58 | subversion 1.14.2-4+b2 fixed in 1.14.2-4+deb12u1 | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils 2.40-2 No fix yet | 0.1% 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.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.1% 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.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% 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-2018-1000021 | LOW2.55 | git 1:2.39.5-0+deb12u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2007-2243 | LOW2.55 | openssh-client 1:9.2p1-2+deb12u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | login 1:4.13+dfsg1-1+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.13+dfsg1-1+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-4039 | LOW2.45 | cpp-12 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-10148 | LOW2.45 | curl 7.88.1-10+deb12u8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | curl 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-4039 | LOW2.45 | g++-12 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-4039 | LOW2.45 | gcc-12 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-4039 | LOW2.45 | gcc-12-base 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | LOW2.45 | python3.11 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.45 | python3.11 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | LOW2.45 | python3.11-minimal 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.45 | python3.11-minimal 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | 0.2% 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.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl 7.88.1-10+deb12u8 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | dirmngr 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | dirmngr 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gnupg 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gnupg 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gnupg-utils 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gnupg-utils 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg-agent 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg-agent 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg-wks-client 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg-wks-client 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg-wks-server 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg-wks-server 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgconf 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgconf 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgsm 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgsm 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgv 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgv 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-10041 | LOW2.4 | libpam-modules-bin 1.5.2-6+deb12u1 No fix yet | <0.1% 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-2024-13176 | LOW2.4 | openssl 3.0.15-1~deb12u1 fixed in 3.0.16-1~deb12u1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68160 | LOW2.4 | openssl 3.0.15-1~deb12u1 fixed in 3.0.18-1~deb12u2 | <0.1% 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-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.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libbinutils 2.40-2 No fix yet | <0.1% 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.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf-nobfd0 2.40-2 No fix yet | <0.1% 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.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf0 2.40-2 No fix yet | <0.1% 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.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | LOW2.29 | python3.11 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0865 | LOW2.29 | python3.11 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW2.29 | python3.11 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11468 | LOW2.29 | python3.11-minimal 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0865 | LOW2.29 | python3.11-minimal 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW2.29 | python3.11-minimal 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils 9.1-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 2.6.1 No fix yet | 1.5% 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.1% Theoretical Threat | Post-Exploit |
| CVE-2007-2768 | LOW2.19 | openssh-client 1:9.2p1-2+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6069 | LOW2.19 | python3.11 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-8291 | LOW2.19 | python3.11 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-6069 | LOW2.19 | python3.11-minimal 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-8291 | LOW2.19 | python3.11-minimal 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW2.16 | login 1:4.13+dfsg1-1+b1 No fix yet | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-56433 | LOW2.16 | passwd 1:4.13+dfsg1-1+b1 No fix yet | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-24515 | LOW2.12 | libexpat1 2.5.0-1+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-11191 | LOW2.12 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68788 | LOW2.12 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27139 | LOW2.12 | stdlib v1.22.12 fixed in 1.25.8, 1.26.1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-0725 | LOW2.04 | curl 7.88.1-10+deb12u8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-69418 | LOW2.04 | openssl 3.0.15-1~deb12u1 fixed in 3.0.18-1~deb12u2 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-32728 | LOW1.94 | openssh-client 1:9.2p1-2+deb12u4 fixed in 1:9.2p1-2+deb12u6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2007-3719 | LOW1.78 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% 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.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils 2.40-2 No fix yet | <0.1% 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.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-common 2.40-2 No fix yet | <0.1% 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.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | dirmngr 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gnupg 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gnupg-utils 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg-agent 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg-wks-client 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg-wks-server 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgconf 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgsm 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgv 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-29383 | LOW1.68 | login 1:4.13+dfsg1-1+b1 fixed in 1:4.13+dfsg1-1+deb12u1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-6141 | LOW1.68 | ncurses-bin 6.4-4 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-29383 | LOW1.68 | passwd 1:4.13+dfsg1-1+b1 fixed in 1:4.13+dfsg1-1+deb12u1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl 5.36.0-7+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-base 5.36.0-7+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-modules-5.36 5.36.0-7+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-4016 | LOW1.68 | procps 2:4.0.2-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.68 | python3.11 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3.11 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4519 | LOW1.68 | python3.11 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.68 | python3.11-minimal 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3.11-minimal 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4519 | LOW1.68 | python3.11-minimal 3.11.2-6+deb12u5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42155 | LOW1.61 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW1.58 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% 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.1% Theoretical Threat | Post-Exploit |
| CVE-2025-9232 | LOW1.58 | openssl 3.0.15-1~deb12u1 fixed in 3.0.17-1~deb12u3 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1795 | LOW1.58 | python3.11 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u6 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-1795 | LOW1.58 | python3.11-minimal 3.11.2-6+deb12u5 fixed in 3.11.2-6+deb12u6 | 0.8% Theoretical Threat | 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.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils 2.40-2 No fix yet | <0.1% 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.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-common 2.40-2 No fix yet | <0.1% 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.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-35388 | LOW1.27 | openssh-client 1:9.2p1-2+deb12u4 fixed in 1:9.2p1-2+deb12u10 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-52005 | NONE0 | git-man 1:2.39.5-0+deb12u2 No fix yet | 0.4% 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.2% Theoretical Threat | Not Applicable |
| CVE-2025-48384 | NONE0 | git-man 1:2.39.5-0+deb12u2 fixed in 1:2.39.5-0+deb12u3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-24975 | NONE0 | git-man 1:2.39.5-0+deb12u2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2025-68973 | NONE0 | gnupg-l10n 2.2.40-1.1 fixed in 2.2.40-1.1+deb12u2 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2018-1000021 | NONE0 | git-man 1:2.39.5-0+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-30258 | NONE0 | gnupg-l10n 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68972 | NONE0 | gnupg-l10n 2.2.40-1.1 No fix yet | <0.1% 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.1% Theoretical Threat | Not Applicable |
| CVE-2022-3219 | NONE0 | gnupg-l10n 2.2.40-1.1 No fix yet | <0.1% 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.1% Theoretical Threat | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.2.15-2+b7 No fix yet | — | Not Applicable |
| CVE-2025-0167 | NONE0 | curl 7.88.1-10+deb12u8 fixed in 7.88.1-10+deb12u11 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-2219 | NONE0 | dpkg 1.21.22 fixed in 1.21.23 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6297 | NONE0 | dpkg 1.21.22 fixed in 1.21.23 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-0167 | NONE0 | libcurl3-gnutls 7.88.1-10+deb12u8 fixed in 7.88.1-10+deb12u11 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-0167 | NONE0 | libcurl4 7.88.1-10+deb12u8 fixed in 7.88.1-10+deb12u11 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42014 | NONE0 | libgnutls30 3.7.9-2+deb12u3 fixed in 3.7.9-2+deb12u7 | — | Not Applicable |
| CVE-2026-48959 | NONE0 | libperl5.36 5.36.0-7+deb12u1 No fix yet | — | Not Applicable |
| CVE-2025-15649 | NONE0 | libperl5.36 5.36.0-7+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | libperl5.36 5.36.0-7+deb12u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48961 | NONE0 | libperl5.36 5.36.0-7+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-7774 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u5 No fix yet | — | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u5 No fix yet | — | Not Applicable |
| CVE-2026-9669 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u5 No fix yet | — | Not Applicable |
| CVE-2026-7774 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u5 No fix yet | — | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u5 No fix yet | — | Not Applicable |
| CVE-2026-9669 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u5 No fix yet | — | Not Applicable |
| CVE-2025-7709 | NONE0 | libsqlite3-0 3.40.1-2+deb12u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-27587 | NONE0 | libssl3 3.0.15-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-34180 | NONE0 | libssl3 3.0.15-1~deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-34182 | NONE0 | libssl3 3.0.15-1~deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-42766 | NONE0 | libssl3 3.0.15-1~deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-42767 | NONE0 | libssl3 3.0.15-1~deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-42770 | NONE0 | libssl3 3.0.15-1~deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-45445 | NONE0 | libssl3 3.0.15-1~deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-45446 | NONE0 | libssl3 3.0.15-1~deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-45447 | NONE0 | libssl3 3.0.15-1~deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-7383 | NONE0 | libssl3 3.0.15-1~deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-9076 | NONE0 | libssl3 3.0.15-1~deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-43011 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23268 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31705 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54125 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-36331 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-27558 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37838 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39985 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39986 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39987 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39988 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39995 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40003 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40008 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40013 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40022 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40032 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40036 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40043 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40055 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40060 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40062 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40068 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40077 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40084 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40087 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40093 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40095 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40097 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40106 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40107 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40112 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40116 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40124 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40126 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40127 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40137 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40156 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40180 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40188 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40193 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40202 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40207 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40223 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40233 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40243 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40245 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40262 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40263 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40266 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40278 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40282 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40285 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40286 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40288 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40289 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40306 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40311 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40313 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40314 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40315 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40317 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40333 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40337 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40354 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40358 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68177 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68190 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68201 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68217 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68220 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68238 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68246 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68249 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68254 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68255 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68256 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68257 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68258 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68263 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68266 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68286 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68289 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68290 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68302 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68303 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68315 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68320 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68322 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68325 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68327 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68328 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68330 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68332 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68335 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68339 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68344 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68364 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68369 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68727 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68728 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68733 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68750 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68759 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68765 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68766 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68767 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68769 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68771 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68772 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68773 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68777 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68781 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68786 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68787 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68796 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68797 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68799 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68804 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68806 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68808 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68809 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71065 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71067 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71069 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71192 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71196 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71197 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71198 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71199 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71304 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-23030 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23033 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23037 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23049 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23056 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23176 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23182 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23245 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23269 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23281 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23364 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23372 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23393 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23406 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23407 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31396 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31405 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31409 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31417 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31432 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31433 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31476 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31477 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31478 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31494 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31563 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31587 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31597 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31598 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31602 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31611 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31612 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31622 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31626 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31627 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31629 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31656 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31657 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31659 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31683 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31695 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31706 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31707 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31711 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31712 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31716 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31761 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31768 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31780 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43075 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43076 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43117 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43184 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43203 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43206 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43207 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43212 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43232 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43236 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43249 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43256 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43258 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43283 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43291 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43324 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43336 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43370 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43373 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43377 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43476 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-43480 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-43490 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-43495 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-43497 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-43499 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-45839 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-45848 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45849 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45850 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-45864 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45865 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45866 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45867 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45869 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45875 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45879 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45881 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45883 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45885 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45890 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45893 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-45902 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45916 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45924 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45930 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-45935 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45936 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-45946 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45954 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45957 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-45958 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45965 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45969 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45978 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45986 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-45993 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46006 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46009 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46019 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46031 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46044 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46058 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46062 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46072 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46075 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46077 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46080 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46091 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46098 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46108 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46109 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46110 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46112 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46122 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46124 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46128 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46129 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46143 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46148 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46156 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46163 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46164 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46177 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46179 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46187 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46197 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46198 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46199 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46200 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46204 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46205 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46206 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46208 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46212 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46218 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46219 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46220 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46225 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46226 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46229 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46230 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46231 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46233 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46236 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46238 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46241 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46245 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46250 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-46254 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46265 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-46267 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-46270 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2023-53851 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46276 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46282 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46285 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46293 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46296 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46301 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46303 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46314 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46319 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46320 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46321 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46322 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46323 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| CVE-2026-46328 | NONE0 | linux-libc-dev 6.1.124-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-46330 | NONE0 | linux-libc-dev 6.1.124-1 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login 1:4.13+dfsg1-1+b1 No fix yet | — | Not Applicable |
| CVE-2025-2361 | NONE0 | mercurial 6.3.2-1 fixed in 6.3.2-1+deb12u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-2361 | NONE0 | mercurial-common 6.3.2-1 fixed in 6.3.2-1+deb12u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-27587 | NONE0 | openssl 3.0.15-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-34180 | NONE0 | openssl 3.0.15-1~deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-34182 | NONE0 | openssl 3.0.15-1~deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-42766 | NONE0 | openssl 3.0.15-1~deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-42767 | NONE0 | openssl 3.0.15-1~deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-42770 | NONE0 | openssl 3.0.15-1~deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-45445 | NONE0 | openssl 3.0.15-1~deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-45446 | NONE0 | openssl 3.0.15-1~deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-45447 | NONE0 | openssl 3.0.15-1~deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-7383 | NONE0 | openssl 3.0.15-1~deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-9076 | NONE0 | openssl 3.0.15-1~deb12u1 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.13+dfsg1-1+b1 No fix yet | — | Not Applicable |
| CVE-2026-48959 | NONE0 | perl 5.36.0-7+deb12u1 No fix yet | — | Not Applicable |
| CVE-2025-15649 | NONE0 | perl 5.36.0-7+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl 5.36.0-7+deb12u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48961 | NONE0 | perl 5.36.0-7+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-48959 | NONE0 | perl-base 5.36.0-7+deb12u1 No fix yet | — | Not Applicable |
| CVE-2025-15649 | NONE0 | perl-base 5.36.0-7+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.36.0-7+deb12u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48961 | NONE0 | perl-base 5.36.0-7+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-48959 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u1 No fix yet | — | Not Applicable |
| CVE-2025-15649 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48961 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-7774 | NONE0 | python3.11 3.11.2-6+deb12u5 No fix yet | — | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.11 3.11.2-6+deb12u5 No fix yet | — | Not Applicable |
| CVE-2026-9669 | NONE0 | python3.11 3.11.2-6+deb12u5 No fix yet | — | Not Applicable |
| CVE-2026-7774 | NONE0 | python3.11-minimal 3.11.2-6+deb12u5 No fix yet | — | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.11-minimal 3.11.2-6+deb12u5 No fix yet | — | Not Applicable |
| CVE-2026-9669 | NONE0 | python3.11-minimal 3.11.2-6+deb12u5 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-39823 | NONE0 | stdlib v1.22.12 fixed in 1.25.10, 1.26.3 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-39825 | NONE0 | stdlib v1.22.12 fixed in 1.25.10, 1.26.3 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-42499 | NONE0 | stdlib v1.22.12 fixed in 1.25.10, 1.26.3 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-42504 | NONE0 | stdlib v1.22.12 fixed in 1.25.11, 1.26.4 | — | Not Applicable |
| CVE-2025-0913 | NONE0 | stdlib v1.22.12 fixed in 1.23.10, 1.24.4 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27145 | NONE0 | stdlib v1.22.12 fixed in 1.25.11, 1.26.4 | — | Not Applicable |
| CVE-2026-42507 | NONE0 | stdlib v1.22.12 fixed in 1.25.11, 1.26.4 | — | Not Applicable |