Last scanned:
This image poses a critical security risk and must not be used in production, especially as an internet-facing service. An attacker could achieve remote code execution, information disclosure, and server-side request forgery through vulnerabilities in the Apache HTTP server (CVE-2024-38476, CVE-2024-38475) and other components. Disabling the HTTP/2 module would fully eliminate one of the critical remote code execution vulnerabilities. Note that CVE-2024-38475 only affects configurations where mod_rewrite is enabled with unsafe rewrite rules; if mod_rewrite is not required, disabling it reduces risk. However, the sheer volume of exposures (over 7000) and the presence of multiple critical flaws make this image unacceptable for any production environment.
This report ran the first 3 stages — get the full report to unlock the rest.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2024-38476 | CRITICAL10 | apache2 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 41.6% High Exploitation Risk | Directly ExposedContext importance: HIGH |
| CVE-2024-38476 | CRITICAL10 | apache2-bin 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 41.6% High Exploitation Risk | Directly ExposedContext importance: HIGH |
| CVE-2024-38476 | CRITICAL10 | apache2-data 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 41.6% High Exploitation Risk | Directly ExposedContext importance: HIGH |
| CVE-2024-38475 | CRITICAL10 | apache2 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 100.0% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2024-38475 | CRITICAL10 | apache2-bin 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 100.0% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2024-38475 | CRITICAL10 | apache2-data 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 100.0% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2026-23918 | CRITICAL10 | apache2 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 45.8% High Exploitation Risk | Directly Exposed |
| CVE-2026-23918 | CRITICAL10 | apache2-bin 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 45.8% High Exploitation Risk | Directly Exposed |
| CVE-2026-23918 | CRITICAL10 | apache2-data 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 45.8% High Exploitation Risk | Directly Exposed |
| CVE-2023-4863 | CRITICAL10 | libwebp-dev 1.2.4-0.2 fixed in 1.2.4-0.2+deb12u1 | 99.7% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2023-4863 | CRITICAL10 | libwebp7 1.2.4-0.2 fixed in 1.2.4-0.2+deb12u1 | 99.7% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2023-4863 | CRITICAL10 | libwebpdemux2 1.2.4-0.2 fixed in 1.2.4-0.2+deb12u1 | 99.7% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2023-4863 | CRITICAL10 | libwebpmux3 1.2.4-0.2 fixed in 1.2.4-0.2+deb12u1 | 99.7% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2023-4911 | CRITICAL10 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u3 | 81.4% Actively Exploited | Directly Exposed |
| CVE-2023-4911 | CRITICAL10 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u3 | 81.4% Actively Exploited | Directly Exposed |
| CVE-2023-4911 | CRITICAL10 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u3 | 81.4% Actively Exploited | Directly Exposed |
| CVE-2023-4911 | CRITICAL10 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u3 | 81.4% Actively Exploited | Directly Exposed |
| CVE-2026-31431 | CRITICAL10 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 96.3% Actively Exploited | Directly Exposed |
| CVE-2026-43284 | CRITICAL10 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-3 | 93.2% Actively Exploited | Directly Exposed |
| CVE-2026-43500 | CRITICAL10 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-3 | 92.8% Actively Exploited | Directly Exposed |
| CVE-2025-6965 | CRITICAL10 | libsqlite3-0 3.40.1-2 fixed in 3.40.1-2+deb12u2 | 73.5% Actively Exploited | Directly Exposed |
| CVE-2025-6965 | CRITICAL10 | libsqlite3-dev 3.40.1-2 fixed in 3.40.1-2+deb12u2 | 73.5% Actively Exploited | Directly Exposed |
| CVE-2024-38474 | CRITICAL9.8 | apache2 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-38474 | CRITICAL9.8 | apache2-bin 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-38474 | CRITICAL9.8 | apache2-data 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-42116 | CRITICAL9.8 | exim4-base 4.96-15+deb12u1 fixed in 4.96-15+deb12u2 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-42117 | CRITICAL9.8 | exim4-base 4.96-15+deb12u1 fixed in 4.96-15+deb12u3 | 5.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-42116 | CRITICAL9.8 | exim4-config 4.96-15+deb12u1 fixed in 4.96-15+deb12u2 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-42117 | CRITICAL9.8 | exim4-config 4.96-15+deb12u1 fixed in 4.96-15+deb12u3 | 5.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-42116 | CRITICAL9.8 | exim4-daemon-light 4.96-15+deb12u1 fixed in 4.96-15+deb12u2 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-42117 | CRITICAL9.8 | exim4-daemon-light 4.96-15+deb12u1 fixed in 4.96-15+deb12u3 | 5.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | CRITICAL9.8 | libc-bin 2.36-9+deb12u1 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | CRITICAL9.8 | libc-dev-bin 2.36-9+deb12u1 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | CRITICAL9.8 | libc6 2.36-9+deb12u1 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | CRITICAL9.8 | libc6-dev 2.36-9+deb12u1 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-45491 | CRITICAL9.8 | libexpat1 2.5.0-1 fixed in 2.5.0-1+deb12u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-45492 | CRITICAL9.8 | libexpat1 2.5.0-1 fixed in 2.5.0-1+deb12u1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42010 | CRITICAL9.8 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42010 | CRITICAL9.8 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33278 | CRITICAL9.8 | libunbound8 1.17.1-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-56171 | CRITICAL9.8 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45853 | CRITICAL9.8 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45853 | CRITICAL9.8 | zlib1g-dev 1:1.2.13.dfsg-1 No fix yet | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-43622 | CRITICAL9.75 | apache2 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 70.6% Actively Exploited | Directly Exposed |
| CVE-2024-27316 | CRITICAL9.75 | apache2 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 91.3% Actively Exploited | Directly Exposed |
| CVE-2023-43622 | CRITICAL9.75 | apache2-bin 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 70.6% Actively Exploited | Directly Exposed |
| CVE-2024-27316 | CRITICAL9.75 | apache2-bin 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 91.3% Actively Exploited | Directly Exposed |
| CVE-2023-43622 | CRITICAL9.75 | apache2-data 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 70.6% Actively Exploited | Directly Exposed |
| CVE-2024-27316 | CRITICAL9.75 | apache2-data 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 91.3% Actively Exploited | Directly Exposed |
| CVE-2023-44487 | CRITICAL9.75 | libnghttp2-14 1.52.0-1 fixed in 1.52.0-1+deb12u1 | 100.0% Actively Exploited | Directly Exposed |
| CVE-2024-6119 | CRITICAL9.75 | libssl-dev 3.0.9-1 fixed in 3.0.14-1~deb12u2 | 66.6% Actively Exploited | Directly Exposed |
| CVE-2024-6119 | CRITICAL9.75 | libssl3 3.0.9-1 fixed in 3.0.14-1~deb12u2 | 66.6% Actively Exploited | Directly Exposed |
| CVE-2023-50387 | CRITICAL9.75 | libunbound8 1.17.1-2 fixed in 1.17.1-2+deb12u2 | 100.0% Actively Exploited | Directly Exposed |
| CVE-2023-50868 | CRITICAL9.75 | libunbound8 1.17.1-2 fixed in 1.17.1-2+deb12u2 | 81.7% Actively Exploited | Directly Exposed |
| CVE-2025-27363 | CRITICAL9.31 | libfreetype-dev 2.12.1+dfsg-5 fixed in 2.12.1+dfsg-5+deb12u4 | 26.0% High Exploitation Risk | Directly Exposed |
| CVE-2025-27363 | CRITICAL9.31 | libfreetype6 2.12.1+dfsg-5 fixed in 2.12.1+dfsg-5+deb12u4 | 26.0% High Exploitation Risk | Directly Exposed |
| CVE-2025-27363 | CRITICAL9.31 | libfreetype6-dev 2.12.1+dfsg-5 fixed in 2.12.1+dfsg-5+deb12u4 | 26.0% High Exploitation Risk | Directly Exposed |
| CVE-2024-26594 | CRITICAL9.23 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 78.4% Actively Exploited | Directly Exposed |
| CVE-2024-37371 | CRITICAL9.1 | libgssapi-krb5-2 1.20.1-2 fixed in 1.20.1-2+deb12u2 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-37371 | CRITICAL9.1 | libk5crypto3 1.20.1-2 fixed in 1.20.1-2+deb12u2 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-37371 | CRITICAL9.1 | libkrb5-3 1.20.1-2 fixed in 1.20.1-2+deb12u2 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-37371 | CRITICAL9.1 | libkrb5support0 1.20.1-2 fixed in 1.20.1-2+deb12u2 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-13221 | CRITICAL9.1 | libperl5.36 5.36.0-7 No fix yet | — | Directly Exposed |
| CVE-2025-49796 | CRITICAL9.1 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u3 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-47685 | CRITICAL9.1 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-52440 | HIGH8.97 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 36.7% High Exploitation Risk | Directly Exposed |
| CVE-2023-52755 | HIGH8.97 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 26.9% High Exploitation Risk | Directly Exposed |
| CVE-2024-1086 | HIGH8.97 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 28.1% High Exploitation Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc-bin 2.36-9+deb12u1 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc-dev-bin 2.36-9+deb12u1 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc6 2.36-9+deb12u1 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc6-dev 2.36-9+deb12u1 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5178 | HIGH8.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 9.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-8805 | HIGH8.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-49975 | HIGH8.62 | apache2 2.4.57-2 fixed in 2.4.67-1~deb12u3 | 11.5% High Exploitation Risk | Directly Exposed |
| CVE-2026-49975 | HIGH8.62 | apache2-bin 2.4.57-2 fixed in 2.4.67-1~deb12u3 | 11.5% High Exploitation Risk | Directly Exposed |
| CVE-2026-49975 | HIGH8.62 | apache2-data 2.4.57-2 fixed in 2.4.67-1~deb12u3 | 11.5% High Exploitation Risk | Directly Exposed |
| CVE-2024-39573 | HIGH8.51 | apache2 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 35.4% High Exploitation Risk | Directly Exposed |
| CVE-2024-39573 | HIGH8.51 | apache2-bin 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 35.4% High Exploitation Risk | Directly Exposed |
| CVE-2024-39573 | HIGH8.51 | apache2-data 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 35.4% High Exploitation Risk | Directly Exposed |
| CVE-2026-42960 | HIGH8.5 | libunbound8 1.17.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-57432 | HIGH8.4 | libperl5.36 5.36.0-7 No fix yet | — | Directly Exposed |
| CVE-2026-40685 | HIGH8.33 | exim4-base 4.96-15+deb12u1 fixed in 4.96-15+deb12u9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-40685 | HIGH8.33 | exim4-config 4.96-15+deb12u1 fixed in 4.96-15+deb12u9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-40685 | HIGH8.33 | exim4-daemon-light 4.96-15+deb12u1 fixed in 4.96-15+deb12u9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8376 | HIGH8.33 | libperl5.36 5.36.0-7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | HIGH8.33 | libssl-dev 3.0.9-1 fixed in 3.0.19-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | HIGH8.33 | libssl3 3.0.9-1 fixed in 3.0.19-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6653 | HIGH8.33 | libxml2 2.9.14+dfsg-1.3~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-25775 | HIGH8.33 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-23112 | HIGH8.33 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-51736 | HIGH8.33 | symfony/process v6.3.2 fixed in 7.1.0, 7.1.7, 5.0.0, 5.4.46, 6.4.0, 5.3.0, 5.4.0, 6.2.0, 6.3.0, 5.1.0, 5.2.0, 6.4.14, 3.0.0, 4.0.0, 6.1.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-32988 | HIGH8.2 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-32988 | HIGH8.2 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2008-4609 | HIGH8.16 | linux-libc-dev 6.1.38-1 No fix yet | 32.1% High Exploitation Risk | Directly Exposed |
| CVE-2026-28780 | HIGH8.1 | apache2 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28780 | HIGH8.1 | apache2-bin 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28780 | HIGH8.1 | apache2-data 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-31484 | HIGH8.1 | libperl5.36 5.36.0-7 fixed in 5.36.0-7+deb12u3 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-31486 | HIGH8.1 | libperl5.36 5.36.0-7 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45447 | HIGH8.1 | libssl-dev 3.0.9-1 fixed in 3.0.20-1~deb12u2 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45447 | HIGH8.1 | libssl3 3.0.9-1 fixed in 3.0.20-1~deb12u2 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2025-15467 | HIGH8 | libssl-dev 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 47.6% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2025-15467 | HIGH8 | libssl3 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 47.6% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2024-2961 | HIGH8 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u6 | 88.3% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2024-2961 | HIGH8 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u6 | 88.3% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2024-2961 | HIGH8 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u6 | 88.3% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2024-2961 | HIGH8 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u6 | 88.3% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2007-0086 | HIGH7.8 | apache2 2.4.57-2 No fix yet | 9.6% Low-Moderate Risk | Directly Exposed |
| CVE-2007-0086 | HIGH7.8 | apache2-bin 2.4.57-2 No fix yet | 9.6% Low-Moderate Risk | Directly Exposed |
| CVE-2007-0086 | HIGH7.8 | apache2-data 2.4.57-2 No fix yet | 9.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6246 | HIGH7.8 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u4 | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6246 | HIGH7.8 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u4 | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6246 | HIGH7.8 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u4 | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6246 | HIGH7.8 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u4 | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2013-7445 | HIGH7.8 | linux-libc-dev 6.1.38-1 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19449 | HIGH7.8 | linux-libc-dev 6.1.38-1 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19814 | HIGH7.8 | linux-libc-dev 6.1.38-1 No fix yet | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26581 | HIGH7.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-36886 | HIGH7.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-36971 | HIGH7.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-53104 | HIGH7.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-37924 | HIGH7.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 9.8% Low-Moderate Risk | Directly Exposed |
| CVE-2025-38352 | HIGH7.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-46300 | HIGH7.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.174-1 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-46333 | HIGH7.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.172-1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19378 | HIGH7.8 | linux-libc-dev 6.1.38-1 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25265 | HIGH7.8 | linux-libc-dev 6.1.38-1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-40687 | HIGH7.73 | exim4-base 4.96-15+deb12u1 fixed in 4.96-15+deb12u9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-40687 | HIGH7.73 | exim4-config 4.96-15+deb12u1 fixed in 4.96-15+deb12u9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-40687 | HIGH7.73 | exim4-daemon-light 4.96-15+deb12u1 fixed in 4.96-15+deb12u9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33845 | HIGH7.73 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-33845 | HIGH7.73 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | HIGH7.73 | libperl5.36 5.36.0-7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-7458 | HIGH7.73 | libsqlite3-0 3.40.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7458 | HIGH7.73 | libsqlite3-dev 3.40.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | HIGH7.73 | libssl-dev 3.0.9-1 fixed in 3.0.20-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | HIGH7.73 | libssl3 3.0.9-1 fixed in 3.0.20-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-49794 | HIGH7.73 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-31122 | HIGH7.5 | apache2 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-38477 | HIGH7.5 | apache2 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-49630 | HIGH7.5 | apache2 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-31122 | HIGH7.5 | apache2-bin 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-38477 | HIGH7.5 | apache2-bin 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-49630 | HIGH7.5 | apache2-bin 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-31122 | HIGH7.5 | apache2-data 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-38477 | HIGH7.5 | apache2-data 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-49630 | HIGH7.5 | apache2-data 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6779 | HIGH7.5 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u4 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-bin 2.36-9+deb12u1 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-bin 2.36-9+deb12u1 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6779 | HIGH7.5 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u4 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-dev-bin 2.36-9+deb12u1 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-dev-bin 2.36-9+deb12u1 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6779 | HIGH7.5 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u4 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6 2.36-9+deb12u1 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6 2.36-9+deb12u1 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6779 | HIGH7.5 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u4 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6-dev 2.36-9+deb12u1 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6-dev 2.36-9+deb12u1 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-52425 | HIGH7.5 | libexpat1 2.5.0-1 fixed in 2.5.0-1+deb12u2 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-45490 | HIGH7.5 | libexpat1 2.5.0-1 fixed in 2.5.0-1+deb12u1 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-8176 | HIGH7.5 | libexpat1 2.5.0-1 fixed in 2.5.0-1+deb12u2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28757 | HIGH7.5 | libexpat1 2.5.0-1 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2018-6829 | HIGH7.5 | libgcrypt20 1.10.1-3 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0553 | HIGH7.5 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0567 | HIGH7.5 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33846 | HIGH7.5 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42009 | HIGH7.5 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0553 | HIGH7.5 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0567 | HIGH7.5 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33846 | HIGH7.5 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42009 | HIGH7.5 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libgssapi-krb5-2 1.20.1-2 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libk5crypto3 1.20.1-2 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5-3 1.20.1-2 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5support0 1.20.1-2 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2953 | HIGH7.5 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2015-3276 | HIGH7.5 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | HIGH7.5 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33416 | HIGH7.5 | libpng-dev 1.6.39-2 fixed in 1.6.39-2+deb12u4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33416 | HIGH7.5 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+deb12u4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5363 | HIGH7.5 | libssl-dev 3.0.9-1 fixed in 3.0.11-1~deb12u2 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28388 | HIGH7.5 | libssl-dev 3.0.9-1 fixed in 3.0.19-1~deb12u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5363 | HIGH7.5 | libssl3 3.0.9-1 fixed in 3.0.11-1~deb12u2 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28388 | HIGH7.5 | libssl3 3.0.9-1 fixed in 3.0.19-1~deb12u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-25062 | HIGH7.5 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u2 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-27113 | HIGH7.5 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-6021 | HIGH7.5 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u3 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-39179 | HIGH7.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-39180 | HIGH7.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-46838 | HIGH7.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6356 | HIGH7.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6535 | HIGH7.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6536 | HIGH7.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-49997 | HIGH7.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-38501 | HIGH7.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19070 | HIGH7.5 | linux-libc-dev 6.1.38-1 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0400 | HIGH7.5 | linux-libc-dev 6.1.38-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45133 | HIGH7.5 | symfony/yaml v6.3.3 fixed in 3.0.0, 4.0.0, 5.4.52, 6.3.0, 6.4.40, 7.2.0, 7.4.0, 5.1.0, 5.2.0, 5.3.0, 7.1.0, 7.3.0, 5.0.0, 5.4.0, 6.1.0, 8.0.12, 6.2.0, 6.4.0, 7.4.12 | — | Directly Exposed |
| CVE-2026-45304 | HIGH7.5 | symfony/yaml v6.3.3 fixed in 3.0.0, 5.0.0, 5.3.0, 5.4.52, 6.4.0, 7.1.0, 7.4.12, 5.1.0, 5.2.0, 5.4.0, 6.1.0, 6.2.0, 7.3.0, 8.0.12, 4.0.0, 6.3.0, 7.2.0, 6.4.40, 7.4.0 | — | Directly Exposed |
| CVE-2026-45305 | HIGH7.5 | symfony/yaml v6.3.3 fixed in 4.0.0, 5.3.0, 6.2.0, 6.3.0, 6.4.0, 3.0.0, 7.3.0, 7.4.0, 5.1.0, 5.2.0, 5.4.52, 7.1.0, 7.2.0, 7.4.12, 5.0.0, 5.4.0, 6.1.0, 6.4.40, 8.0.12 | — | Directly Exposed |
| CVE-2026-43037 | HIGH7.48 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-25744 | HIGH7.48 | linux-libc-dev 6.1.38-1 fixed in 6.1.69-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47659 | HIGH7.48 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-23395 | HIGH7.48 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-0565 | HIGH7.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.69-1 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-7104 | HIGH7.3 | libsqlite3-0 3.40.1-2 fixed in 3.40.1-2+deb12u1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-7104 | HIGH7.3 | libsqlite3-dev 3.40.1-2 fixed in 3.40.1-2+deb12u1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-10263 | HIGH7.14 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58098 | HIGH7.1 | apache2 2.4.57-2 fixed in 2.4.66-1~deb12u1 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2025-58098 | HIGH7.1 | apache2-bin 2.4.57-2 fixed in 2.4.66-1~deb12u1 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2025-58098 | HIGH7.1 | apache2-data 2.4.57-2 fixed in 2.4.66-1~deb12u1 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3867 | HIGH7.1 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-53150 | HIGH7.1 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-53366 | HIGH7 | linux-libc-dev 6.1.38-1 fixed in 6.1.177-1 | — | Directly Exposed |
| CVE-2026-34032 | MEDIUM6.97 | apache2 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34059 | MEDIUM6.97 | apache2 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34032 | MEDIUM6.97 | apache2-bin 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34059 | MEDIUM6.97 | apache2-bin 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34032 | MEDIUM6.97 | apache2-data 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34059 | MEDIUM6.97 | apache2-data 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-32990 | MEDIUM6.97 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42013 | MEDIUM6.97 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM6.97 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-32990 | MEDIUM6.97 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42013 | MEDIUM6.97 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM6.97 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-31788 | MEDIUM6.97 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-39191 | MEDIUM6.97 | linux-libc-dev 6.1.38-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-28182 | MEDIUM6.89 | libnghttp2-14 1.52.0-1 fixed in 1.52.0-1+deb12u2 | 85.0% Actively Exploited | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25646 | MEDIUM6.88 | libpng-dev 1.6.39-2 fixed in 1.6.39-2+deb12u3 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-25646 | MEDIUM6.88 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+deb12u3 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | libssl-dev 3.0.9-1 fixed in 3.0.19-1~deb12u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | libssl3 3.0.9-1 fixed in 3.0.19-1~deb12u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-58087 | MEDIUM6.88 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43112 | MEDIUM6.88 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43114 | MEDIUM6.88 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-52434 | MEDIUM6.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-38709 | MEDIUM6.8 | apache2 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-38709 | MEDIUM6.8 | apache2-bin 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-38709 | MEDIUM6.8 | apache2-data 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-24023 | MEDIUM6.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-43133 | MEDIUM6.71 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-30232 | MEDIUM6.63 | exim4-base 4.96-15+deb12u1 fixed in 4.96-15+deb12u7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-30232 | MEDIUM6.63 | exim4-config 4.96-15+deb12u1 fixed in 4.96-15+deb12u7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-30232 | MEDIUM6.63 | exim4-daemon-light 4.96-15+deb12u1 fixed in 4.96-15+deb12u7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25210 | MEDIUM6.63 | libexpat1 2.5.0-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-47038 | MEDIUM6.63 | libperl5.36 5.36.0-7 fixed in 5.36.0-7+deb12u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-48962 | MEDIUM6.63 | libperl5.36 5.36.0-7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22801 | MEDIUM6.63 | libpng-dev 1.6.39-2 fixed in 1.6.39-2+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22801 | MEDIUM6.63 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49043 | MEDIUM6.63 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11979 | MEDIUM6.63 | libxml2 2.9.14+dfsg-1.3~deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-3847 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-2176 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-34319 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-3611 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-3776 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-3777 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-4004 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-4015 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-40283 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4147 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4206 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4207 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-4208 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-42753 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-4623 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-4921 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-51042 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52436 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52438 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52439 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52441 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-52444 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52445 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52451 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52452 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52457 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52464 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52469 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52475 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52482 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52483 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52491 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52494 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52509 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52510 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52515 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52524 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52530 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52531 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52572 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52594 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52599 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52600 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52603 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52604 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52612 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52614 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52621 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52624 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-52637 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52642 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52664 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52667 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52669 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52679 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52691 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52748 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52751 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52752 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52757 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52764 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52772 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52775 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.66-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52777 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52795 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52796 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52799 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52804 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52805 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52807 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52812 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52816 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52818 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52835 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52836 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52837 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52840 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52846 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52851 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52852 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52854 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52859 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52864 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52867 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52868 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52885 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52916 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52922 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52927 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-53145 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53148 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53179 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53184 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53187 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53192 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53194 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53205 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53215 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53218 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53252 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53257 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53263 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53286 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53305 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53311 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53316 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53322 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53331 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53338 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53363 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53377 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53386 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53395 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53426 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53432 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53446 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-5345 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-53454 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53479 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53485 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53487 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53492 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53495 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53500 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53508 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53510 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53515 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53541 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53543 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53552 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53554 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53556 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53559 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53560 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53570 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53572 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53577 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53596 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53613 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53616 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53619 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53652 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53673 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53676 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54207 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-54285 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-5633 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-5717 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-6111 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6817 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.69-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-0646 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.69-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-0841 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-1085 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-21803 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-22705 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-23307 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-26582 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26588 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26589 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26592 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26598 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26599 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26610 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26622 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26625 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26689 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26704 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26736 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26739 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26742 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26748 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26749 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26753 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26754 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26782 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26793 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26800 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26836 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26856 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26865 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26882 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26883 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26884 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26885 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26895 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26898 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26907 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26913 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26914 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26928 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26933 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26934 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26936 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26944 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26951 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26952 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26955 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26956 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26957 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26958 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26961 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26965 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26981 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26983 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26988 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26989 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26996 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27000 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27008 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27018 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27022 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27024 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27043 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27045 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27065 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27075 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27395 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27396 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27398 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-35789 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35791 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35847 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35855 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35861 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35862 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35863 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35864 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35866 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35867 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35868 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35886 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35887 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35905 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35932 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36012 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36015 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36880 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36898 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36904 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-36906 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36914 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36934 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36940 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36973 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36974 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36978 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36979 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38545 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38552 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38555 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38556 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38568 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38569 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38570 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38577 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38578 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38581 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38583 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38586 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38588 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38610 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38627 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38630 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38667 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39277 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39463 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-39480 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-39494 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-39495 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-39496 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-39502 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-39510 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40899 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40900 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40901 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40902 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40903 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40906 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40913 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40920 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40927 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40935 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40939 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40940 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40954 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40956 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40958 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40974 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40989 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40994 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40996 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41000 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41011 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41028 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41039 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41042 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41045 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41046 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41050 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41051 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41058 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41069 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41070 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41073 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41074 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41087 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41092 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41096 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42086 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42092 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42104 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42105 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42118 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42119 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42120 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42121 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42136 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42138 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42147 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42148 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42159 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42160 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42271 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42280 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42284 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42285 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42301 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42302 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42313 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42314 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43830 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43839 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-43842 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43858 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43873 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43900 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44934 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44940 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44941 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44942 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44949 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44951 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44967 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44974 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-44977 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-44985 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-44986 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44987 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-44998 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-45026 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46673 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46674 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46713 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46725 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46729 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46738 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46740 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46744 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46746 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46759 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46782 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46786 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46798 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46800 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46804 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46811 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46812 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46813 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46814 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46815 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46818 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46821 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46828 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46830 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46836 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46844 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46849 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46852 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46853 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46859 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46871 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47670 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47682 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47691 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47695 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47696 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47697 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47698 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47701 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47718 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47727 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47730 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47742 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47745 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47748 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47750 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47751 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49852 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49853 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49882 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49883 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49884 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49889 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49894 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49895 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49924 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49930 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49936 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49950 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49960 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49966 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49969 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49982 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49983 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49986 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49989 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49991 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49992 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49996 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50007 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50029 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50047 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50051 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50055 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50063 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50067 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50073 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50074 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50088 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50121 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50124 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50125 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50126 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50127 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50131 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50143 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50150 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50151 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50155 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50180 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50186 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50209 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50215 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50217 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50226 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50230 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50235 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50242 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50246 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50257 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50261 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50262 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50264 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-50267 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50269 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50276 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50282 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50283 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53057 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53059 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53061 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53068 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53096 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53103 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53106 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53141 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-53142 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53156 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53165 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53166 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53168 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53170 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53171 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53173 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53179 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53203 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53206 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53208 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53213 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53214 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53218 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53227 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53237 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53239 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56538 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56548 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56551 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56570 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56581 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56582 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56595 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56596 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56598 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56600 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56601 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56602 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56603 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56604 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56605 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56606 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56608 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56609 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56614 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56615 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56616 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56619 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56626 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56628 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56631 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56633 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56640 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56642 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56651 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56658 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56675 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56704 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56708 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56759 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56765 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56766 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56775 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57792 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57798 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57849 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57850 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57887 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57892 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57896 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57900 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57904 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57917 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57951 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57980 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57998 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58002 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58034 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58055 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58069 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58072 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58093 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58240 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21631 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21671 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21680 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21687 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21692 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-21704 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-21715 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21724 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21734 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21735 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21756 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-21772 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21780 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21785 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-21791 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21811 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21812 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21855 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21858 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21863 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21914 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21919 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21927 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21928 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21934 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21945 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21967 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21968 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21969 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21979 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21991 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22020 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22022 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22040 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-22041 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-22056 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22083 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22088 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22126 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23133 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23142 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23158 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37738 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37750 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37752 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37777 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37778 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-37786 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37789 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37796 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37797 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37798 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37803 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37810 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37817 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37819 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37822 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37823 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37839 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37840 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37849 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37854 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37861 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37885 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37890 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37892 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37899 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-37903 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37913 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37914 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37921 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37923 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37926 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37927 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37928 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-37947 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37952 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37957 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37979 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37991 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38000 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38022 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38024 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38052 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38068 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38069 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38077 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38079 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38117 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38118 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38129 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38131 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38146 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38154 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38157 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38180 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38182 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38183 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38198 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38201 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38206 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38211 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38212 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38226 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38227 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38230 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38236 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38239 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38245 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38248 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38250 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38257 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38259 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38280 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38298 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38313 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38323 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38346 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38348 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38350 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38361 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38369 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38375 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38377 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38385 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38389 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38396 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38401 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38403 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38415 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38416 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38422 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38425 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38428 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38437 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38443 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38456 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38459 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38464 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38471 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38476 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38485 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38488 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-38494 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38500 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38512 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38527 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38535 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38538 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38548 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38550 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38552 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38555 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38563 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-38565 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38572 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38574 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38579 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38582 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38584 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38585 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38593 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38595 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38618 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38627 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38653 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38666 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38676 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-38685 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38697 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38699 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38702 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38704 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38707 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38708 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38718 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38722 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38724 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38729 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38734 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39686 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39689 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39691 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39701 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39730 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39738 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39743 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39766 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39776 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39783 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39788 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39790 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39797 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39810 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39823 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39824 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39828 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39835 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39841 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39849 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39859 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39860 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39863 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39864 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39866 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-39870 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39871 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39873 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39877 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39880 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39881 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39911 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39913 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39944 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39945 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39951 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39952 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39955 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39957 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39967 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40149 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40364 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68817 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71068 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71071 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71073 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71075 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71078 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71082 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71086 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71089 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71091 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71123 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71137 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71152 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71162 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71220 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71238 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22980 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23001 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23010 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23025 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23068 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23073 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23074 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23078 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23083 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23089 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23098 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23111 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23156 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23171 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23193 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23208 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23209 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23216 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23221 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23226 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23227 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23231 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-23234 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23262 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23281 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23319 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23343 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23359 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23361 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23378 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23408 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23410 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23411 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23422 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23428 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23447 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23448 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31399 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31402 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31452 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31455 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31485 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31488 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31489 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31493 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31500 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31527 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31532 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31566 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31576 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31578 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31580 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31581 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31583 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31686 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31696 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31702 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31709 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31715 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31720 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31729 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31747 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31748 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31759 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31787 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43015 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43020 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43027 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43049 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43128 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43150 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43196 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43205 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43250 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43328 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43329 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43378 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43426 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43458 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43499 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45839 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45866 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45867 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45879 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45885 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45891 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45902 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45914 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45916 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45920 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45936 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45946 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45984 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45996 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46004 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46047 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46068 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46069 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46075 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46122 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46136 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46163 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46180 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46189 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46219 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46234 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46241 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46243 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.174-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46267 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46285 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46294 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46301 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46323 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52943 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52962 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52969 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52992 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53004 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53129 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53136 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53137 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53143 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53148 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53156 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53157 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53195 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53262 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53272 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53294 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53296 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53359 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.177-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53362 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.177-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40258 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40277 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46274 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-12456 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-11725 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-26934 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3238 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-26242 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-3640 | MEDIUM6.63 | linux-libc-dev 6.1.38-1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-21759 | MEDIUM6.6 | linux-libc-dev 6.1.38-1 No fix yet | 7.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-44631 | MEDIUM6.54 | apache2 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44631 | MEDIUM6.54 | apache2-bin 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44631 | MEDIUM6.54 | apache2-data 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-24928 | MEDIUM6.54 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libbinutils 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4527 | MEDIUM6.5 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u3 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4527 | MEDIUM6.5 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u3 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4527 | MEDIUM6.5 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u3 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4527 | MEDIUM6.5 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u3 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libctf-nobfd0 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libctf0 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libgprofng0 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libgssapi-krb5-2 1.20.1-2 fixed in 1.20.1-2+deb12u1 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libk5crypto3 1.20.1-2 fixed in 1.20.1-2+deb12u1 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libkrb5-3 1.20.1-2 fixed in 1.20.1-2+deb12u1 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libkrb5support0 1.20.1-2 fixed in 1.20.1-2+deb12u1 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6129 | MEDIUM6.5 | libssl-dev 3.0.9-1 fixed in 3.0.13-1~deb12u1 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6129 | MEDIUM6.5 | libssl3 3.0.9-1 fixed in 3.0.13-1~deb12u1 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-40982 | MEDIUM6.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.38-4 | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-1192 | MEDIUM6.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-1193 | MEDIUM6.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-47692 | MEDIUM6.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2004-0230 | MEDIUM6.5 | linux-libc-dev 6.1.38-1 No fix yet | 80.9% Actively Exploited | Directly Exposed |
| CVE-2026-33636 | MEDIUM6.46 | libpng-dev 1.6.39-2 fixed in 1.6.39-2+deb12u4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33636 | MEDIUM6.46 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+deb12u4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-39971 | MEDIUM6.46 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-55753 | MEDIUM6.38 | apache2 2.4.57-2 fixed in 2.4.66-1~deb12u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34355 | MEDIUM6.38 | apache2 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42536 | MEDIUM6.38 | apache2 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-47252 | MEDIUM6.38 | apache2 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-23048 | MEDIUM6.38 | apache2 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-49812 | MEDIUM6.38 | apache2 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-29168 | MEDIUM6.38 | apache2 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33857 | MEDIUM6.38 | apache2 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34356 | MEDIUM6.38 | apache2 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-29169 | MEDIUM6.38 | apache2 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-55753 | MEDIUM6.38 | apache2-bin 2.4.57-2 fixed in 2.4.66-1~deb12u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34355 | MEDIUM6.38 | apache2-bin 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42536 | MEDIUM6.38 | apache2-bin 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-47252 | MEDIUM6.38 | apache2-bin 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-23048 | MEDIUM6.38 | apache2-bin 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-49812 | MEDIUM6.38 | apache2-bin 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-29168 | MEDIUM6.38 | apache2-bin 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33857 | MEDIUM6.38 | apache2-bin 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34356 | MEDIUM6.38 | apache2-bin 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-29169 | MEDIUM6.38 | apache2-bin 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-55753 | MEDIUM6.38 | apache2-data 2.4.57-2 fixed in 2.4.66-1~deb12u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34355 | MEDIUM6.38 | apache2-data 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42536 | MEDIUM6.38 | apache2-data 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-47252 | MEDIUM6.38 | apache2-data 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-23048 | MEDIUM6.38 | apache2-data 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-49812 | MEDIUM6.38 | apache2-data 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-29168 | MEDIUM6.38 | apache2-data 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33857 | MEDIUM6.38 | apache2-data 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34356 | MEDIUM6.38 | apache2-data 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-29169 | MEDIUM6.38 | apache2-data 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40684 | MEDIUM6.38 | exim4-base 4.96-15+deb12u1 fixed in 4.96-15+deb12u9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-40684 | MEDIUM6.38 | exim4-config 4.96-15+deb12u1 fixed in 4.96-15+deb12u9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-40684 | MEDIUM6.38 | exim4-daemon-light 4.96-15+deb12u1 fixed in 4.96-15+deb12u9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45186 | MEDIUM6.38 | libexpat1 2.5.0-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41989 | MEDIUM6.38 | libgcrypt20 1.10.1-3 fixed in 1.10.1-3+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | libgssapi-krb5-2 1.20.1-2 fixed in 1.20.1-2+deb12u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libgssapi-krb5-2 1.20.1-2 fixed in 1.20.1-2+deb12u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libgssapi-krb5-2 1.20.1-2 fixed in 1.20.1-2+deb12u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | libk5crypto3 1.20.1-2 fixed in 1.20.1-2+deb12u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libk5crypto3 1.20.1-2 fixed in 1.20.1-2+deb12u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libk5crypto3 1.20.1-2 fixed in 1.20.1-2+deb12u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | libkrb5-3 1.20.1-2 fixed in 1.20.1-2+deb12u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkrb5-3 1.20.1-2 fixed in 1.20.1-2+deb12u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkrb5-3 1.20.1-2 fixed in 1.20.1-2+deb12u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | libkrb5support0 1.20.1-2 fixed in 1.20.1-2+deb12u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkrb5support0 1.20.1-2 fixed in 1.20.1-2+deb12u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkrb5support0 1.20.1-2 fixed in 1.20.1-2+deb12u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-31115 | MEDIUM6.38 | liblzma5 5.4.1-0.2 fixed in 5.4.1-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-27135 | MEDIUM6.38 | libnghttp2-14 1.52.0-1 fixed in 1.52.0-1+deb12u3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42497 | MEDIUM6.38 | libperl5.36 5.36.0-7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM6.38 | libperl5.36 5.36.0-7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | libssl-dev 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM6.38 | libssl-dev 3.0.9-1 fixed in 3.0.19-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.38 | libssl-dev 3.0.9-1 fixed in 3.0.19-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | libssl3 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM6.38 | libssl3 3.0.9-1 fixed in 3.0.19-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.38 | libssl3 3.0.9-1 fixed in 3.0.19-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-5994 | MEDIUM6.38 | libunbound8 1.17.1-2 fixed in 1.17.1-2+deb12u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40622 | MEDIUM6.38 | libunbound8 1.17.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41292 | MEDIUM6.38 | libunbound8 1.17.1-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42944 | MEDIUM6.38 | libunbound8 1.17.1-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42959 | MEDIUM6.38 | libunbound8 1.17.1-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-32414 | MEDIUM6.38 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-32415 | MEDIUM6.38 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-39176 | MEDIUM6.38 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-39197 | MEDIUM6.38 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-4458 | MEDIUM6.38 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-45871 | MEDIUM6.38 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-52340 | MEDIUM6.38 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-26620 | MEDIUM6.38 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-42225 | MEDIUM6.38 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-50083 | MEDIUM6.38 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-57791 | MEDIUM6.38 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-22998 | MEDIUM6.38 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-43501 | MEDIUM6.38 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46195 | MEDIUM6.38 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-53266 | MEDIUM6.38 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53819 | MEDIUM6.38 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39973 | MEDIUM6.38 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39982 | MEDIUM6.38 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40240 | MEDIUM6.38 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68349 | MEDIUM6.38 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31669 | MEDIUM6.38 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43110 | MEDIUM6.38 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43186 | MEDIUM6.38 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-43190 | MEDIUM6.38 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53071 | MEDIUM6.38 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-40476 | MEDIUM6.38 | webonyx/graphql-php v15.5.3 fixed in 15.31.5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-20588 | MEDIUM6.32 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 12.4% High Exploitation Risk | Directly Exposed |
| CVE-2023-52442 | MEDIUM6.32 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 17.4% High Exploitation Risk | Directly Exposed |
| CVE-2025-21758 | MEDIUM6.32 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 13.0% High Exploitation Risk | Directly Exposed |
| CVE-2025-22037 | MEDIUM6.32 | linux-libc-dev 6.1.38-1 No fix yet | 28.2% High Exploitation Risk | Directly Exposed |
| CVE-2026-3833 | MEDIUM6.29 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM6.29 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3833 | MEDIUM6.29 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM6.29 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | libssl-dev 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | libssl-dev 3.0.9-1 fixed in 3.0.20-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | libssl3 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | libssl3 3.0.9-1 fixed in 3.0.20-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40170 | MEDIUM6.29 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44185 | MEDIUM6.21 | apache2 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44186 | MEDIUM6.21 | apache2 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-48913 | MEDIUM6.21 | apache2 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44185 | MEDIUM6.21 | apache2-bin 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44186 | MEDIUM6.21 | apache2-bin 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-48913 | MEDIUM6.21 | apache2-bin 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44185 | MEDIUM6.21 | apache2-data 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44186 | MEDIUM6.21 | apache2-data 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-48913 | MEDIUM6.21 | apache2-data 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-56406 | MEDIUM6.21 | libperl5.36 5.36.0-7 fixed in 5.36.0-7+deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-42093 | MEDIUM6.21 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31607 | MEDIUM6.21 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43038 | MEDIUM6.21 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-53752 | MEDIUM6.21 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53781 | MEDIUM6.21 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39981 | MEDIUM6.21 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40141 | MEDIUM6.21 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40176 | MEDIUM6.21 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40269 | MEDIUM6.21 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40294 | MEDIUM6.21 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40304 | MEDIUM6.21 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68800 | MEDIUM6.21 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23243 | MEDIUM6.21 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43078 | MEDIUM6.21 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43248 | MEDIUM6.21 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-38473 | MEDIUM6.09 | apache2 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 25.9% High Exploitation Risk | Directly Exposed |
| CVE-2024-38473 | MEDIUM6.09 | apache2-bin 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 25.9% High Exploitation Risk | Directly Exposed |
| CVE-2024-38473 | MEDIUM6.09 | apache2-data 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 25.9% High Exploitation Risk | Directly Exposed |
| CVE-2023-42114 | MEDIUM6.09 | exim4-base 4.96-15+deb12u1 fixed in 4.96-15+deb12u2 | 28.1% High Exploitation Risk | Directly Exposed |
| CVE-2023-42114 | MEDIUM6.09 | exim4-config 4.96-15+deb12u1 fixed in 4.96-15+deb12u2 | 28.1% High Exploitation Risk | Directly Exposed |
| CVE-2023-42114 | MEDIUM6.09 | exim4-daemon-light 4.96-15+deb12u1 fixed in 4.96-15+deb12u2 | 28.1% High Exploitation Risk | Directly Exposed |
| CVE-2026-54369 | MEDIUM6.03 | libacl1 2.3.1-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM6.03 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM6.03 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-64720 | MEDIUM6.03 | libpng-dev 1.6.39-2 fixed in 1.6.39-2+deb12u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-65018 | MEDIUM6.03 | libpng-dev 1.6.39-2 fixed in 1.6.39-2+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66293 | MEDIUM6.03 | libpng-dev 1.6.39-2 fixed in 1.6.39-2+deb12u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22695 | MEDIUM6.03 | libpng-dev 1.6.39-2 fixed in 1.6.39-2+deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-64720 | MEDIUM6.03 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+deb12u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-65018 | MEDIUM6.03 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66293 | MEDIUM6.03 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+deb12u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22695 | MEDIUM6.03 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52501 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52504 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52507 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52519 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52525 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52565 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52588 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52598 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52628 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-52640 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52682 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52766 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52842 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53034 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53222 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53238 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53272 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53321 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53333 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53357 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53420 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53465 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53486 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53600 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53659 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53668 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-6606 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-26593 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26597 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26664 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26665 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26669 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26673 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26763 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26791 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26954 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26982 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27401 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-34777 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35785 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35849 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35871 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35896 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35937 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35939 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35963 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35964 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35965 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35966 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35967 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36032 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36033 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36883 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36915 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36916 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-36931 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36960 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-37078 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38381 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38538 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38560 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38585 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38599 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38621 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38635 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38659 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39467 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39469 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39471 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39487 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39499 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40929 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40978 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41013 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41014 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41059 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41090 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41091 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41935 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42094 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42292 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43877 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44983 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-44999 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46722 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46723 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46724 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46731 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46743 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46747 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46774 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46854 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46865 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47686 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47723 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47757 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49860 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49861 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49900 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50033 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50035 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50115 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50128 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50164 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50193 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50247 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50250 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50268 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50278 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50279 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50301 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-52332 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53082 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53099 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53147 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53155 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56597 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56627 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56650 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56663 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57838 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57906 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57907 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57908 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57910 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57911 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57912 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57925 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57929 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57945 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57982 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58007 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58014 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58054 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21647 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-21719 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21782 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21794 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21905 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21920 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21946 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21950 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21985 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21993 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22038 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22039 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-22079 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22104 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22107 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22121 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23156 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23157 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37739 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37749 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37780 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37785 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37879 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38004 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38027 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38081 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38088 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38103 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38111 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38153 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38159 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38204 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38249 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38286 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38320 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38342 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38395 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38445 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38482 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38483 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38497 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38502 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38529 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38530 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38556 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38616 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38636 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38652 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38670 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38677 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38679 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38680 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38713 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38714 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38715 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38728 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38736 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39682 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39683 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39685 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39687 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39710 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39719 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39735 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39744 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39757 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39760 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39806 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39817 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39839 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39853 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39869 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39883 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39891 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39901 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39943 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40082 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71093 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71112 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71116 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71133 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71136 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22984 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23076 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23099 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23102 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23187 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23204 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23235 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23315 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23318 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23327 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23388 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23397 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31568 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31778 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43040 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43052 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43141 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43241 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43281 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43380 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43386 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43427 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43449 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43450 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43453 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45893 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45943 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45957 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45994 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46022 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46033 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46064 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46130 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46191 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46293 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52968 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53138 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53149 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53179 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53255 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53303 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53309 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-52502 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-25742 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-25743 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36013 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-53174 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53216 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56558 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58013 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21753 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21762 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21887 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40064 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40301 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40322 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40349 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40351 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68168 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68183 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68324 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68347 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68366 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68724 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23455 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31613 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31685 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31786 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43051 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43126 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43414 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46053 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46056 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46120 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46135 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46150 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46209 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46259 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-48502 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-6610 | MEDIUM6.03 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-68973 | MEDIUM5.95 | gpgv 2.2.40-1.1 fixed in 2.2.40-1.1+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u11 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u11 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u11 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u11 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4878 | MEDIUM5.95 | libcap2 1:2.66-4 fixed in 1:2.66-4+deb12u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5222 | MEDIUM5.95 | libicu72 72.1-3 fixed in 72.1-3+deb12u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-3864 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1989 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-35827 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4244 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4622 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-46813 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-51043 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-51780 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.69-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-51781 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.69-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-51782 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.69-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52480 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52503 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52517 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52578 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52586 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52847 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53622 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-6270 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-6531 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.69-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-6546 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-6931 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.69-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-6932 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.66-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26654 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26872 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26939 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26974 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27020 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27397 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36899 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38561 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39503 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41040 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41049 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41057 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42162 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42228 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43882 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43883 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46858 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47747 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49855 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49903 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49981 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50036 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50059 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50061 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50086 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50154 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50234 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50275 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50286 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56664 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56672 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57876 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21702 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-21718 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37776 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37915 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38051 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38102 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38107 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38108 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39702 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39749 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39759 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39826 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40186 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40248 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68287 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71221 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23191 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23454 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31419 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31663 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43050 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43125 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43198 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43494 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43503 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.174-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45852 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45972 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46054 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46099 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46116 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46181 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46227 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52989 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52991 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52993 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53000 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53002 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53006 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53091 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-51779 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.69-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-53762 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53821 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54148 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26852 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57984 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21703 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-21726 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21727 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21739 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21761 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21764 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21867 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22004 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39993 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40096 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40135 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40154 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40158 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40168 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40259 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40271 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-40318 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40328 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68285 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68301 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23050 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23270 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23392 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31408 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31508 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31586 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43023 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43116 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43158 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43226 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43233 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43303 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43304 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43334 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43339 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43341 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43493 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45856 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45859 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45860 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45894 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45942 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45970 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46015 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46043 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46052 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46090 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46119 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46123 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46133 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-46149 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46173 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46174 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.174-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46185 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46251 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46266 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46275 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46306 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46319 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46324 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46330 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52912 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52917 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52918 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52920 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52924 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52933 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52935 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52942 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52945 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52947 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52956 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52957 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52986 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-52998 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53005 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53009 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53011 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53016 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53036 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53049 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53053 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53062 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53072 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53073 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53075 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53078 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53089 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53131 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53132 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53133 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53182 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53185 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53189 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53209 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53212 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53223 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53224 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53228 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-53230 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53239 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53242 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53246 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53253 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53254 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53256 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53264 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53268 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53270 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53275 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53354 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53355 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53357 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53361 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-1247 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-2961 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-45884 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-45885 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23054 | MEDIUM5.95 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-45802 | MEDIUM5.9 | apache2 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45802 | MEDIUM5.9 | apache2-bin 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45802 | MEDIUM5.9 | apache2-data 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libbinutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u3 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u3 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u3 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u3 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libctf-nobfd0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libctf0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-50602 | MEDIUM5.9 | libexpat1 2.5.0-1 fixed in 2.5.0-1+deb12u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt20 1.10.1-3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5981 | MEDIUM5.9 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u1 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5981 | MEDIUM5.9 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u1 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libgprofng0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libgssapi-krb5-2 1.20.1-2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libk5crypto3 1.20.1-2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5-3 1.20.1-2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5support0 1.20.1-2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6237 | MEDIUM5.9 | libssl-dev 3.0.9-1 fixed in 3.0.13-1~deb12u1 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-5535 | MEDIUM5.9 | libssl-dev 3.0.9-1 fixed in 3.0.15-1~deb12u1 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6237 | MEDIUM5.9 | libssl3 3.0.9-1 fixed in 3.0.13-1~deb12u1 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-5535 | MEDIUM5.9 | libssl3 3.0.9-1 fixed in 3.0.15-1~deb12u1 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1-6 4.19.0-2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-1121 | MEDIUM5.9 | linux-libc-dev 6.1.38-1 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3714 | MEDIUM5.9 | linux-libc-dev 6.1.38-1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56132 | MEDIUM5.87 | libexpat1 2.5.0-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM5.87 | libexpat1 2.5.0-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56404 | MEDIUM5.87 | libexpat1 2.5.0-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56405 | MEDIUM5.87 | libexpat1 2.5.0-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM5.87 | libexpat1 2.5.0-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56410 | MEDIUM5.87 | libexpat1 2.5.0-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56411 | MEDIUM5.87 | libexpat1 2.5.0-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-43622 | MEDIUM5.85 | apache2-utils 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 70.6% Actively Exploited | Post-Exploit |
| CVE-2024-27316 | MEDIUM5.85 | apache2-utils 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 91.3% Actively Exploited | Post-Exploit |
| CVE-2023-38039 | MEDIUM5.85 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u3 | 62.2% Actively Exploited | Post-Exploit |
| CVE-2023-38039 | MEDIUM5.85 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u3 | 62.2% Actively Exploited | Post-Exploit |
| CVE-2024-6119 | MEDIUM5.85 | openssl 3.0.9-1 fixed in 3.0.14-1~deb12u2 | 66.6% Actively Exploited | Post-Exploit |
| CVE-2024-53197 | MEDIUM5.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-42516 | MEDIUM5.78 | apache2 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-42516 | MEDIUM5.78 | apache2-bin 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-42516 | MEDIUM5.78 | apache2-data 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 0.7% 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-2026-46125 | MEDIUM5.78 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-24857 | MEDIUM5.78 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-40345 | MEDIUM5.78 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68346 | MEDIUM5.78 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53196 | MEDIUM5.78 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46331 | MEDIUM5.7 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-36694 | MEDIUM5.7 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-21264 | MEDIUM5.7 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4273 | MEDIUM5.7 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-52447 | MEDIUM5.7 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52512 | MEDIUM5.7 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52584 | MEDIUM5.7 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-0193 | MEDIUM5.7 | linux-libc-dev 6.1.38-1 fixed in 6.1.69-1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26586 | MEDIUM5.7 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53095 | MEDIUM5.7 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56678 | MEDIUM5.7 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56693 | MEDIUM5.7 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57795 | MEDIUM5.7 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21714 | MEDIUM5.7 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21731 | MEDIUM5.7 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22035 | MEDIUM5.7 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22097 | MEDIUM5.7 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40257 | MEDIUM5.7 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68237 | MEDIUM5.7 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26828 | MEDIUM5.7 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.61 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.61 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-5197 | MEDIUM5.61 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-53729 | MEDIUM5.61 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54179 | MEDIUM5.61 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54300 | MEDIUM5.61 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-0607 | MEDIUM5.61 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40018 | MEDIUM5.61 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40261 | MEDIUM5.61 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45991 | MEDIUM5.61 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53267 | MEDIUM5.61 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | libssl-dev 3.0.9-1 fixed in 3.0.17-1~deb12u3 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4741 | MEDIUM5.6 | libssl-dev 3.0.9-1 fixed in 3.0.14-1~deb12u1 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | libssl3 3.0.9-1 fixed in 3.0.17-1~deb12u3 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4741 | MEDIUM5.6 | libssl3 3.0.9-1 fixed in 3.0.14-1~deb12u1 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls-dane0 3.7.9-2 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls30 3.7.9-2 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2025-65082 | MEDIUM5.52 | apache2 2.4.57-2 fixed in 2.4.66-1~deb12u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-33523 | MEDIUM5.52 | apache2 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42535 | MEDIUM5.52 | apache2 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43951 | MEDIUM5.52 | apache2 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-65082 | MEDIUM5.52 | apache2-bin 2.4.57-2 fixed in 2.4.66-1~deb12u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-33523 | MEDIUM5.52 | apache2-bin 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42535 | MEDIUM5.52 | apache2-bin 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43951 | MEDIUM5.52 | apache2-bin 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-65082 | MEDIUM5.52 | apache2-data 2.4.57-2 fixed in 2.4.66-1~deb12u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-33523 | MEDIUM5.52 | apache2-data 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42535 | MEDIUM5.52 | apache2-data 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43951 | MEDIUM5.52 | apache2-data 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libbinutils 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.36-9+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-dev-bin 2.36-9+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.36-9+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6-dev 2.36-9+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libctf-nobfd0 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libctf0 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-6395 | MEDIUM5.52 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-6395 | MEDIUM5.52 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libgprofng0 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libgssapi-krb5-2 1.20.1-2 fixed in 1.20.1-2+deb12u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libk5crypto3 1.20.1-2 fixed in 1.20.1-2+deb12u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libkrb5-3 1.20.1-2 fixed in 1.20.1-2+deb12u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libkrb5support0 1.20.1-2 fixed in 1.20.1-2+deb12u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-15649 | MEDIUM5.52 | libperl5.36 5.36.0-7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-39615 | MEDIUM5.52 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-45322 | MEDIUM5.52 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-68284 | MEDIUM5.52 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-28746 | MEDIUM5.52 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-53785 | MEDIUM5.52 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54094 | MEDIUM5.52 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54292 | MEDIUM5.52 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-6240 | MEDIUM5.52 | linux-libc-dev 6.1.38-1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-26808 | MEDIUM5.52 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36968 | MEDIUM5.52 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47693 | MEDIUM5.52 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-47726 | MEDIUM5.52 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-50076 | MEDIUM5.52 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-53135 | MEDIUM5.52 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39969 | MEDIUM5.52 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40273 | MEDIUM5.52 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68354 | MEDIUM5.52 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68362 | MEDIUM5.52 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68380 | MEDIUM5.52 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31588 | MEDIUM5.52 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43239 | MEDIUM5.52 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53176 | MEDIUM5.52 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-0564 | MEDIUM5.52 | linux-libc-dev 6.1.38-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libbinutils 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libbinutils 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libbinutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf-nobfd0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libctf-nobfd0 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libctf-nobfd0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libctf0 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libctf0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libgprofng0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libgprofng0 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libgprofng0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | libssl-dev 3.0.9-1 fixed in 3.0.13-1~deb12u1 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | libssl3 3.0.9-1 fixed in 3.0.13-1~deb12u1 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-34459 | MEDIUM5.5 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u2 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-20593 | MEDIUM5.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.38-2 | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-52832 | MEDIUM5.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2193 | MEDIUM5.5 | linux-libc-dev 6.1.38-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-27028 | MEDIUM5.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-27053 | MEDIUM5.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-27405 | MEDIUM5.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-35955 | MEDIUM5.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-35960 | MEDIUM5.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-38587 | MEDIUM5.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-38612 | MEDIUM5.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-21760 | MEDIUM5.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 9.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-38562 | MEDIUM5.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 7.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-39946 | MEDIUM5.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 8.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26924 | MEDIUM5.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-38573 | MEDIUM5.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-13221 | MEDIUM5.46 | perl 5.36.0-7 No fix yet | — | Post-Exploit |
| CVE-2026-13221 | MEDIUM5.46 | perl-base 5.36.0-7 No fix yet | — | Post-Exploit |
| CVE-2026-13221 | MEDIUM5.46 | perl-modules-5.36 5.36.0-7 No fix yet | — | Post-Exploit |
| CVE-2022-45888 | MEDIUM5.44 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-39198 | MEDIUM5.44 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-52886 | MEDIUM5.44 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-54156 | MEDIUM5.44 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54164 | MEDIUM5.44 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-21823 | MEDIUM5.44 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36016 | MEDIUM5.44 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57979 | MEDIUM5.44 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21700 | MEDIUM5.44 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21999 | MEDIUM5.44 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39978 | MEDIUM5.44 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40074 | MEDIUM5.44 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40309 | MEDIUM5.44 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40321 | MEDIUM5.44 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68371 | MEDIUM5.44 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23178 | MEDIUM5.44 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23383 | MEDIUM5.44 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23450 | MEDIUM5.44 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-23456 | MEDIUM5.44 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31502 | MEDIUM5.44 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31516 | MEDIUM5.44 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52910 | MEDIUM5.44 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53033 | MEDIUM5.44 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53074 | MEDIUM5.44 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53090 | MEDIUM5.44 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-44032 | MEDIUM5.44 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-44033 | MEDIUM5.44 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-44034 | MEDIUM5.44 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54370 | MEDIUM5.35 | libacl1 2.3.1-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | MEDIUM5.35 | libattr1 1:2.5.1-4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-3397 | MEDIUM5.35 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52644 | MEDIUM5.35 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54072 | MEDIUM5.35 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-24861 | MEDIUM5.35 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26830 | MEDIUM5.35 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27030 | MEDIUM5.35 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38544 | MEDIUM5.35 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41012 | MEDIUM5.35 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42161 | MEDIUM5.35 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57893 | MEDIUM5.35 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40307 | MEDIUM5.35 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68282 | MEDIUM5.35 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31504 | MEDIUM5.35 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53059 | MEDIUM5.35 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-40918 | MEDIUM5.35 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40725 | MEDIUM5.3 | apache2 2.4.57-2 fixed in 2.4.62-1~deb12u1 | 4.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-53020 | MEDIUM5.3 | apache2 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-40725 | MEDIUM5.3 | apache2-bin 2.4.57-2 fixed in 2.4.62-1~deb12u1 | 4.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-53020 | MEDIUM5.3 | apache2-bin 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-40725 | MEDIUM5.3 | apache2-data 2.4.57-2 fixed in 2.4.62-1~deb12u1 | 4.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-53020 | MEDIUM5.3 | apache2-data 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-51766 | MEDIUM5.3 | exim4-base 4.96-15+deb12u1 fixed in 4.96-15+deb12u4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-51766 | MEDIUM5.3 | exim4-config 4.96-15+deb12u1 fixed in 4.96-15+deb12u4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-51766 | MEDIUM5.3 | exim4-daemon-light 4.96-15+deb12u1 fixed in 4.96-15+deb12u4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6780 | MEDIUM5.3 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u4 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-bin 2.36-9+deb12u1 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-bin 2.36-9+deb12u1 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6780 | MEDIUM5.3 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u4 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-dev-bin 2.36-9+deb12u1 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-dev-bin 2.36-9+deb12u1 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6780 | MEDIUM5.3 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u4 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6 2.36-9+deb12u1 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6 2.36-9+deb12u1 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6780 | MEDIUM5.3 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u4 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6-dev 2.36-9+deb12u1 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6-dev 2.36-9+deb12u1 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-59375 | MEDIUM5.3 | libexpat1 2.5.0-1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-12243 | MEDIUM5.3 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u4 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-32989 | MEDIUM5.3 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-12243 | MEDIUM5.3 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u4 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-32989 | MEDIUM5.3 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u5 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3446 | MEDIUM5.3 | libssl-dev 3.0.9-1 fixed in 3.0.10-1~deb12u1 | 5.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3817 | MEDIUM5.3 | libssl-dev 3.0.9-1 fixed in 3.0.10-1~deb12u1 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5678 | MEDIUM5.3 | libssl-dev 3.0.9-1 fixed in 3.0.13-1~deb12u1 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4603 | MEDIUM5.3 | libssl-dev 3.0.9-1 fixed in 3.0.14-1~deb12u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3446 | MEDIUM5.3 | libssl3 3.0.9-1 fixed in 3.0.10-1~deb12u1 | 5.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3817 | MEDIUM5.3 | libssl3 3.0.9-1 fixed in 3.0.10-1~deb12u1 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5678 | MEDIUM5.3 | libssl3 3.0.9-1 fixed in 3.0.13-1~deb12u1 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4603 | MEDIUM5.3 | libssl3 3.0.9-1 fixed in 3.0.14-1~deb12u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-12133 | MEDIUM5.3 | libtasn1-6 4.19.0-2 fixed in 4.19.0-2+deb12u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | libp11-kit0 0.24.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-28162 | MEDIUM5.27 | libpng-dev 1.6.39-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-28162 | MEDIUM5.27 | libpng16-16 1.6.39-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1757 | MEDIUM5.27 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54081 | MEDIUM5.27 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54169 | MEDIUM5.27 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50251 | MEDIUM5.27 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-21722 | MEDIUM5.27 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40048 | MEDIUM5.27 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40146 | MEDIUM5.27 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68757 | MEDIUM5.27 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71066 | MEDIUM5.27 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23253 | MEDIUM5.27 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid1 2.38.1-5+b1 No fix yet | 0.2% 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.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount1 2.38.1-5+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-64506 | MEDIUM5.18 | libpng-dev 1.6.39-2 fixed in 1.6.39-2+deb12u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-64506 | MEDIUM5.18 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+deb12u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libsmartcols1 2.38.1-5+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11411 | MEDIUM5.18 | libunbound8 1.17.1-2 fixed in 1.17.1-2+deb12u4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid1 2.38.1-5+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52497 | MEDIUM5.18 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52810 | MEDIUM5.18 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-53808 | MEDIUM5.18 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53850 | MEDIUM5.18 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54096 | MEDIUM5.18 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42224 | MEDIUM5.18 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57874 | MEDIUM5.18 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40019 | MEDIUM5.18 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-40071 | MEDIUM5.18 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40080 | MEDIUM5.18 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40190 | MEDIUM5.18 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40279 | MEDIUM5.18 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40355 | MEDIUM5.18 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68245 | MEDIUM5.18 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68342 | MEDIUM5.18 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68343 | MEDIUM5.18 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68736 | MEDIUM5.18 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68764 | MEDIUM5.18 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68815 | MEDIUM5.18 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68819 | MEDIUM5.18 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31449 | MEDIUM5.18 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31464 | MEDIUM5.18 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31505 | MEDIUM5.18 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31570 | MEDIUM5.18 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31700 | MEDIUM5.18 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31708 | MEDIUM5.18 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43134 | MEDIUM5.18 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-49975 | MEDIUM5.17 | apache2-utils 2.4.57-2 fixed in 2.4.67-1~deb12u3 | 11.5% High Exploitation Risk | Post-Exploit |
| CVE-2024-2398 | MEDIUM5.17 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u6 | 36.1% High Exploitation Risk | Post-Exploit |
| CVE-2024-2398 | MEDIUM5.17 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u6 | 36.1% High Exploitation Risk | Post-Exploit |
| CVE-2024-39573 | MEDIUM5.11 | apache2-utils 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 35.4% High Exploitation Risk | Post-Exploit |
| CVE-2023-39189 | MEDIUM5.1 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-39192 | MEDIUM5.1 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-39193 | MEDIUM5.1 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26843 | MEDIUM5.1 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56662 | MEDIUM5.1 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31649 | MEDIUM5.1 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-52481 | MEDIUM5.1 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-52511 | MEDIUM5.1 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-52529 | MEDIUM5.1 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26702 | MEDIUM5.1 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26894 | MEDIUM5.1 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-57432 | MEDIUM5.04 | perl 5.36.0-7 No fix yet | — | Post-Exploit |
| CVE-2026-57432 | MEDIUM5.04 | perl-base 5.36.0-7 No fix yet | — | Post-Exploit |
| CVE-2026-57432 | MEDIUM5.04 | perl-modules-5.36 5.36.0-7 No fix yet | — | Post-Exploit |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.36-9+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-dev-bin 2.36-9+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.36-9+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6-dev 2.36-9+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | MEDIUM5.02 | libexpat1 2.5.0-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56412 | MEDIUM5.02 | libexpat1 2.5.0-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libgssapi-krb5-2 1.20.1-2 fixed in 1.20.1-2+deb12u4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssapi-krb5-2 1.20.1-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libk5crypto3 1.20.1-2 fixed in 1.20.1-2+deb12u4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libk5crypto3 1.20.1-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libkrb5-3 1.20.1-2 fixed in 1.20.1-2+deb12u4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-3 1.20.1-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libkrb5support0 1.20.1-2 fixed in 1.20.1-2+deb12u4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5support0 1.20.1-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-40909 | MEDIUM5.02 | libperl5.36 5.36.0-7 fixed in 5.36.0-7+deb12u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.02 | libssl-dev 3.0.9-1 fixed in 3.0.19-1~deb12u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | libssl-dev 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | libssl-dev 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | libssl-dev 3.0.9-1 fixed in 3.0.20-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | libssl-dev 3.0.9-1 fixed in 3.0.20-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.02 | libssl3 3.0.9-1 fixed in 3.0.19-1~deb12u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | libssl3 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | libssl3 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | libssl3 3.0.9-1 fixed in 3.0.20-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | libssl3 3.0.9-1 fixed in 3.0.20-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-44608 | MEDIUM5.02 | libunbound8 1.17.1-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0990 | MEDIUM5.02 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-54048 | MEDIUM5.02 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54302 | MEDIUM5.02 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35870 | MEDIUM5.02 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40083 | MEDIUM5.02 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40242 | MEDIUM5.02 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40324 | MEDIUM5.02 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | MEDIUM5 | openssl 3.0.9-1 fixed in 3.0.19-1~deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | MEDIUM5 | perl 5.36.0-7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | MEDIUM5 | perl-base 5.36.0-7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | MEDIUM5 | perl-modules-5.36 5.36.0-7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2010-4563 | MEDIUM5 | linux-libc-dev 6.1.38-1 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-53706 | MEDIUM4.93 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54045 | MEDIUM4.93 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54107 | MEDIUM4.93 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54136 | MEDIUM4.93 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54141 | MEDIUM4.93 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35910 | MEDIUM4.93 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39994 | MEDIUM4.93 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39998 | MEDIUM4.93 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40111 | MEDIUM4.93 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40118 | MEDIUM4.93 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40167 | MEDIUM4.93 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40194 | MEDIUM4.93 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40201 | MEDIUM4.93 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40214 | MEDIUM4.93 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40272 | MEDIUM4.93 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40323 | MEDIUM4.93 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68742 | MEDIUM4.93 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23239 | MEDIUM4.93 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23240 | MEDIUM4.93 | linux-libc-dev 6.1.38-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-23271 | MEDIUM4.93 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23317 | MEDIUM4.93 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31392 | MEDIUM4.93 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31414 | MEDIUM4.93 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31426 | MEDIUM4.93 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43279 | MEDIUM4.93 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46065 | MEDIUM4.93 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46113 | MEDIUM4.93 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52923 | MEDIUM4.93 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28780 | MEDIUM4.86 | apache2-utils 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | MEDIUM4.86 | openssl 3.0.9-1 fixed in 3.0.20-1~deb12u2 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31484 | MEDIUM4.86 | perl 5.36.0-7 fixed in 5.36.0-7+deb12u3 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | MEDIUM4.86 | perl 5.36.0-7 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31484 | MEDIUM4.86 | perl-base 5.36.0-7 fixed in 5.36.0-7+deb12u3 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | MEDIUM4.86 | perl-base 5.36.0-7 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31484 | MEDIUM4.86 | perl-modules-5.36 5.36.0-7 fixed in 5.36.0-7+deb12u3 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | MEDIUM4.86 | perl-modules-5.36 5.36.0-7 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-1206 | MEDIUM4.84 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-53996 | MEDIUM4.84 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-49569 | MEDIUM4.84 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-53240 | MEDIUM4.84 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-40319 | MEDIUM4.84 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46024 | MEDIUM4.84 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-23039 | MEDIUM4.84 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6965 | MEDIUM4.81 | sqlite3 3.40.1-2 fixed in 3.40.1-2+deb12u2 | 73.5% Actively Exploited | Post-ExploitContext importance: MEDIUM |
| CVE-2024-2511 | MEDIUM4.81 | libssl-dev 3.0.9-1 fixed in 3.0.14-1~deb12u1 | 54.0% Actively Exploited | Directly Exposed |
| CVE-2024-2511 | MEDIUM4.81 | libssl3 3.0.9-1 fixed in 3.0.14-1~deb12u1 | 54.0% Actively Exploited | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libbinutils 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf-nobfd0 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf0 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libgprofng0 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-4155 | MEDIUM4.76 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53828 | MEDIUM4.76 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54251 | MEDIUM4.76 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-28956 | MEDIUM4.76 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-36350 | MEDIUM4.76 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-36357 | MEDIUM4.76 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68801 | MEDIUM4.76 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68816 | MEDIUM4.76 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-20569 | MEDIUM4.7 | linux-libc-dev 6.1.38-1 fixed in 6.1.38-4 | 6.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2201 | MEDIUM4.7 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 8.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-0630 | MEDIUM4.7 | linux-libc-dev 6.1.38-1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2007-0086 | MEDIUM4.68 | apache2-utils 2.4.57-2 No fix yet | 9.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-24072 | MEDIUM4.67 | apache2 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-44119 | MEDIUM4.67 | apache2 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-24072 | MEDIUM4.67 | apache2-bin 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-44119 | MEDIUM4.67 | apache2-bin 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-24072 | MEDIUM4.67 | apache2-data 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-44119 | MEDIUM4.67 | apache2-data 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-49582 | MEDIUM4.67 | libapr1 1.7.2-3 fixed in 1.7.2-3+deb12u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libasan8 12.2.0-14 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libatomic1 12.2.0-14 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libblkid1 2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libcc1-0 12.2.0-14 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1 2.5.0-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32776 | MEDIUM4.67 | libexpat1 2.5.0-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | MEDIUM4.67 | libexpat1 2.5.0-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | MEDIUM4.67 | libexpat1 2.5.0-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52426 | MEDIUM4.67 | libexpat1 2.5.0-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc-12-dev 12.2.0-14 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc-s1 12.2.0-14 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgomp1 12.2.0-14 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26462 | MEDIUM4.67 | libgssapi-krb5-2 1.20.1-2 fixed in 1.20.1-2+deb12u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libitm1 12.2.0-14 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-26462 | MEDIUM4.67 | libk5crypto3 1.20.1-2 fixed in 1.20.1-2+deb12u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26462 | MEDIUM4.67 | libkrb5-3 1.20.1-2 fixed in 1.20.1-2+deb12u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26462 | MEDIUM4.67 | libkrb5support0 1.20.1-2 fixed in 1.20.1-2+deb12u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | liblsan0 12.2.0-14 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount1 2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | MEDIUM4.67 | libpng-dev 1.6.39-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | MEDIUM4.67 | libpng16-16 1.6.39-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libquadmath0 12.2.0-14 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libsmartcols1 2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-29088 | MEDIUM4.67 | libsqlite3-0 3.40.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-29088 | MEDIUM4.67 | libsqlite3-dev 3.40.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM4.67 | libssl-dev 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | libssl-dev 3.0.9-1 fixed in 3.0.20-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM4.67 | libssl3 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | libssl3 3.0.9-1 fixed in 3.0.20-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libstdc++-12-dev 12.2.0-14 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libstdc++6 12.2.0-14 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libtsan2 12.2.0-14 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libubsan1 12.2.0-14 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-9714 | MEDIUM4.67 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u5 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40347 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68192 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68291 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68307 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-36402 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-38096 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-48628 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48772 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49034 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-0160 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-0597 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-23005 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-2430 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31082 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-37454 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-4130 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4132 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-4133 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4194 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-42752 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-42754 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-42755 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-4515 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-4569 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-46343 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-50431 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-5090 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-5158 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52429 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52435 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52443 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52448 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52449 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52454 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52456 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52458 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52462 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52463 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52467 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52470 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52476 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52477 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52479 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52484 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52485 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52486 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52488 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52493 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52498 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52499 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52500 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52506 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52513 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52516 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52518 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52520 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52522 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52523 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52526 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52527 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52528 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52532 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52559 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52560 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52562 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52563 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52564 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52566 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52567 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52570 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52573 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52574 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52577 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52580 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52582 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52583 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52587 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52590 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52591 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52593 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52595 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52601 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52606 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52607 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52610 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52615 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52616 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52619 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52622 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52623 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52625 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52629 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52632 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52635 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52638 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52641 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52643 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52648 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52650 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52652 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52655 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.69-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52656 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52658 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52660 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52661 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52662 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52670 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52671 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52672 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52675 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52676 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52677 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52678 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52680 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52683 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52686 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52687 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52690 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52692 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52693 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52694 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52698 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52699 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-52750 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52753 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52754 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52761 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52762 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52763 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52767 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52770 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52773 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52774 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.66-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52778 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52780 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52781 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.66-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52784 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52787 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52788 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52789 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52791 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52792 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52797 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52803 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52806 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52808 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52809 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52813 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52814 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52815 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52817 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52821 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52825 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52826 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52828 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52831 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52833 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52834 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52841 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52843 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52845 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52849 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52850 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52853 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52856 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52857 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52860 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52863 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52865 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52869 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52871 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52873 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52875 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52876 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52877 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52878 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52879 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52880 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52881 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.69-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52882 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52887 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52888 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52889 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52915 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52918 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52919 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52920 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52923 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52924 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53071 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53146 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53147 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53149 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53150 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53151 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53152 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53165 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53167 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53174 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53175 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53177 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53181 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53185 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53189 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53195 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53196 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53201 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53207 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53208 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53209 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53210 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53220 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53221 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53226 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53228 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53230 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53231 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53243 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53245 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53247 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53248 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53249 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53251 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53255 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53258 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53260 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53261 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53264 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53275 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53280 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53287 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53288 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53291 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53292 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53304 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53309 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53312 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53313 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53314 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53323 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53324 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53325 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53328 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53336 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53339 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53342 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53343 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53352 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53353 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53354 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53356 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53360 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53361 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53362 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53365 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53367 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53369 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53370 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53371 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53379 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53380 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53384 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53385 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53391 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53394 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53397 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53421 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53424 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53425 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53429 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53436 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53438 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53441 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53442 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53444 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53448 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53451 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53456 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53457 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53460 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53461 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53462 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53463 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53472 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53480 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53488 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53491 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53505 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53518 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53519 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53523 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53526 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53529 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53531 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53538 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53539 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53540 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53545 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53546 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53548 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53557 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53558 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53563 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53568 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53574 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53579 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53580 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53583 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53585 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53588 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53593 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53597 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53601 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53602 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53603 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53611 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53617 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53618 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53627 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53631 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53647 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53648 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53649 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53650 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53653 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53654 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53656 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53657 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53658 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53660 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53662 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53663 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53666 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53670 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53672 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53674 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53681 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53687 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53698 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53825 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53829 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53846 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53856 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53989 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53995 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53999 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54013 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54052 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54106 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54137 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54271 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54280 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54299 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-6039 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6622 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.69-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6915 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-7042 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-0340 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-0639 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-0641 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-1151 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-22099 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-23848 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-23849 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-23850 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-23851 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-25739 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-25740 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-25741 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26584 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26590 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26591 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26595 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26596 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26600 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26601 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26602 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26603 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26605 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26606 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26608 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26615 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26618 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26621 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26626 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26629 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26632 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26634 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26635 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26636 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26640 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26641 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26642 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26643 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26644 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26645 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26646 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26651 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26656 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26659 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26660 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26663 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26667 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26668 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26670 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26675 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26677 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26679 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26680 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26681 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26684 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26686 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26687 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26688 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26691 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26695 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26696 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26697 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26700 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26706 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26707 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26714 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26715 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26717 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26718 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26722 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26726 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26727 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26731 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26733 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26735 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26737 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26740 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26741 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26743 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26744 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26750 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26751 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26752 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26756 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26759 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26760 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26761 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26765 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26766 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26767 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26771 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26772 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26773 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26774 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26775 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26776 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26777 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26778 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26779 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26780 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26781 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26783 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26787 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26788 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26789 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26790 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26795 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26798 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26799 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26801 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26802 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26803 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26804 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-26805 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26807 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26809 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26811 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26812 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26813 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26814 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26815 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26816 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26817 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26820 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26822 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26825 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26826 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26829 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26832 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26833 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26834 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26835 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26838 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26839 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26840 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26841 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26844 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26845 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26849 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26851 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26853 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26855 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26860 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26863 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26864 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26866 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26868 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26870 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26876 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26877 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26879 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26880 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-26881 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26889 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26891 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26893 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26896 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26900 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26901 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26902 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26903 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26906 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26916 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26917 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26919 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26920 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26921 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26922 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26925 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26926 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26931 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26935 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26937 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26940 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26943 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26946 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26947 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26948 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26953 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26962 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26963 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26964 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26966 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26969 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26970 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26973 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26976 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26977 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26978 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26980 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26984 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26987 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26993 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26994 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26997 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26999 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27001 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27002 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27003 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27004 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27010 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27011 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27012 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27013 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27014 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27015 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27016 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27017 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27023 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27025 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27032 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27034 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27035 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27037 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27038 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27039 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27041 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27044 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27046 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27047 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27051 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27052 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27054 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27056 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27057 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27059 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27062 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27072 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27074 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27076 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27077 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27078 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27079 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27388 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27389 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27390 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27391 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27399 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27400 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27402 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27403 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27407 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27410 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27412 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27413 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27414 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27416 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27417 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27418 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27431 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27432 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27435 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27436 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-27437 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-31076 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-33619 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-33621 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-33847 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-34027 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35247 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35784 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35790 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35794 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35796 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35799 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35800 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35801 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35803 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35804 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35805 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35806 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35807 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35808 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35811 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35813 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35815 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35817 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35818 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35819 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35821 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-35822 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35823 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-35824 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35825 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35826 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35827 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35828 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35829 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35830 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35833 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35835 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-35837 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35838 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35839 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35840 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35842 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35844 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35851 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35852 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35860 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35872 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35875 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35877 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35879 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35884 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-35885 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35890 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35891 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35892 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35893 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35895 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35897 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35898 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35899 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35900 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35902 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35904 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35907 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35908 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35909 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35912 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35915 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35916 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-35922 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35924 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35925 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35930 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35931 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35933 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35934 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35936 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35938 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35940 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35942 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35943 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35944 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35945 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35946 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35950 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35951 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35952 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35956 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35958 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35959 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35961 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35962 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35969 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35970 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-35971 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35978 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35981 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35982 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35983 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35984 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35986 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35988 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35989 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35990 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35992 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35995 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35996 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35997 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35998 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35999 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36000 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36004 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36005 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36006 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36007 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36008 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36009 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36014 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36017 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36020 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36021 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36023 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36025 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36026 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36029 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36244 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36270 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36286 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36288 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36476 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36478 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36479 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36484 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36489 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36882 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36889 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36890 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36891 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36893 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36897 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36900 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36901 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36902 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36903 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36905 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36908 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36909 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36911 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36917 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36918 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36919 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36920 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36922 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36924 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36926 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36929 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36930 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36933 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36937 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36938 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36939 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36941 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36945 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36946 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36947 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-36951 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36953 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36954 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36957 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36959 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36962 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36964 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36965 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36967 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36969 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36972 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-36975 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36977 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-37021 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-37356 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38390 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38543 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38546 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38547 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38549 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38553 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38554 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38557 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38558 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38564 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38565 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-38567 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38571 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38575 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38579 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38582 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-38589 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38590 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38591 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38594 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38597 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38598 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38600 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38602 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38603 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38607 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38608 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38611 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38615 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38618 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-38619 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38620 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38622 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38623 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-38624 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38625 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38632 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38633 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38634 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38636 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38637 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38661 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38780 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39282 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39292 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39298 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39301 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39371 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39466 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39468 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39472 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39474 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39475 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39476 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39481 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39482 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39484 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39488 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39489 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39490 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39493 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39497 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-39505 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-39506 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-39507 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-39509 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40904 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40908 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40910 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40911 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40912 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40914 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40915 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40916 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40919 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40921 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40924 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40931 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40932 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40934 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40937 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40938 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40941 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40942 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40945 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40947 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40948 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40957 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40959 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40960 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40961 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40963 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40965 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40966 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40967 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40968 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40969 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40970 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40971 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40972 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40973 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40975 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40976 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40977 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40980 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40981 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40983 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40984 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40987 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40988 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40990 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40993 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40995 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40998 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40999 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41001 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41002 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41004 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41006 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41008 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41009 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41015 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41016 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41017 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41019 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41022 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41023 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41030 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41031 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41034 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41035 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41036 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41038 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41041 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41044 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41047 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41048 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41055 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41056 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41060 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41062 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41063 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41064 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41065 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41066 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41068 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41072 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41075 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41076 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41077 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41078 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41079 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41080 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41081 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41082 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41088 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41089 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41093 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41095 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41097 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41098 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42063 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42068 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42069 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42070 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42073 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42076 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42077 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42079 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42080 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42082 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42084 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42085 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42087 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42089 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42090 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42095 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42096 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42097 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42098 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42101 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42103 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42106 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42109 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42110 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42115 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42122 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42124 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42126 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42127 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42128 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42129 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42137 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42139 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42140 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42142 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42145 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42153 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42223 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42232 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42236 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42237 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42238 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42239 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42240 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42241 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42243 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42244 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42245 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42246 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42247 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42250 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42252 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42258 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42259 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42265 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42267 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42268 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42269 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42270 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42272 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42273 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42274 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42276 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42277 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42279 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42281 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42283 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42286 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42288 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42289 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42290 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42291 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42295 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42296 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42297 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42299 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42304 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42305 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42306 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42307 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42309 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42310 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42311 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42312 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42315 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42316 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42317 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42318 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42319 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42320 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42321 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42322 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43098 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43817 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43818 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43819 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43823 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43824 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43828 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43829 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43831 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43832 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43833 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43834 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43835 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-43837 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43840 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43846 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43849 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43850 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43851 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43853 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43854 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43855 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43856 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-43859 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43860 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43861 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43863 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43867 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43868 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43869 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43870 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43871 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43872 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-43875 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43876 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43879 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43880 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43884 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-43889 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43890 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-43893 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-43894 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43897 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43899 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43901 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43902 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43904 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43905 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43907 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43908 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43909 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43912 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43913 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43914 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44931 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44935 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44938 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44939 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44944 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44946 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-44947 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-44948 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44950 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44958 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44960 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44963 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44965 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44966 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44968 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44969 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44970 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44971 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44982 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44988 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44989 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44990 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44991 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44995 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45000 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45001 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45002 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45006 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-45007 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45008 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45009 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45010 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45011 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45015 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45016 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45018 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45019 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45021 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45022 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45025 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45028 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45029 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45828 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46675 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46676 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46677 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46678 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46681 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46685 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46686 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46689 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46694 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46698 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46702 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46707 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46714 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46715 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46716 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46717 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46719 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46720 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46721 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46726 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46727 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46728 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46730 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46732 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46733 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46735 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46737 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46739 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46742 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46745 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46750 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46751 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46752 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46753 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46754 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46755 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46760 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46761 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46763 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46765 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46770 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46771 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46772 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46773 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46775 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46776 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46777 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46780 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46781 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46783 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46784 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46791 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46795 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46802 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46805 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46806 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46807 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46808 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46809 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46810 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46816 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46817 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46819 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46822 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46826 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46829 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46832 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46834 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46835 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46840 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46841 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46846 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46848 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46855 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46857 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46860 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46896 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47141 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47143 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47408 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47658 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47661 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47662 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47663 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47664 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47665 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47666 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47667 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47669 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47671 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47673 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47674 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47678 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47683 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47684 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47690 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47699 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47703 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47704 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47705 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47706 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47707 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47709 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47710 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47712 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47713 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47720 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47728 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47731 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47734 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47735 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47736 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47737 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47739 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47740 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47743 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47749 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47752 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47753 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47754 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47756 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47794 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47809 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-48881 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49568 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49571 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49850 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49851 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49856 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49858 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49863 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49867 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49868 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49870 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49871 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49875 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49877 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49878 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49879 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49881 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49886 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49890 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49891 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49892 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49893 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49896 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49897 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49898 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49899 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49901 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49902 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49905 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49906 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49907 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49908 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49909 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49910 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49911 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49912 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49913 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49914 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49915 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49916 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49917 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49918 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49919 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49920 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49921 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49922 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49923 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49925 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49926 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49927 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49929 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49933 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49935 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49937 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49938 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49939 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49940 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49944 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49945 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49946 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49948 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49949 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49951 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49952 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49954 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49955 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49957 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49958 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49959 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49961 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49962 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49963 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49965 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49968 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49970 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49973 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49974 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49975 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49977 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49978 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49985 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49988 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49994 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50000 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50001 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50002 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50003 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50008 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50009 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50012 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50013 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50015 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50017 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50019 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50022 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50024 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50026 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50028 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50031 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50038 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50039 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50040 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50041 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50045 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50046 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50048 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50049 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50056 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50058 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50060 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50062 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50069 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50072 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50077 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50078 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50085 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50087 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50093 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50095 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50096 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50098 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50099 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50101 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50103 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50108 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50110 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50111 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50116 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50117 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50133 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50134 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50136 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50138 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50141 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50142 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50145 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50146 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50147 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50148 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50153 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50156 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50160 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50162 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50163 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50166 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50167 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50168 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50171 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50176 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50179 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50182 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50184 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50185 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50187 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50188 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50189 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50194 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50195 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50196 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50198 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50199 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50200 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50201 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50202 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50205 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50208 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50210 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50218 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50229 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50232 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50233 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50236 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50237 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50243 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50244 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50245 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50248 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50249 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50252 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50255 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50256 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50258 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50259 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50265 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50271 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50272 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50273 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50284 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50285 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50287 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50289 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50290 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50292 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50295 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50296 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50298 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50299 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50302 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-50304 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-52559 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-52560 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53042 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53043 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53051 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53055 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53056 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53058 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53060 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53063 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53066 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53070 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53072 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53079 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53081 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53085 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53089 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53090 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53091 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53093 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53094 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53097 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53101 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53105 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53110 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53112 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53113 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53114 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53119 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53120 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53121 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53122 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53123 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53125 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53127 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53128 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53129 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53130 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53131 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53134 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53138 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53140 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53144 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53145 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53146 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53148 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53151 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53154 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53157 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53158 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53161 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53164 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53172 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53175 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53180 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53181 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53183 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53184 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53187 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53190 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53194 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53195 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53196 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53198 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53207 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53209 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53210 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53215 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53217 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53219 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53220 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53221 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53224 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53226 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53229 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53230 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53231 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53233 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53234 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53241 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53680 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53685 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53687 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53690 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-54031 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-54683 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-55881 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-55916 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56369 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56531 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56532 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56533 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56539 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56544 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56546 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56549 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56557 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56562 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56565 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56566 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56567 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56569 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56572 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56574 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56575 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56578 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56579 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56583 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56584 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56585 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56586 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56587 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56588 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56589 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56590 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56591 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56592 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56593 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56594 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56599 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56610 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56611 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56622 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56623 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56625 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56629 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56630 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56634 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56636 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56641 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56643 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56644 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56645 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56647 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56648 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56657 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56659 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56660 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56661 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56665 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56670 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56677 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56679 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56681 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56683 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56687 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56688 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56690 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56691 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56692 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56694 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56698 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56700 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56701 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56703 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56705 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56707 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56709 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56712 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56715 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56716 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56717 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56718 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56719 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56720 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56722 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56723 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56724 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56725 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56726 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56727 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56728 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56739 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56742 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56745 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56746 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56747 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56748 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56751 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56754 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56755 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56756 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56758 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56763 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56767 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56769 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56770 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56774 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56776 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56777 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56778 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56779 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56780 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56783 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56785 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56787 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57802 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57804 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57807 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57809 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57834 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57841 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57872 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57882 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57883 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57884 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57888 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57889 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57890 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57895 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57897 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57901 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57902 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57903 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57916 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57922 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57924 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57930 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57931 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57938 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57939 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57940 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57946 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57947 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57948 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57949 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57973 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57975 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57976 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57977 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57978 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57981 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57986 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57993 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57996 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57997 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57999 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58001 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58005 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58006 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58009 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58010 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58011 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58012 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58016 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58017 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58020 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58051 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58052 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58053 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58056 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58058 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58061 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58063 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58068 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58071 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58076 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58079 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58080 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58083 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58085 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58086 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58089 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58090 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58094 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58095 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58096 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58097 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58098 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58100 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58237 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58239 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58241 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21629 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21634 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21635 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21636 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21637 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21638 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21639 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21640 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21645 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21646 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21648 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21649 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21653 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21656 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21658 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21660 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21662 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21664 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21665 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21666 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21667 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21668 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21669 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21673 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21675 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21676 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21678 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21681 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21682 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21683 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21684 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21689 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21690 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21693 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21694 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21696 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21697 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21699 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21705 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21706 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21707 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21708 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21711 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21712 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21716 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21721 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21723 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21725 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21728 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21729 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21736 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21738 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21744 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21745 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21748 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21749 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21750 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21763 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21765 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21766 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21767 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21768 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21775 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21776 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21779 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21781 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21787 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21790 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21792 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21795 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21796 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21799 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21801 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21802 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21804 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21806 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21814 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21816 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21819 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21820 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21821 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21823 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21826 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21829 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21830 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21831 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21832 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21835 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21836 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21838 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21839 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21844 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21846 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21848 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21853 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21859 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21861 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21862 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21864 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21865 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21866 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21870 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21871 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21872 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21875 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21877 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21878 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21881 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21885 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21888 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21891 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21894 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21898 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21899 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21904 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21907 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21909 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21910 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21912 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21913 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21916 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21917 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21918 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21922 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21924 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21925 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21926 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21931 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21935 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21936 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21937 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21941 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21944 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21948 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21949 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21951 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21955 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21956 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21957 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21959 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21960 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21961 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21962 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21963 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21964 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21970 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21971 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21972 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21975 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21976 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21978 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21980 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21981 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21986 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21992 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21994 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21996 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21997 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22005 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22007 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22008 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22010 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22014 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22015 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22018 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22021 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22025 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22026 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22028 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22033 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22042 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22043 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22044 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22045 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22048 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22049 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22053 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22054 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22055 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22057 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22058 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22062 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22063 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22066 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22070 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22071 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22072 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22073 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22075 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22081 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22086 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22089 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22090 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22093 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22095 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22103 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22105 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22109 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22111 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22113 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22119 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22125 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22127 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23129 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23130 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23131 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.177-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23132 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23136 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23138 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23140 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23141 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23143 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23144 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23145 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23146 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23147 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23148 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23150 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23155 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23159 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23160 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23161 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23163 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37740 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37741 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37742 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37747 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37748 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37756 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37757 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37758 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37765 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37766 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37767 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37768 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37769 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37770 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37771 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37772 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37773 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37775 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37781 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37787 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37788 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37790 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37792 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37794 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37800 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37801 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37802 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37805 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37806 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37807 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37808 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37811 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37812 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37815 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37818 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37820 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37824 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37829 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37830 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37833 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37834 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37836 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37841 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37842 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37844 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37850 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37851 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37852 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37853 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37856 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37857 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37858 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37859 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37860 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37862 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37864 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37865 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37867 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37871 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37875 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37880 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37881 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37883 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37889 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37893 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37897 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37901 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37905 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37909 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37911 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37912 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37917 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37925 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37929 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37930 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37931 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37932 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37936 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37937 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37938 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37940 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37945 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37948 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37949 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37951 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37953 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37956 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37958 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37959 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37961 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37962 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37963 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37964 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37967 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37968 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37969 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37970 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37972 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37977 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37980 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37982 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37983 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37989 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37990 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37992 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37994 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.139-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37995 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.139-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37997 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.139-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37998 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.139-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38001 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-38003 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38005 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38006 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38007 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38009 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38014 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38015 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38018 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38020 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38023 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38029 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38031 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38034 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38035 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38037 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38038 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38039 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38040 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38041 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38042 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38043 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38044 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38045 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38057 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38058 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38059 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38061 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38062 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38063 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38064 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38065 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38066 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38067 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-38071 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38072 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38074 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38075 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38080 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38084 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38086 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38090 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38094 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38095 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38096 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38097 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38100 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38105 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38113 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38115 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38119 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38120 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38122 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38124 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38125 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38126 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38127 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38132 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38135 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38136 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38138 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38140 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38142 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38143 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38145 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38147 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38148 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38151 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38152 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38158 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38160 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38161 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38162 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38163 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38165 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38166 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38167 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38170 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38173 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38174 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38177 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.139-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38181 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38184 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38185 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38190 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38191 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-38192 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38193 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38194 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38195 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38197 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38200 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38202 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38203 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38207 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38214 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38215 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38218 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38219 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38222 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38225 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38229 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38231 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38237 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38244 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38246 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38251 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38260 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38261 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38262 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38263 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38264 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38272 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38273 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38275 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38277 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38282 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38283 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38285 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38293 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38300 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38303 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38304 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38305 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38310 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38311 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38312 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38319 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38322 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38324 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38326 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38328 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38331 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38332 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38333 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38334 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38335 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38336 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38337 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38344 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38345 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38347 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38354 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38359 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38362 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38363 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38364 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38371 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38382 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38384 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38386 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38387 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38391 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38399 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38400 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38404 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38406 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38408 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38409 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38410 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38412 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38418 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38419 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38420 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38424 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38426 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38429 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38430 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38436 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38438 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38439 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38441 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38444 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38449 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38451 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38455 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38457 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38458 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38460 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38465 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38466 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38467 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38468 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38470 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38472 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38473 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38474 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38478 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38480 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38481 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38487 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38491 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38495 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38498 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38499 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38503 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38507 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38510 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38513 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38514 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38516 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38520 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38528 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38531 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38539 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38540 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38542 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38543 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38544 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38546 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38560 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38569 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38575 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38576 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38577 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38578 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38581 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38583 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38587 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38588 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38590 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38591 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38597 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38601 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38602 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38604 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38608 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38609 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38610 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38612 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38614 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38615 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38622 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38623 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38624 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38626 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38630 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38634 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38635 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38637 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-38639 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38643 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38644 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38645 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38650 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38659 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38663 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38664 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38665 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38668 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38671 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38678 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38683 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38684 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38691 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38692 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38693 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38694 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38695 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38696 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38698 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38700 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38701 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38705 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38706 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38709 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38710 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38711 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38712 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38716 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38721 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38723 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38725 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38727 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38732 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38735 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39675 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39676 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39677 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39681 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39684 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39692 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39693 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39694 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39703 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39705 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39706 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39707 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39709 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39714 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39715 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39716 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39718 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39720 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39721 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39724 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39728 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39731 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39732 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39734 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39736 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39737 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39742 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39746 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39747 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39748 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39752 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39756 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39762 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39763 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39764 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39767 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39770 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39772 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39773 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39779 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39782 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39787 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39789 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39794 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39795 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39798 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39800 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39801 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39805 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39808 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39812 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39819 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39827 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39829 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39833 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39838 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39842 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39843 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39844 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39845 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39846 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39847 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39848 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39850 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39851 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39857 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39865 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39876 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39885 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39886 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39889 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39894 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39902 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39907 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39909 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39910 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39914 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39916 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39920 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39923 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39925 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39929 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39931 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39932 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39933 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39934 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39937 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39938 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39940 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39942 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39947 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39949 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39953 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39989 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40005 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40020 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40026 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40027 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40029 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40030 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40040 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-40044 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40051 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40053 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40070 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40075 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40078 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40102 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40104 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40109 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40115 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40140 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40153 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40160 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40164 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40171 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40211 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40231 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40251 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40264 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40280 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40283 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40284 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40292 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40293 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40297 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40300 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-40325 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40339 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40363 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68176 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68185 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68188 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68209 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68211 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68223 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68229 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68231 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68236 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68259 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68261 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68265 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68283 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68304 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68310 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68331 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68337 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68340 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68358 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68365 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68372 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68379 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68725 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68774 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68776 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68803 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68814 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68821 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68823 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71064 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71077 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71079 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71081 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71083 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71084 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71085 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71087 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71088 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71094 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71095 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71096 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71097 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71098 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71102 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71104 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71105 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71108 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71109 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71113 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71114 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71118 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71119 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71120 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71121 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71125 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71126 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71127 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71129 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71130 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71131 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71132 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71138 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71144 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71147 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71150 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71154 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71160 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71161 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71163 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71180 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71182 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71183 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71184 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71185 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71186 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71188 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71189 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71190 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71191 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71200 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71202 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71222 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71227 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71232 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71233 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71235 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71236 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71237 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71265 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71266 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71267 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71268 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71269 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71272 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71273 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71285 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71287 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71288 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71289 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71291 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71292 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71295 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71297 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71304 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71305 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71313 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71315 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22976 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22977 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22979 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22982 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22990 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22991 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-22992 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22994 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22996 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22997 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-22999 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23000 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23003 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-23005 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23006 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23011 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23019 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23020 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23021 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23026 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23031 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23038 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23047 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23058 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23060 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23061 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23063 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23064 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23066 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23069 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23075 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23080 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23084 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23085 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23086 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23087 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23088 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23090 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23091 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23093 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23095 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23096 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23097 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23100 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23103 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23105 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23107 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23108 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23113 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23116 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23119 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23120 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23121 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23124 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23125 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23128 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23133 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23137 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23138 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23139 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23140 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23141 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23142 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23144 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23145 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23146 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23150 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23154 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23157 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23164 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23168 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23170 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23172 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23190 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23198 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23202 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23205 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23206 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23213 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23214 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23220 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23222 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23228 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23229 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23230 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23236 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23237 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23238 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23242 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23247 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23255 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23256 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23257 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23258 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23264 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23265 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23266 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23267 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23272 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23273 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23274 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23276 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23277 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23278 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.177-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23279 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23284 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23286 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23287 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23289 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23290 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23291 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23292 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23293 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23296 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23298 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23300 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23303 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23304 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23306 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23307 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23310 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23312 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23321 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23324 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23330 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23335 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23336 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23339 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23340 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23346 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23351 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23352 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23356 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23357 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23362 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23365 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23367 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23368 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23370 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23371 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23374 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23379 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23381 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23382 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23389 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23391 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23396 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23398 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23399 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23401 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23403 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23404 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23405 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23409 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23414 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23419 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23420 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23426 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23434 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23438 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23439 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23442 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23444 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23446 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23449 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23460 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23462 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23465 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23468 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23472 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23474 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23475 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31391 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31400 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31403 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31407 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31410 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31411 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31412 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31415 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31416 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31418 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31420 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31421 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31422 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31423 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31424 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31425 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31427 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31428 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31434 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31441 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31446 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31447 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31448 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31450 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31451 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31453 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31454 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31458 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31462 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31467 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31469 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31473 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31480 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31483 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31487 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31492 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31495 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31496 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31497 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31498 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31503 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31507 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31509 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31510 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31512 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31515 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31518 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31519 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31520 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31521 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31522 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31524 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31531 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31533 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31537 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31540 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31545 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31546 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31548 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31549 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31550 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31551 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31552 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31555 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31557 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31560 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31565 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31577 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31579 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31585 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31590 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31592 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31594 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31595 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31596 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31599 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31603 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31605 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31606 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31610 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31615 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31616 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31617 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31618 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31619 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31623 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31624 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31625 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31628 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31630 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31634 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31637 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31642 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31648 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31651 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31655 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31658 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31660 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31661 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31662 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31664 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31665 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31667 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31670 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31671 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31672 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31673 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31674 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31675 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31676 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31677 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31678 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31679 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31680 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31681 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31682 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31684 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31687 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31689 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31692 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31698 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31699 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31701 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31704 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31721 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31722 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31723 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31724 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31725 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31726 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31737 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31738 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31749 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31752 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31754 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31755 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31756 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31758 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31762 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31763 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31767 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31770 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31771 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31773 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31777 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31779 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31781 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43009 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43010 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43013 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43014 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43016 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43017 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43018 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43022 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43024 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43025 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43026 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43028 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43032 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43033 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43035 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43036 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43041 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43042 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43043 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43046 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43048 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43054 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43057 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43058 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43060 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43061 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43062 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43064 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43065 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43066 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43068 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43069 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43071 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43072 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43073 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43077 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43079 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43080 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43083 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43085 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43088 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43089 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43091 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43093 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43094 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43098 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43099 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43101 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43103 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43104 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43105 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43107 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43111 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43113 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43115 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43118 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43119 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43123 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43124 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43129 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43130 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43132 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43135 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43136 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43137 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43139 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43140 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43143 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43145 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43147 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43148 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43149 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43152 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43153 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43156 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43157 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43159 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43161 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43162 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43167 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43168 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43170 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43171 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43172 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43173 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43180 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43182 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43183 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43187 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43200 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43202 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43204 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43209 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43213 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43214 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43215 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43216 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43218 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43219 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43221 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43223 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43225 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43227 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43230 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43231 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43234 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43238 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43240 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43242 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43244 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43246 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43251 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43252 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43255 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43257 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43261 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43262 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43264 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43265 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43266 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43268 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43269 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43270 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43271 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43273 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43277 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43278 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43287 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43288 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43289 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43295 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43296 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43299 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43302 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43308 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43309 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43310 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43312 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43313 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43314 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43315 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43316 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43317 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43318 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43327 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43333 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43338 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43340 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43343 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43344 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43350 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43352 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43353 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43355 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43357 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43359 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43360 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43361 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43362 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43363 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43365 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43366 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43381 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43382 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43387 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43405 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43406 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43407 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43409 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43411 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43412 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43413 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43416 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43419 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43421 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43424 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43425 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43428 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43429 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43432 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43436 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43437 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43441 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43443 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43445 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43451 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43452 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43455 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43456 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43457 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43459 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43466 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43468 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43469 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43472 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43473 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43475 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43480 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43483 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43484 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43491 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43492 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43496 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43502 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45834 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45835 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45836 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45838 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45840 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45841 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45842 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45843 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45844 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45846 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45847 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45848 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45849 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45850 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45855 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45857 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45858 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45862 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45864 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45865 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45868 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45869 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45870 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45871 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45872 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45873 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45875 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45877 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45881 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45883 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45886 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45890 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45892 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45897 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45899 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45901 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45904 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45911 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45912 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45915 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45917 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45919 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45923 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45924 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45930 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45934 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45940 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45941 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45944 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45948 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45954 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45960 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45961 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45962 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45963 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45964 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45965 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45968 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45969 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45974 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45978 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45981 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45982 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45983 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45985 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45986 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45987 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45988 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45993 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45997 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45999 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46000 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46002 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46003 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46005 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46009 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46012 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46014 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46018 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46019 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46021 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46023 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46026 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46027 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46028 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46032 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46037 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46038 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46040 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46044 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46046 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46049 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46050 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46051 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46059 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46070 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46071 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46072 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46077 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46078 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46079 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46080 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46082 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46083 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46086 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46088 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46091 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46092 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46098 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46101 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46102 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46103 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46107 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46108 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46109 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46111 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46127 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46128 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46132 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46137 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46143 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46146 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46147 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46148 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46151 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46153 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46156 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46157 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46158 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46160 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46161 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46165 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46167 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46168 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46169 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46170 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46172 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46179 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46184 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46186 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46190 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46193 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46196 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46200 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46214 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46220 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46225 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46226 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46229 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46231 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46233 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46235 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46236 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46245 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46247 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46249 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46252 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.177-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46253 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46254 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46262 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46273 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46276 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46280 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46282 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46291 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46292 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46296 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46302 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46303 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46304 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46307 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46312 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46314 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46320 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46321 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46322 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52909 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52913 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52915 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52916 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52921 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52925 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52926 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52927 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52928 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52929 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52930 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52936 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52937 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52939 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52941 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52944 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52946 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-52948 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52954 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52958 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52961 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52963 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52967 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52970 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52972 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52975 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52977 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52981 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52982 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52984 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52985 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52988 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52990 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52995 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52999 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53001 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53003 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53012 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53015 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53017 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53018 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53021 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53022 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53023 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53027 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53034 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53035 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53037 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53039 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53047 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53050 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53052 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53061 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53069 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53070 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53076 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53077 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53086 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53096 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53108 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53115 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53117 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53118 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53120 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53122 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53128 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53134 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53135 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53139 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53146 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53147 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53150 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53158 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53159 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53163 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53167 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53168 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53177 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53181 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53183 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53184 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53199 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53207 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53208 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53213 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53218 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53219 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53220 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53221 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-53225 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53226 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53227 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53229 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53232 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53236 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53237 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53238 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53245 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53249 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53252 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53258 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53263 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53265 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53269 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53274 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53279 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53285 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53287 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53289 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53291 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53292 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53295 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53297 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53304 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53306 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53313 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53314 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53317 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53320 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53325 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53349 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53358 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2008-2544 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2011-4915 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2011-4916 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2011-4917 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2014-9892 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2014-9900 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2016-10723 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-8660 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-13693 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-13694 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-12928 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12378 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12379 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12380 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-12381 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12382 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-12455 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-47432 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-4543 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-48669 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31081 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31085 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-4134 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52576 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52631 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52653 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52674 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52696 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-52811 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52819 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53704 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53711 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53712 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53728 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53730 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53731 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53743 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53768 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53792 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53793 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53823 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53836 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53842 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53844 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53847 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53852 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53857 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53858 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53863 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54001 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54006 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54014 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54019 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54023 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54030 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-54031 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54032 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54051 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54064 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54066 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54067 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54069 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54088 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54091 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54093 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54095 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54099 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54117 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54121 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54134 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54154 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54170 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54173 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54189 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54224 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54254 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54264 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54281 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54296 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54303 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54313 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54314 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54318 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54324 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54326 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26627 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26633 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26676 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26685 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26927 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26950 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26960 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27073 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27393 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35843 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35853 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-35854 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-35865 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35888 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35947 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35973 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35976 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36896 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-36955 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38576 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-39276 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-54458 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39990 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39997 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40010 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40042 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40049 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40057 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40088 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40092 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40094 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40099 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40100 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40103 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40105 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40125 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40196 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40205 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40219 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40253 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40346 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40360 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68171 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68173 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68194 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68200 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68204 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68206 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68218 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68219 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68227 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68233 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68244 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68288 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68295 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68308 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68321 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68334 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68336 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68345 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68363 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68378 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68732 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68734 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68753 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68758 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68778 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68780 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68783 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68785 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68794 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68795 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68798 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68813 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68818 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68820 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68822 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71194 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31486 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43030 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43194 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43211 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43253 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46178 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46299 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52974 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53048 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53060 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53063 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53064 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53080 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53083 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53088 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53093 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53102 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53106 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53111 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53284 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53327 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.177-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53337 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53339 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53350 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53352 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53353 | MEDIUM4.67 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g-dev 1:1.2.13.dfsg-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7598 | MEDIUM4.64 | libssh2-1 1.10.0-3+b1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | MEDIUM4.64 | openssl 3.0.9-1 fixed in 3.0.20-1~deb12u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl 5.36.0-7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl-base 5.36.0-7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl-modules-5.36 5.36.0-7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-7458 | MEDIUM4.64 | sqlite3 3.40.1-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38428 | MEDIUM4.64 | wget 1.21.3-1+b2 fixed in 1.21.3-1+deb12u1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-43204 | MEDIUM4.59 | apache2 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-66200 | MEDIUM4.59 | apache2 2.4.57-2 fixed in 2.4.66-1~deb12u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-29170 | MEDIUM4.59 | apache2 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-43204 | MEDIUM4.59 | apache2-bin 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-66200 | MEDIUM4.59 | apache2-bin 2.4.57-2 fixed in 2.4.66-1~deb12u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-29170 | MEDIUM4.59 | apache2-bin 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-43204 | MEDIUM4.59 | apache2-data 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-66200 | MEDIUM4.59 | apache2-data 2.4.57-2 fixed in 2.4.66-1~deb12u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-29170 | MEDIUM4.59 | apache2-data 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-38545 | MEDIUM4.58 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u4 | 78.5% Actively Exploited | Post-Exploit |
| CVE-2023-38545 | MEDIUM4.58 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u4 | 78.5% Actively Exploited | Post-Exploit |
| CVE-2023-31122 | MEDIUM4.5 | apache2-utils 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2024-38477 | MEDIUM4.5 | apache2-utils 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-49630 | MEDIUM4.5 | apache2-utils 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-33416 | MEDIUM4.5 | libpng-tools 1.6.39-2 fixed in 1.6.39-2+deb12u4 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2008-1687 | MEDIUM4.5 | m4 1.4.19-3 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2008-1688 | MEDIUM4.5 | m4 1.4.19-3 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5363 | MEDIUM4.5 | openssl 3.0.9-1 fixed in 3.0.11-1~deb12u2 | 3.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28388 | MEDIUM4.5 | openssl 3.0.9-1 fixed in 3.0.19-1~deb12u2 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6951 | MEDIUM4.5 | patch 2.7.6-7 No fix yet | 8.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6952 | MEDIUM4.5 | patch 2.7.6-7 No fix yet | 8.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-33007 | MEDIUM4.5 | apache2 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33007 | MEDIUM4.5 | apache2-bin 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33007 | MEDIUM4.5 | apache2-data 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40686 | MEDIUM4.5 | exim4-base 4.96-15+deb12u1 fixed in 4.96-15+deb12u9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40686 | MEDIUM4.5 | exim4-config 4.96-15+deb12u1 fixed in 4.96-15+deb12u9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40686 | MEDIUM4.5 | exim4-daemon-light 4.96-15+deb12u1 fixed in 4.96-15+deb12u9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libblkid1 2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid1 2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-28834 | MEDIUM4.5 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-14831 | MEDIUM4.5 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM4.5 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-28834 | MEDIUM4.5 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-14831 | MEDIUM4.5 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM4.5 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | liblzma5 5.4.1-0.2 fixed in 5.4.1-1+deb12u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libmount1 2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount1 2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-12087 | MEDIUM4.5 | libperl5.36 5.36.0-7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3713 | MEDIUM4.5 | libpng-dev 1.6.39-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3713 | MEDIUM4.5 | libpng16-16 1.6.39-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libsmartcols1 2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libsmartcols1 2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-2975 | MEDIUM4.5 | libssl-dev 3.0.9-1 fixed in 3.0.10-1~deb12u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | libssl-dev 3.0.9-1 fixed in 3.0.20-1~deb12u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | libssl-dev 3.0.9-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-2975 | MEDIUM4.5 | libssl3 3.0.9-1 fixed in 3.0.10-1~deb12u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | libssl3 3.0.9-1 fixed in 3.0.20-1~deb12u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | libssl3 3.0.9-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-8508 | MEDIUM4.5 | libunbound8 1.17.1-2 fixed in 1.17.1-2+deb12u3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42534 | MEDIUM4.5 | libunbound8 1.17.1-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42923 | MEDIUM4.5 | libunbound8 1.17.1-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-44390 | MEDIUM4.5 | libunbound8 1.17.1-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32792 | MEDIUM4.5 | libunbound8 1.17.1-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libuuid1 2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-53713 | MEDIUM4.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53726 | MEDIUM4.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54092 | MEDIUM4.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-24858 | MEDIUM4.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-24860 | MEDIUM4.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26886 | MEDIUM4.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-35857 | MEDIUM4.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-36881 | MEDIUM4.5 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39968 | MEDIUM4.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39972 | MEDIUM4.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40204 | MEDIUM4.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68367 | MEDIUM4.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71225 | MEDIUM4.5 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23457 | MEDIUM4.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53194 | MEDIUM4.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-54181 | MEDIUM4.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48998 | MEDIUM4.5 | guzzlehttp/psr7 2.5.0 fixed in 2.10.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-7264 | MEDIUM4.48 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u7 | 17.3% High Exploitation Risk | Post-Exploit |
| CVE-2024-7264 | MEDIUM4.48 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u7 | 17.3% High Exploitation Risk | Post-Exploit |
| CVE-2023-53841 | MEDIUM4.42 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39970 | MEDIUM4.42 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40338 | MEDIUM4.42 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40343 | MEDIUM4.42 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-28085 | MEDIUM4.4 | libblkid1 2.38.1-5+b1 fixed in 2.38.1-5+deb12u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28085 | MEDIUM4.4 | libmount1 2.38.1-5+b1 fixed in 2.38.1-5+deb12u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28085 | MEDIUM4.4 | libsmartcols1 2.38.1-5+b1 fixed in 2.38.1-5+deb12u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28085 | MEDIUM4.4 | libuuid1 2.38.1-5+b1 fixed in 2.38.1-5+deb12u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-35845 | MEDIUM4.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-38541 | MEDIUM4.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-52798 | MEDIUM4.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-38605 | MEDIUM4.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-7104 | MEDIUM4.38 | sqlite3 3.40.1-2 fixed in 3.40.1-2+deb12u1 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-53843 | MEDIUM4.33 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40178 | MEDIUM4.33 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71193 | MEDIUM4.33 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23035 | MEDIUM4.33 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2003-1307 | MEDIUM4.3 | apache2 2.4.57-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1580 | MEDIUM4.3 | apache2 2.4.57-2 No fix yet | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1307 | MEDIUM4.3 | apache2-bin 2.4.57-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1580 | MEDIUM4.3 | apache2-bin 2.4.57-2 No fix yet | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1307 | MEDIUM4.3 | apache2-data 2.4.57-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1580 | MEDIUM4.3 | apache2-data 2.4.57-2 No fix yet | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-45346 | MEDIUM4.3 | libsqlite3-0 3.40.1-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-45346 | MEDIUM4.3 | libsqlite3-dev 3.40.1-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6121 | MEDIUM4.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-38475 | MEDIUM4.26 | apache2-utils 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 100.0% Actively Exploited | Post-Exploit |
| CVE-2025-58098 | MEDIUM4.26 | apache2-utils 2.4.57-2 fixed in 2.4.66-1~deb12u1 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-57360 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM4.25 | libbz2-1.0 1.0.8-5+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.36-9+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.36-9+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-dev-bin 2.36-9+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-dev-bin 2.36-9+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.36-9+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.36-9+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6-dev 2.36-9+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6-dev 2.36-9+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-28835 | MEDIUM4.25 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-28835 | MEDIUM4.25 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libgssapi-krb5-2 1.20.1-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libk5crypto3 1.20.1-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5-3 1.20.1-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5support0 1.20.1-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48959 | MEDIUM4.25 | libperl5.36 5.36.0-7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48961 | MEDIUM4.25 | libperl5.36 5.36.0-7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-28164 | MEDIUM4.25 | libpng-dev 1.6.39-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-28164 | MEDIUM4.25 | libpng16-16 1.6.39-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM4.25 | libssl-dev 3.0.9-1 fixed in 3.0.20-1~deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM4.25 | libssl3 3.0.9-1 fixed in 3.0.20-1~deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-52633 | MEDIUM4.25 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40121 | MEDIUM4.25 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23180 | MEDIUM4.25 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-39929 | MEDIUM4.25 | exim4-base 4.96-15+deb12u1 fixed in 4.96-15+deb12u5 | 41.2% High Exploitation Risk | Directly Exposed |
| CVE-2024-39929 | MEDIUM4.25 | exim4-config 4.96-15+deb12u1 fixed in 4.96-15+deb12u5 | 41.2% High Exploitation Risk | Directly Exposed |
| CVE-2024-39929 | MEDIUM4.25 | exim4-daemon-light 4.96-15+deb12u1 fixed in 4.96-15+deb12u5 | 41.2% High Exploitation Risk | Directly Exposed |
| CVE-2026-55200 | MEDIUM4.23 | libssh2-1 1.10.0-3+b1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2020-15719 | MEDIUM4.2 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34032 | MEDIUM4.18 | apache2-utils 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-34059 | MEDIUM4.18 | apache2-utils 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2007-3303 | MEDIUM4.17 | apache2 2.4.57-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2007-3303 | MEDIUM4.17 | apache2-bin 2.4.57-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2007-3303 | MEDIUM4.17 | apache2-data 2.4.57-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-34324 | MEDIUM4.17 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2005-3660 | MEDIUM4.17 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8286 | MEDIUM4.13 | curl 7.88.1-10+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | curl 7.88.1-10+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl4 7.88.1-10+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl4 7.88.1-10+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-25646 | MEDIUM4.13 | libpng-tools 1.6.39-2 fixed in 1.6.39-2+deb12u3 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-28387 | MEDIUM4.13 | openssl 3.0.9-1 fixed in 3.0.19-1~deb12u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-44466 | MEDIUM4.12 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 54.6% Actively Exploited | Post-Exploit |
| CVE-2023-38709 | MEDIUM4.08 | apache2-utils 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 3.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-33006 | MEDIUM4.08 | apache2 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33006 | MEDIUM4.08 | apache2-bin 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33006 | MEDIUM4.08 | apache2-data 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libasan8 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libatomic1 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libcc1-0 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libgcc-12-dev 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libgcc-s1 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libgomp1 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libitm1 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | liblsan0 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libquadmath0 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libstdc++-12-dev 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libstdc++6 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libtsan2 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libubsan1 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-43168 | MEDIUM4.08 | libunbound8 1.17.1-2 fixed in 1.17.1-2+deb12u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-24859 | MEDIUM4.08 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-38476 | MEDIUM4.06 | apache2-utils 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 41.6% High Exploitation Risk | Post-Exploit |
| CVE-2023-42115 | MEDIUM4.06 | exim4-base 4.96-15+deb12u1 fixed in 4.96-15+deb12u2 | 10.0% High Exploitation Risk | Post-Exploit |
| CVE-2023-42115 | MEDIUM4.06 | exim4-config 4.96-15+deb12u1 fixed in 4.96-15+deb12u2 | 10.0% High Exploitation Risk | Post-Exploit |
| CVE-2023-42115 | MEDIUM4.06 | exim4-daemon-light 4.96-15+deb12u1 fixed in 4.96-15+deb12u2 | 10.0% High Exploitation Risk | Post-Exploit |
| CVE-2025-15467 | MEDIUM4.06 | openssl 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 47.6% High Exploitation Risk | Post-Exploit |
| CVE-2025-30258 | MEDIUM4 | gpgv 2.2.40-1.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | MEDIUM4 | gpgv 2.2.40-1.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | MEDIUM4 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount1 2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols1 2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | libssl-dev 3.0.9-1 fixed in 3.0.16-1~deb12u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4 | libssl-dev 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | libssl3 3.0.9-1 fixed in 3.0.16-1~deb12u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4 | libssl3 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-20794 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-2898 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31083 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-42756 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-46862 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52478 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52489 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52505 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52568 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52589 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52602 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52608 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52609 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52639 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52645 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52654 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.69-1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-52749 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.66-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52771 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53204 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53368 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53401 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53447 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53490 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53501 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53520 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53581 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53615 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53697 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53703 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53766 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53777 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53794 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53799 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53815 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53839 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53848 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53860 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53861 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54166 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54201 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-6176 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-22386 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-23196 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-24855 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-24864 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26583 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26585 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26607 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26631 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26671 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26698 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26837 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26859 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26861 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26862 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26869 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26874 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26878 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26897 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26910 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26923 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27009 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27019 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27404 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27408 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27415 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27419 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35809 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35848 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36024 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36028 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36927 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36949 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36952 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-37354 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38580 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38596 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38601 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38613 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38662 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39500 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39508 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40905 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40943 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40953 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41005 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41020 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42102 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42107 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42152 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42253 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42287 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43866 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43892 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44954 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45003 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46679 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46710 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46711 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46734 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46787 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46870 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-47660 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47668 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47679 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49859 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49866 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49998 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50006 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50010 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50082 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50135 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50183 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50192 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53088 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53100 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53124 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53136 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53176 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53178 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56568 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56576 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56637 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56729 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57857 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57913 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57974 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21651 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21655 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21688 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21701 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21732 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21825 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21892 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21938 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21943 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21947 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-22027 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22050 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22060 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22115 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23151 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37920 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37985 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38048 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38078 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38083 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38085 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38104 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38112 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38232 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38234 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38365 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38393 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38448 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38461 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38462 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38477 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38515 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38524 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38561 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-38617 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-38681 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38687 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38717 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39673 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39697 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39713 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39726 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39754 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39813 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39825 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39927 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39961 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39977 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39980 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39996 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40006 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40011 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40016 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40039 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40056 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40085 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40110 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40120 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40134 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40139 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40179 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40187 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40197 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40215 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40220 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40244 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40252 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40254 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40331 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40342 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68214 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68239 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68241 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68296 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68312 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68745 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71074 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71111 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71274 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23004 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23071 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23101 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23110 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23118 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23126 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23167 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23169 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23207 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23212 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23302 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.177-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23348 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23394 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23452 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23463 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31389 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31393 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31466 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31523 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31697 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31728 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31751 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43047 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43053 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43163 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43275 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43342 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43383 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43420 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43430 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43439 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43448 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45905 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45949 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46017 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46159 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46187 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52955 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16230 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16234 | MEDIUM4 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-54026 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54035 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54042 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54185 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54289 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54309 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26915 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68264 | MEDIUM4 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-24795 | MEDIUM4 | apache2 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-24795 | MEDIUM4 | apache2-bin 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-24795 | MEDIUM4 | apache2-data 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-bin 2.36-9+deb12u1 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-dev-bin 2.36-9+deb12u1 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.36-9+deb12u1 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6-dev 2.36-9+deb12u1 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-11082 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-22801 | LOW3.98 | libpng-tools 1.6.39-2 fixed in 1.6.39-2+deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-47038 | LOW3.98 | perl 5.36.0-7 fixed in 5.36.0-7+deb12u1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl 5.36.0-7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-47038 | LOW3.98 | perl-base 5.36.0-7 fixed in 5.36.0-7+deb12u1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl-base 5.36.0-7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-47038 | LOW3.98 | perl-modules-5.36 5.36.0-7 fixed in 5.36.0-7+deb12u1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl-modules-5.36 5.36.0-7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-44631 | LOW3.93 | apache2-utils 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-29167 | LOW3.91 | apache2 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-29167 | LOW3.91 | apache2-bin 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-29167 | LOW3.91 | apache2-data 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2019-15213 | LOW3.91 | linux-libc-dev 6.1.38-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-37453 | LOW3.91 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4010 | LOW3.91 | linux-libc-dev 6.1.38-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-49934 | LOW3.91 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2012-4542 | LOW3.91 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | LOW3.9 | binutils 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20712 | LOW3.9 | binutils-common 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20712 | LOW3.9 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-46218 | LOW3.9 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u5 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-9681 | LOW3.9 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u9 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-11856 | LOW3.9 | curl 7.88.1-10+deb12u1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2023-46218 | LOW3.9 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u5 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-9681 | LOW3.9 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u9 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-11856 | LOW3.9 | libcurl4 7.88.1-10+deb12u1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2023-6129 | LOW3.9 | openssl 3.0.9-1 fixed in 3.0.13-1~deb12u1 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-10524 | LOW3.9 | wget 1.21.3-1+b2 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-33636 | LOW3.88 | libpng-tools 1.6.39-2 fixed in 1.6.39-2+deb12u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-55753 | LOW3.82 | apache2-utils 2.4.57-2 fixed in 2.4.66-1~deb12u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34355 | LOW3.82 | apache2-utils 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-42536 | LOW3.82 | apache2-utils 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-47252 | LOW3.82 | apache2-utils 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-23048 | LOW3.82 | apache2-utils 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2025-49812 | LOW3.82 | apache2-utils 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-29168 | LOW3.82 | apache2-utils 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-33857 | LOW3.82 | apache2-utils 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34356 | LOW3.82 | apache2-utils 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-29169 | LOW3.82 | apache2-utils 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-0840 | LOW3.82 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW3.82 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-0840 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-0840 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | curl 7.88.1-10+deb12u1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u15 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | curl 7.88.1-10+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | curl 7.88.1-10+deb12u1 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | curl 7.88.1-10+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW3.82 | gzip 1.12-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | libcurl4 7.88.1-10+deb12u1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u15 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl4 7.88.1-10+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl4 7.88.1-10+deb12u1 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl4 7.88.1-10+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-55199 | LOW3.82 | libssh2-1 1.10.0-3+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69421 | LOW3.82 | openssl 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28389 | LOW3.82 | openssl 3.0.9-1 fixed in 3.0.19-1~deb12u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28390 | LOW3.82 | openssl 3.0.9-1 fixed in 3.0.19-1~deb12u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl 5.36.0-7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl 5.36.0-7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl-base 5.36.0-7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-base 5.36.0-7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl-modules-5.36 5.36.0-7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-modules-5.36 5.36.0-7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-31115 | LOW3.82 | xz-utils 5.4.1-0.2 fixed in 5.4.1-1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-69277 | LOW3.82 | libsodium23 1.0.18-1 fixed in 1.0.18-1+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54113 | LOW3.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40308 | LOW3.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40312 | LOW3.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-45896 | LOW3.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53831 | LOW3.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | LOW3.77 | curl 7.88.1-10+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl4 7.88.1-10+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69419 | LOW3.77 | openssl 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW3.77 | openssl 3.0.9-1 fixed in 3.0.20-1~deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2007-1743 | LOW3.74 | apache2 2.4.57-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2007-1743 | LOW3.74 | apache2-bin 2.4.57-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2007-1743 | LOW3.74 | apache2-data 2.4.57-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-64505 | LOW3.74 | libpng-dev 1.6.39-2 fixed in 1.6.39-2+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34757 | LOW3.74 | libpng-dev 1.6.39-2 fixed in 1.6.39-2+deb12u5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-64505 | LOW3.74 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34757 | LOW3.74 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+deb12u5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2020-14304 | LOW3.74 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-3772 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-3773 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-39194 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-52508 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52585 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52617 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52627 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53722 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53733 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54155 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54253 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54263 | LOW3.74 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26810 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36950 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38540 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42114 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42123 | LOW3.74 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42131 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42154 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42230 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46695 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53052 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40001 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40081 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40206 | LOW3.74 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40281 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68768 | LOW3.74 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-17977 | LOW3.74 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-52492 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52618 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-52765 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52768 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52800 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52838 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52844 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52855 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52858 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52861 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52870 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52884 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53718 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54209 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54210 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54247 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26638 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26661 | LOW3.74 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26662 | LOW3.74 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26672 | LOW3.74 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26712 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26723 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26745 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26747 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26757 | LOW3.74 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26758 | LOW3.74 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26768 | LOW3.74 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26769 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26846 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26857 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26875 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36031 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-36894 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36910 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36912 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-36913 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-36944 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38388 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38548 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38550 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38559 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38616 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-38628 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40021 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40123 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40183 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40198 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40200 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23458 | LOW3.74 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-44185 | LOW3.72 | apache2-utils 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-44186 | LOW3.72 | apache2-utils 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-48913 | LOW3.72 | apache2-utils 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-56406 | LOW3.72 | perl 5.36.0-7 fixed in 5.36.0-7+deb12u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-56406 | LOW3.72 | perl-base 5.36.0-7 fixed in 5.36.0-7+deb12u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-56406 | LOW3.72 | perl-modules-5.36 5.36.0-7 fixed in 5.36.0-7+deb12u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-36387 | LOW3.7 | apache2 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-36387 | LOW3.7 | apache2-bin 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-36387 | LOW3.7 | apache2-data 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2011-3374 | LOW3.7 | libapt-pkg6.0 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-9143 | LOW3.7 | libssl-dev 3.0.9-1 fixed in 3.0.15-1~deb12u1 | 6.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-9143 | LOW3.7 | libssl3 3.0.9-1 fixed in 3.0.15-1~deb12u1 | 6.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33655 | LOW3.7 | libunbound8 1.17.1-2 fixed in 1.17.1-2+deb12u3 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-31879 | LOW3.66 | wget 1.21.3-1+b2 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-38473 | LOW3.66 | apache2-utils 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 25.9% High Exploitation Risk | Post-Exploit |
| CVE-2023-47233 | LOW3.65 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2010-5321 | LOW3.65 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40275 | LOW3.65 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23918 | LOW3.64 | apache2-utils 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 45.8% High Exploitation Risk | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-64720 | LOW3.62 | libpng-tools 1.6.39-2 fixed in 1.6.39-2+deb12u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-65018 | LOW3.62 | libpng-tools 1.6.39-2 fixed in 1.6.39-2+deb12u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66293 | LOW3.62 | libpng-tools 1.6.39-2 fixed in 1.6.39-2+deb12u1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-22695 | LOW3.62 | libpng-tools 1.6.39-2 fixed in 1.6.39-2+deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-58471 | LOW3.62 | wget 1.21.3-1+b2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-58472 | LOW3.62 | wget 1.21.3-1+b2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2005-2541 | LOW3.6 | tar 1.34+dfsg-1.2 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-8058 | LOW3.57 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u13 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u13 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u13 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u13 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-41848 | LOW3.57 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-45802 | LOW3.54 | apache2-utils 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils-common 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-11053 | LOW3.54 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u10 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2024-11053 | LOW3.54 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u10 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2023-6237 | LOW3.54 | openssl 3.0.9-1 fixed in 3.0.13-1~deb12u1 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-5535 | LOW3.54 | openssl 3.0.9-1 fixed in 3.0.15-1~deb12u1 | 5.6% Low-Moderate Risk | Post-Exploit |
| CVE-2024-38474 | LOW3.53 | apache2-utils 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2018-13410 | LOW3.53 | zip 3.0-13 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2010-4651 | LOW3.48 | patch 2.7.6-7 No fix yet | 4.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-16089 | LOW3.48 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-3863 | LOW3.48 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52872 | LOW3.48 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36928 | LOW3.48 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42156 | LOW3.48 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42157 | LOW3.48 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42158 | LOW3.48 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42229 | LOW3.48 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40173 | LOW3.48 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-16229 | LOW3.48 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16231 | LOW3.48 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16232 | LOW3.48 | linux-libc-dev 6.1.38-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-16233 | LOW3.48 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-42516 | LOW3.47 | apache2-utils 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | curl 7.88.1-10+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u15 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl4 7.88.1-10+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u15 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-5742 | LOW3.42 | nano 7.2-1 fixed in 7.2-1+deb12u1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-33602 | LOW3.4 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9820 | LOW3.4 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9820 | LOW3.4 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW3.4 | libssl-dev 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW3.4 | libssl3 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-54229 | LOW3.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52597 | LOW3.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53708 | LOW3.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53994 | LOW3.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | LOW3.37 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53589 | LOW3.37 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53589 | LOW3.37 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-9230 | LOW3.36 | openssl 3.0.9-1 fixed in 3.0.17-1~deb12u3 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4741 | LOW3.36 | openssl 3.0.9-1 fixed in 3.0.14-1~deb12u1 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2025-65082 | LOW3.31 | apache2-utils 2.4.57-2 fixed in 2.4.66-1~deb12u1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-33523 | LOW3.31 | apache2-utils 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42535 | LOW3.31 | apache2-utils 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43951 | LOW3.31 | apache2-utils 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils 2.40-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2016-2781 | LOW3.31 | coreutils 9.1-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-8096 | LOW3.31 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u15 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | curl 7.88.1-10+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | curl 7.88.1-10+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl 7.88.1-10+deb12u1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u15 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-8096 | LOW3.31 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u15 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl4 7.88.1-10+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl4 7.88.1-10+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl4 7.88.1-10+deb12u1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u15 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15661 | LOW3.31 | libssh2-1 1.10.0-3+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl 5.36.0-7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl-base 5.36.0-7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl-modules-5.36 5.36.0-7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-common 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils-common 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils-common 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-0727 | LOW3.3 | openssl 3.0.9-1 fixed in 3.0.13-1~deb12u1 | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2018-21232 | LOW3.3 | re2c 3.0-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-48303 | LOW3.3 | tar 1.34+dfsg-1.2 fixed in 1.34+dfsg-1.2+deb12u1 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2379 | LOW3.24 | curl 7.88.1-10+deb12u1 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2379 | LOW3.24 | libcurl4 7.88.1-10+deb12u1 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-5958 | LOW3.21 | sed 4.9-1 fixed in 4.9-1+deb12u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40725 | LOW3.18 | apache2-utils 2.4.57-2 fixed in 2.4.62-1~deb12u1 | 4.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-53020 | LOW3.18 | apache2-utils 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 4.4% Low-Moderate Risk | Post-Exploit |
| CVE-2023-46219 | LOW3.18 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u5 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2004 | LOW3.18 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u6 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-46219 | LOW3.18 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u5 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2004 | LOW3.18 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u6 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-3446 | LOW3.18 | openssl 3.0.9-1 fixed in 3.0.10-1~deb12u1 | 5.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-3817 | LOW3.18 | openssl 3.0.9-1 fixed in 3.0.10-1~deb12u1 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5678 | LOW3.18 | openssl 3.0.9-1 fixed in 3.0.13-1~deb12u1 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4603 | LOW3.18 | openssl 3.0.9-1 fixed in 3.0.14-1~deb12u1 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-28162 | LOW3.16 | libpng-tools 1.6.39-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW3.15 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-41080 | LOW3.15 | libexpat1 2.5.0-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5419 | LOW3.15 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5419 | LOW3.15 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | libssl-dev 3.0.9-1 fixed in 3.0.20-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | libssl3 3.0.9-1 fixed in 3.0.20-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0989 | LOW3.15 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.11 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.38.1-5+b1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-64506 | LOW3.11 | libpng-tools 1.6.39-2 fixed in 1.6.39-2+deb12u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.38.1-5+b1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.38.1-5+b1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux-extra 2.38.1-5+b1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-42119 | LOW3.1 | exim4-base 4.96-15+deb12u1 fixed in 4.96-15+deb12u3 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-42119 | LOW3.1 | exim4-config 4.96-15+deb12u1 fixed in 4.96-15+deb12u3 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-42119 | LOW3.1 | exim4-daemon-light 4.96-15+deb12u1 fixed in 4.96-15+deb12u3 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9232 | LOW3.1 | libssl-dev 3.0.9-1 fixed in 3.0.17-1~deb12u3 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9232 | LOW3.1 | libssl3 3.0.9-1 fixed in 3.0.17-1~deb12u3 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-10966 | LOW3.01 | curl 7.88.1-10+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl4 7.88.1-10+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31790 | LOW3.01 | openssl 3.0.9-1 fixed in 3.0.19-1~deb12u2 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2025-69420 | LOW3.01 | openssl 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-22796 | LOW3.01 | openssl 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW3.01 | openssl 3.0.9-1 fixed in 3.0.20-1~deb12u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.01 | openssl 3.0.9-1 fixed in 3.0.20-1~deb12u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-40909 | LOW3.01 | perl 5.36.0-7 fixed in 5.36.0-7+deb12u3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-40909 | LOW3.01 | perl-base 5.36.0-7 fixed in 5.36.0-7+deb12u3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-40909 | LOW3.01 | perl-modules-5.36 5.36.0-7 fixed in 5.36.0-7+deb12u3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-15146 | LOW3.01 | wget 1.21.3-1+b2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2008-0456 | LOW2.99 | apache2 2.4.57-2 No fix yet | 19.0% High Exploitation Risk | Directly Exposed |
| CVE-2008-0456 | LOW2.99 | apache2-bin 2.4.57-2 No fix yet | 19.0% High Exploitation Risk | Directly Exposed |
| CVE-2008-0456 | LOW2.99 | apache2-data 2.4.57-2 No fix yet | 19.0% High Exploitation Risk | Directly Exposed |
| CVE-2026-3783 | LOW2.91 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u15 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u15 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-2511 | LOW2.89 | openssl 3.0.9-1 fixed in 3.0.14-1~deb12u1 | 54.0% Actively Exploited | Post-Exploit |
| CVE-2020-35501 | LOW2.89 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68740 | LOW2.89 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | LOW2.86 | binutils 2.40-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-common 2.40-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-24072 | LOW2.8 | apache2-utils 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-44119 | LOW2.8 | apache2-utils 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | cpp-12 12.2.0-14 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | g++-12 12.2.0-14 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | gcc-12 12.2.0-14 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | gcc-12-base 12.2.0-14 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2021-4214 | LOW2.8 | libpng-tools 1.6.39-2 No fix yet | 0.5% 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.3% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6843 | LOW2.8 | nano 7.2-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22795 | LOW2.8 | openssl 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW2.8 | openssl 3.0.9-1 fixed in 3.0.20-1~deb12u2 | 0.4% 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.3% Theoretical Threat | Post-Exploit |
| CVE-2021-45261 | LOW2.8 | patch 2.7.6-7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-56288 | LOW2.8 | patch 2.7.6-7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56289 | LOW2.8 | patch 2.7.6-7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-29088 | LOW2.8 | sqlite3 3.40.1-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.34+dfsg-1.2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux-extra 2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW2.8 | gpgv 2.2.40-1.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW2.8 | libperl5.36 5.36.0-7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-4016 | LOW2.8 | libproc2-0 2:4.0.2-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | libsqlite3-0 3.40.1-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | libsqlite3-dev 3.40.1-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8732 | LOW2.8 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68191 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2015-2877 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-52561 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52571 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52926 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53763 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53992 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53998 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54083 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54127 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54145 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54153 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54171 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54172 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54177 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54194 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54211 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54220 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54221 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54227 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54230 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54233 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54235 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54282 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54315 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54322 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26612 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26614 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26764 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26992 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35935 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41007 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41027 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-43841 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46794 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47738 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50044 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50057 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50211 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50280 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-39964 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40035 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40268 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40303 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40341 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68746 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68782 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71224 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22978 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31668 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-43204 | LOW2.75 | apache2-utils 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-66200 | LOW2.75 | apache2-utils 2.4.57-2 fixed in 2.4.66-1~deb12u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-29170 | LOW2.75 | apache2-utils 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-33007 | LOW2.7 | apache2-utils 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | bsdutils 1:2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | curl 7.88.1-10+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | curl 7.88.1-10+deb12u1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u15 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl4 7.88.1-10+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl4 7.88.1-10+deb12u1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u15 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3713 | LOW2.7 | libpng-tools 1.6.39-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | mount 2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-2975 | LOW2.7 | openssl 3.0.9-1 fixed in 3.0.10-1~deb12u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42766 | LOW2.7 | openssl 3.0.9-1 fixed in 3.0.20-1~deb12u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42767 | LOW2.7 | openssl 3.0.9-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl 5.36.0-7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-base 5.36.0-7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-modules-5.36 5.36.0-7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux 2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux-extra 2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux-extra 2.38.1-5+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58470 | LOW2.7 | wget 1.21.3-1+b2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-34743 | LOW2.7 | xz-utils 5.4.1-0.2 fixed in 5.4.1-1+deb12u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-28085 | LOW2.64 | bsdutils 1:2.38.1-5+b1 fixed in 2.38.1-5+deb12u1 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28085 | LOW2.64 | mount 2.38.1-5+b1 fixed in 2.38.1-5+deb12u1 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28085 | LOW2.64 | util-linux 2.38.1-5+b1 fixed in 2.38.1-5+deb12u1 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28085 | LOW2.64 | util-linux-extra 2.38.1-5+b1 fixed in 2.38.1-5+deb12u1 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1148 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2003-1581 | LOW2.6 | apache2 2.4.57-2 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1581 | LOW2.6 | apache2-bin 2.4.57-2 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1581 | LOW2.6 | apache2-data 2.4.57-2 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1307 | LOW2.58 | apache2-utils 2.4.57-2 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2003-1580 | LOW2.58 | apache2-utils 2.4.57-2 No fix yet | 3.7% Low-Moderate Risk | Post-Exploit |
| CVE-2021-45346 | LOW2.58 | sqlite3 3.40.1-2 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-42250 | LOW2.55 | bzip2 1.0.8-5+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-28164 | LOW2.55 | libpng-tools 1.6.39-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-34180 | LOW2.55 | openssl 3.0.9-1 fixed in 3.0.20-1~deb12u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl 5.36.0-7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl 5.36.0-7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl-base 5.36.0-7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl-base 5.36.0-7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl-modules-5.36 5.36.0-7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl-modules-5.36 5.36.0-7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2007-3303 | LOW2.5 | apache2-utils 2.4.57-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | login 1:4.13+dfsg1-1+b1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.13+dfsg1-1+b1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW2.46 | gpgv 2.2.40-1.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0992 | LOW2.46 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-33006 | LOW2.45 | apache2-utils 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4039 | LOW2.45 | cpp-12 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-10148 | LOW2.45 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u15 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | curl 7.88.1-10+deb12u1 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.7% Theoretical Threat | Post-Exploit |
| CVE-2023-4039 | LOW2.45 | gcc-12 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-4039 | LOW2.45 | gcc-12-base 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-10148 | LOW2.45 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u15 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl4 7.88.1-10+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 9.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | curl 7.88.1-10+deb12u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl 7.88.1-10+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.12-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | libcurl4 7.88.1-10+deb12u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl4 7.88.1-10+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-13176 | LOW2.4 | openssl 3.0.9-1 fixed in 3.0.16-1~deb12u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-68160 | LOW2.4 | openssl 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux-extra 2.38.1-5+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-24795 | LOW2.4 | apache2-utils 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0725 | LOW2.4 | curl 7.88.1-10+deb12u1 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0725 | LOW2.4 | libcurl4 7.88.1-10+deb12u1 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-69644 | LOW2.38 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43167 | LOW2.38 | libunbound8 1.17.1-2 fixed in 1.17.1-2+deb12u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-29167 | LOW2.35 | apache2-utils 2.4.57-2 fixed in 2.4.68-1~deb12u1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2007-1743 | LOW2.24 | apache2-utils 2.4.57-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils 9.1-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-64505 | LOW2.24 | libpng-tools 1.6.39-2 fixed in 1.6.39-2+deb12u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-34757 | LOW2.24 | libpng-tools 1.6.39-2 fixed in 1.6.39-2+deb12u5 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36387 | LOW2.22 | apache2-utils 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-38546 | LOW2.22 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u4 | 6.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-38546 | LOW2.22 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u4 | 6.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-9143 | LOW2.22 | openssl 3.0.9-1 fixed in 3.0.15-1~deb12u1 | 6.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-24515 | LOW2.12 | libexpat1 2.5.0-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-57053 | LOW2.12 | libidn12 1.41-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6170 | LOW2.12 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-11191 | LOW2.12 | linux-libc-dev 6.1.38-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-52620 | LOW2.12 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54246 | LOW2.12 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54267 | LOW2.12 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54283 | LOW2.12 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54312 | LOW2.12 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54316 | LOW2.12 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68788 | LOW2.12 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW2.04 | openssl 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-45446 | LOW1.89 | openssl 3.0.9-1 fixed in 3.0.20-1~deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-9232 | LOW1.86 | openssl 3.0.9-1 fixed in 3.0.17-1~deb12u3 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | login 1:4.13+dfsg1-1+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.13+dfsg1-1+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2008-0456 | LOW1.79 | apache2-utils 2.4.57-2 No fix yet | 19.0% High Exploitation Risk | Post-Exploit |
| CVE-2001-1534 | LOW1.78 | apache2 2.4.57-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2001-1534 | LOW1.78 | apache2-bin 2.4.57-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2001-1534 | LOW1.78 | apache2-data 2.4.57-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2007-3719 | LOW1.78 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW1.68 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-29383 | LOW1.68 | login 1:4.13+dfsg1-1+b1 fixed in 1:4.13+dfsg1-1+deb12u1 | 0.4% 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.4% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl 5.36.0-7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-base 5.36.0-7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-modules-5.36 5.36.0-7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-4016 | LOW1.68 | procps 2:4.0.2-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2903 | LOW1.68 | re2c 3.0-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-70873 | LOW1.68 | sqlite3 3.40.1-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-39804 | LOW1.68 | tar 1.34+dfsg-1.2 fixed in 1.34+dfsg-1.2+deb12u1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-4217 | LOW1.68 | unzip 6.0-28 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-42155 | LOW1.61 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2003-1581 | LOW1.56 | apache2-utils 2.4.57-2 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6842 | LOW1.27 | nano 7.2-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2001-1534 | LOW1.07 | apache2-utils 2.4.57-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | NONE0 | libncursesw6 6.4-4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6020 | NONE0 | libpam-modules 1.5.2-6 fixed in 1.5.2-6+deb12u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6020 | NONE0 | libpam-modules-bin 1.5.2-6 fixed in 1.5.2-6+deb12u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6020 | NONE0 | libpam-runtime 1.5.2-6 fixed in 1.5.2-6+deb12u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6020 | NONE0 | libpam0g 1.5.2-6 fixed in 1.5.2-6+deb12u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-29111 | NONE0 | libsystemd0 252.12-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.4-4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-29111 | NONE0 | libudev1 252.12-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.4-4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.4-4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-50387 | NONE0 | libsystemd0 252.12-1~deb12u1 fixed in 252.23-1~deb12u1 | 100.0% Actively Exploited | Not Applicable |
| CVE-2023-50868 | NONE0 | libsystemd0 252.12-1~deb12u1 fixed in 252.23-1~deb12u1 | 81.7% Actively Exploited | Not Applicable |
| CVE-2023-50387 | NONE0 | libudev1 252.12-1~deb12u1 fixed in 252.23-1~deb12u1 | 100.0% Actively Exploited | Not Applicable |
| CVE-2023-50868 | NONE0 | libudev1 252.12-1~deb12u1 fixed in 252.23-1~deb12u1 | 81.7% Actively Exploited | Not Applicable |
| CVE-2026-4105 | NONE0 | libsystemd0 252.12-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4105 | NONE0 | libudev1 252.12-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libncursesw6 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libtinfo6 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-bin 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-40225 | NONE0 | libsystemd0 252.12-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40226 | NONE0 | libsystemd0 252.12-1~deb12u1 fixed in 252.39-1~deb12u2 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40225 | NONE0 | libudev1 252.12-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40226 | NONE0 | libudev1 252.12-1~deb12u1 fixed in 252.39-1~deb12u2 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-7008 | NONE0 | libsystemd0 252.12-1~deb12u1 fixed in 252.21-1~deb12u1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-7008 | NONE0 | libudev1 252.12-1~deb12u1 fixed in 252.21-1~deb12u1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam-modules 1.5.2-6 fixed in 1.5.2-6+deb12u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam-modules-bin 1.5.2-6 fixed in 1.5.2-6+deb12u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam-runtime 1.5.2-6 fixed in 1.5.2-6+deb12u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam0g 1.5.2-6 fixed in 1.5.2-6+deb12u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-31437 | NONE0 | libsystemd0 252.12-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | libsystemd0 252.12-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | libsystemd0 252.12-1~deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31437 | NONE0 | libudev1 252.12-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | libudev1 252.12-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | libudev1 252.12-1~deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules 1.5.2-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules-bin 1.5.2-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-runtime 1.5.2-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam0g 1.5.2-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-modules 1.5.2-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-modules-bin 1.5.2-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-runtime 1.5.2-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam0g 1.5.2-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-4598 | NONE0 | libsystemd0 252.12-1~deb12u1 fixed in 252.38-1~deb12u1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-4598 | NONE0 | libudev1 252.12-1~deb12u1 fixed in 252.38-1~deb12u1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncursesw6 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | libsystemd0 252.12-1~deb12u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | libsystemd0 252.12-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | libudev1 252.12-1~deb12u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | libudev1 252.12-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-bin 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| DSA-5729-2 | NONE0 | apache2 2.4.57-2 fixed in 2.4.62-1~deb12u2 | — | Not Applicable |
| DSA-5729-2 | NONE0 | apache2-bin 2.4.57-2 fixed in 2.4.62-1~deb12u2 | — | Not Applicable |
| DSA-5729-2 | NONE0 | apache2-data 2.4.57-2 fixed in 2.4.62-1~deb12u2 | — | Not Applicable |
| DSA-5729-2 | NONE0 | apache2-utils 2.4.57-2 fixed in 2.4.62-1~deb12u2 | — | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.2.15-2+b2 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | bsdutils 1:2.38.1-5+b1 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | bsdutils 1:2.38.1-5+b1 No fix yet | — | Not Applicable |
| CVE-2025-0167 | NONE0 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u11 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-8458 | NONE0 | curl 7.88.1-10+deb12u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-2219 | NONE0 | dpkg 1.21.22 fixed in 1.21.23 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6297 | NONE0 | dpkg 1.21.22 fixed in 1.21.23 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-2219 | NONE0 | dpkg-dev 1.21.22 fixed in 1.21.23 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6297 | NONE0 | dpkg-dev 1.21.22 fixed in 1.21.23 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45185 | NONE0 | exim4-base 4.96-15+deb12u1 fixed in 4.96-15+deb12u9 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-48840 | NONE0 | exim4-base 4.96-15+deb12u1 fixed in 4.96-15+deb12u10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45185 | NONE0 | exim4-config 4.96-15+deb12u1 fixed in 4.96-15+deb12u9 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-48840 | NONE0 | exim4-config 4.96-15+deb12u1 fixed in 4.96-15+deb12u10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45185 | NONE0 | exim4-daemon-light 4.96-15+deb12u1 fixed in 4.96-15+deb12u9 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-48840 | NONE0 | exim4-daemon-light 4.96-15+deb12u1 fixed in 4.96-15+deb12u10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid1 2.38.1-5+b1 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libblkid1 2.38.1-5+b1 No fix yet | — | Not Applicable |
| CVE-2025-0167 | NONE0 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u11 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl4 7.88.1-10+deb12u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-2219 | NONE0 | libdpkg-perl 1.21.22 fixed in 1.21.23 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6297 | NONE0 | libdpkg-perl 1.21.22 fixed in 1.21.23 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56131 | NONE0 | libexpat1 2.5.0-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56407 | NONE0 | libexpat1 2.5.0-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56408 | NONE0 | libexpat1 2.5.0-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56409 | NONE0 | libexpat1 2.5.0-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount1 2.38.1-5+b1 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libmount1 2.38.1-5+b1 No fix yet | — | Not Applicable |
| CVE-2026-58055 | NONE0 | libnghttp2-14 1.52.0-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | libperl5.36 5.36.0-7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | libperl5.36 5.36.0-7 No fix yet | — | Not Applicable |
| CVE-2026-7017 | NONE0 | libperl5.36 5.36.0-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libsmartcols1 2.38.1-5+b1 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libsmartcols1 2.38.1-5+b1 No fix yet | — | Not Applicable |
| CVE-2025-7709 | NONE0 | libsqlite3-0 3.40.1-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11822 | NONE0 | libsqlite3-0 3.40.1-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-0 3.40.1-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50812 | NONE0 | libsqlite3-0 3.40.1-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50813 | NONE0 | libsqlite3-0 3.40.1-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-7709 | NONE0 | libsqlite3-dev 3.40.1-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11822 | NONE0 | libsqlite3-dev 3.40.1-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-dev 3.40.1-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50812 | NONE0 | libsqlite3-dev 3.40.1-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50813 | NONE0 | libsqlite3-dev 3.40.1-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-27587 | NONE0 | libssl-dev 3.0.9-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-27587 | NONE0 | libssl3 3.0.9-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libuuid1 2.38.1-5+b1 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libuuid1 2.38.1-5+b1 No fix yet | — | Not Applicable |
| DSA-5990-1 | NONE0 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u4 | — | Not Applicable |
| CVE-2026-43011 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53215 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23268 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23372 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31405 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31432 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31433 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31476 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31478 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31627 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31656 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31657 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31659 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31695 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31705 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31706 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31712 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31716 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31780 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43075 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43076 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43206 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43236 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43370 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43490 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52911 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52914 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53040 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53043 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53046 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53068 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53130 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53186 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53198 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-53693 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53699 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53707 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53714 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53725 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53727 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53732 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53782 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53801 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53807 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53817 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-53834 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53855 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53865 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54005 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54017 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54025 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54049 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54104 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54112 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54115 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54125 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54140 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54142 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54143 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54178 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54183 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54196 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54219 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54225 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54240 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54241 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54255 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54266 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54272 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54293 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54297 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54304 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54319 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36331 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-27558 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37838 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39985 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39986 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39987 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39988 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39995 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40003 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40008 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40013 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40022 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40032 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40036 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40043 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40055 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40060 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40062 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40068 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40077 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40084 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40087 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40093 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40095 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40097 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40106 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40107 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40112 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40116 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40124 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40126 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40127 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40137 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40156 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40180 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40188 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40193 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40202 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40207 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40223 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40233 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40243 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40245 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40262 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40263 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40266 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40278 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40282 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40285 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40286 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40288 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40289 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40306 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40311 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40313 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40314 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40315 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40317 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40333 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40337 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40354 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40358 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68177 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68190 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68201 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68217 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68220 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68238 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68246 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68249 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68254 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68255 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68256 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68257 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68258 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68263 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68266 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68286 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68289 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68290 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68302 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68303 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68315 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68320 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68322 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68325 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68327 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68328 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68330 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68332 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68335 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68339 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68344 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68364 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68369 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68727 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68728 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68733 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68750 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68759 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68765 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68766 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68767 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68769 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68771 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68772 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68773 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68777 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68781 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68786 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68787 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68796 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68797 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68799 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68804 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68806 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68808 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68809 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71065 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71067 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71069 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71192 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71196 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71197 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71198 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71199 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23030 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23033 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23037 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23049 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23056 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23176 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23182 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23245 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23269 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23364 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23393 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23406 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23407 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31396 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31409 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31417 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31477 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31494 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31563 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31597 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31598 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31602 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31611 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31612 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31622 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31626 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31629 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31683 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31707 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31711 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31768 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43117 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43184 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43203 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43212 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43258 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43336 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43373 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43377 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43476 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43495 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45935 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45958 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46006 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46031 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46058 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46062 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46110 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46112 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46124 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46129 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46164 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46177 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46197 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46198 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46199 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46204 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46205 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46206 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46208 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46212 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46218 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46230 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46238 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46328 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52919 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52922 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52931 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52934 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53041 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53045 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53056 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53066 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53107 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53329 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53330 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53331 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53332 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53343 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53345 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53356 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31587 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31761 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43207 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43232 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43249 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43256 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43283 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43291 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43324 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43497 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46250 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46265 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46270 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53065 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53082 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53112 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53160 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53161 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53216 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53217 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53273 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.176-1 | 0.1% Theoretical Threat | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2023-53851 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53864 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54000 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54027 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54101 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login 1:4.13+dfsg1-1+b1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | mount 2.38.1-5+b1 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | mount 2.38.1-5+b1 No fix yet | — | Not Applicable |
| CVE-2025-27587 | NONE0 | openssl 3.0.9-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.13+dfsg1-1+b1 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl 5.36.0-7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl 5.36.0-7 No fix yet | — | Not Applicable |
| CVE-2026-7017 | NONE0 | perl 5.36.0-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.36.0-7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-base 5.36.0-7 No fix yet | — | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-base 5.36.0-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-modules-5.36 5.36.0-7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-modules-5.36 5.36.0-7 No fix yet | — | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-modules-5.36 5.36.0-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7709 | NONE0 | sqlite3 3.40.1-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11822 | NONE0 | sqlite3 3.40.1-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | sqlite3 3.40.1-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50812 | NONE0 | sqlite3 3.40.1-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50813 | NONE0 | sqlite3 3.40.1-2 No fix yet | 0.1% Theoretical Threat | 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 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | util-linux 2.38.1-5+b1 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | util-linux 2.38.1-5+b1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | util-linux-extra 2.38.1-5+b1 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | util-linux-extra 2.38.1-5+b1 No fix yet | — | Not Applicable |
| CVE-2026-58469 | NONE0 | wget 1.21.3-1+b2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-45769 | NONE0 | firebase/php-jwt v6.8.1 fixed in 7.0.0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55568 | NONE0 | guzzlehttp/guzzle 7.7.0 fixed in 7.12.1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55767 | NONE0 | guzzlehttp/guzzle 7.7.0 fixed in 7.12.1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-49214 | NONE0 | guzzlehttp/psr7 2.5.0 fixed in 2.10.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55766 | NONE0 | guzzlehttp/psr7 2.5.0 fixed in 2.12.1 | 0.2% Theoretical Threat | Not Applicable |
| GHSA-fc86-6rv6-2jpm | NONE0 | webonyx/graphql-php v15.5.3 fixed in 15.32.2 | — | Not Applicable |
| GHSA-r7cg-qjjm-xhqq | NONE0 | webonyx/graphql-php v15.5.3 fixed in 15.32.3 | — | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.