This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker could achieve arbitrary code execution or sensitive information disclosure on the Apache HTTP Server, the primary service, through critical vulnerabilities. Notably, CVE-2024-38475 applies specifically if unsafe RewriteRules are configured, and CVE-2024-38476 requires malicious or exploitable backend application response headers. Furthermore, the image is from an unverified community publisher with low trust and very few downloads, significantly increasing its risk. Immediate remediation, including upgrading Apache to a patched version (2.4.60 or higher for CVE-2024-38476), is essential if this image must be considered for use.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2024-38475 | CRITICAL10 | apache2 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 93.8% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2024-38475 | CRITICAL10 | apache2-bin 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 93.8% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2024-38475 | CRITICAL10 | apache2-data 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 93.8% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2024-38475 | CRITICAL10 | apache2-utils 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 93.8% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2025-27363 | CRITICAL10 | libfreetype-dev 2.12.1+dfsg-5 fixed in 2.12.1+dfsg-5+deb12u4 | 69.2% Actively Exploited | Directly Exposed |
| CVE-2025-27363 | CRITICAL10 | libfreetype6 2.12.1+dfsg-5 fixed in 2.12.1+dfsg-5+deb12u4 | 69.2% Actively Exploited | Directly Exposed |
| CVE-2025-27363 | CRITICAL10 | libfreetype6-dev 2.12.1+dfsg-5 fixed in 2.12.1+dfsg-5+deb12u4 | 69.2% Actively Exploited | Directly Exposed |
| CVE-2023-4911 | CRITICAL10 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u3 | 67.2% Actively Exploited | Directly Exposed |
| CVE-2023-4911 | CRITICAL10 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u3 | 67.2% Actively Exploited | Directly Exposed |
| CVE-2024-38476 | CRITICAL9.8 | apache2 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 4.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-38476 | CRITICAL9.8 | apache2-bin 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 4.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-38476 | CRITICAL9.8 | apache2-data 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 4.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-38476 | CRITICAL9.8 | apache2-utils 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 4.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-42116 | CRITICAL9.8 | exim4-base 4.96-15+deb12u1 fixed in 4.96-15+deb12u2 | 6.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-42117 | CRITICAL9.8 | exim4-base 4.96-15+deb12u1 fixed in 4.96-15+deb12u3 | 7.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-42116 | CRITICAL9.8 | exim4-config 4.96-15+deb12u1 fixed in 4.96-15+deb12u2 | 6.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-42117 | CRITICAL9.8 | exim4-config 4.96-15+deb12u1 fixed in 4.96-15+deb12u3 | 7.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-42116 | CRITICAL9.8 | exim4-daemon-light 4.96-15+deb12u1 fixed in 4.96-15+deb12u2 | 6.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-42117 | CRITICAL9.8 | exim4-daemon-light 4.96-15+deb12u1 fixed in 4.96-15+deb12u3 | 7.3% 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 | — | Directly Exposed |
| CVE-2026-42010 | CRITICAL9.8 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | — | Directly Exposed |
| CVE-2026-8376 | CRITICAL9.8 | libperl5.36 5.36.0-7 No fix yet | — | Directly Exposed |
| CVE-2025-6965 | CRITICAL9.8 | libsqlite3-0 3.40.1-2 fixed in 3.40.1-2+deb12u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-6965 | CRITICAL9.8 | libsqlite3-dev 3.40.1-2 fixed in 3.40.1-2+deb12u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33278 | CRITICAL9.8 | libunbound8 1.17.1-2 No fix yet | — | Directly Exposed |
| CVE-2023-45853 | CRITICAL9.8 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45853 | CRITICAL9.8 | zlib1g-dev 1:1.2.13.dfsg-1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-43622 | CRITICAL9.75 | apache2 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 61.3% Actively Exploited | Directly Exposed |
| CVE-2024-27316 | CRITICAL9.75 | apache2 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 89.4% Actively Exploited | Directly Exposed |
| CVE-2023-43622 | CRITICAL9.75 | apache2-bin 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 61.3% Actively Exploited | Directly Exposed |
| CVE-2024-27316 | CRITICAL9.75 | apache2-bin 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 89.4% Actively Exploited | Directly Exposed |
| CVE-2023-43622 | CRITICAL9.75 | apache2-data 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 61.3% Actively Exploited | Directly Exposed |
| CVE-2024-27316 | CRITICAL9.75 | apache2-data 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 89.4% Actively Exploited | Directly Exposed |
| CVE-2023-43622 | CRITICAL9.75 | apache2-utils 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 61.3% Actively Exploited | Directly Exposed |
| CVE-2024-27316 | CRITICAL9.75 | apache2-utils 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 89.4% Actively Exploited | Directly Exposed |
| CVE-2023-44487 | CRITICAL9.75 | libnghttp2-14 1.52.0-1 fixed in 1.52.0-1+deb12u1 | 94.5% Actively Exploited | Directly Exposed |
| CVE-2023-50387 | CRITICAL9.75 | libsystemd0 252.12-1~deb12u1 fixed in 252.23-1~deb12u1 | 52.0% Actively Exploited | Directly Exposed |
| CVE-2023-50387 | CRITICAL9.75 | libudev1 252.12-1~deb12u1 fixed in 252.23-1~deb12u1 | 52.0% Actively Exploited | Directly Exposed |
| CVE-2023-50387 | CRITICAL9.75 | libunbound8 1.17.1-2 fixed in 1.17.1-2+deb12u2 | 52.0% Actively Exploited | Directly Exposed |
| CVE-2024-37371 | CRITICAL9.1 | libgssapi-krb5-2 1.20.1-2 fixed in 1.20.1-2+deb12u2 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-37371 | CRITICAL9.1 | libk5crypto3 1.20.1-2 fixed in 1.20.1-2+deb12u2 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-37371 | CRITICAL9.1 | libkrb5-3 1.20.1-2 fixed in 1.20.1-2+deb12u2 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-37371 | CRITICAL9.1 | libkrb5support0 1.20.1-2 fixed in 1.20.1-2+deb12u2 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42496 | CRITICAL9.1 | libperl5.36 5.36.0-7 No fix yet | — | Directly Exposed |
| CVE-2026-45445 | CRITICAL9.1 | libssl-dev 3.0.9-1 fixed in 3.0.20-1~deb12u2 | — | Directly Exposed |
| CVE-2026-45445 | CRITICAL9.1 | libssl3 3.0.9-1 fixed in 3.0.20-1~deb12u2 | — | 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.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6246 | HIGH8.97 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u4 | 25.5% High Exploitation Risk | Directly Exposed |
| CVE-2023-6246 | HIGH8.97 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u4 | 25.5% High Exploitation Risk | Directly Exposed |
| CVE-2023-38039 | HIGH8.62 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u3 | 12.3% High Exploitation Risk | Directly Exposed |
| CVE-2023-50868 | HIGH8.62 | libsystemd0 252.12-1~deb12u1 fixed in 252.23-1~deb12u1 | 11.8% High Exploitation Risk | Directly Exposed |
| CVE-2023-50868 | HIGH8.62 | libudev1 252.12-1~deb12u1 fixed in 252.23-1~deb12u1 | 11.8% High Exploitation Risk | Directly Exposed |
| CVE-2023-50868 | HIGH8.62 | libunbound8 1.17.1-2 fixed in 1.17.1-2+deb12u2 | 11.8% High Exploitation Risk | Directly Exposed |
| CVE-2024-38474 | HIGH8.33 | apache2 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-38474 | HIGH8.33 | apache2-bin 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-38474 | HIGH8.33 | apache2-data 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-38474 | HIGH8.33 | apache2-utils 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-40685 | HIGH8.33 | exim4-base 4.96-15+deb12u1 fixed in 4.96-15+deb12u9 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40685 | HIGH8.33 | exim4-config 4.96-15+deb12u1 fixed in 4.96-15+deb12u9 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40685 | HIGH8.33 | exim4-daemon-light 4.96-15+deb12u1 fixed in 4.96-15+deb12u9 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-1010022 | HIGH8.33 | libc-bin 2.36-9+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-1010022 | HIGH8.33 | libc6 2.36-9+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-45491 | HIGH8.33 | libexpat1 2.5.0-1 fixed in 2.5.0-1+deb12u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | HIGH8.33 | libssl-dev 3.0.9-1 fixed in 3.0.19-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15467 | HIGH8.33 | libssl-dev 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | HIGH8.33 | libssl3 3.0.9-1 fixed in 3.0.19-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15467 | HIGH8.33 | libssl3 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-56171 | HIGH8.33 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-51736 | HIGH8.33 | symfony/process v6.3.2 fixed in 5.1.0, 5.4.0, 7.1.0, 5.0.0, 5.3.0, 6.2.0, 6.3.0, 3.0.0, 5.2.0, 5.4.46, 7.1.7, 4.0.0, 6.1.0, 6.4.0, 6.4.14 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42013 | HIGH8.2 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u7 | — | Directly Exposed |
| CVE-2026-5260 | HIGH8.2 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u7 | — | Directly Exposed |
| CVE-2026-42013 | HIGH8.2 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | — | Directly Exposed |
| CVE-2026-5260 | HIGH8.2 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | — | Directly Exposed |
| CVE-2023-31484 | HIGH8.1 | libperl5.36 5.36.0-7 fixed in 5.36.0-7+deb12u3 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45447 | HIGH8.1 | libssl-dev 3.0.9-1 fixed in 3.0.20-1~deb12u2 | — | Directly Exposed |
| CVE-2026-45447 | HIGH8.1 | libssl3 3.0.9-1 fixed in 3.0.20-1~deb12u2 | — | Directly Exposed |
| CVE-2026-42960 | HIGH8 | libunbound8 1.17.1-2 No fix yet | — | Directly ExposedContext importance: MEDIUM |
| CVE-2023-38545 | HIGH8 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u4 | 26.3% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2024-2961 | HIGH8 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u6 | 91.9% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2024-2961 | HIGH8 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u6 | 91.9% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-4863 | HIGH8 | libwebp-dev 1.2.4-0.2 fixed in 1.2.4-0.2+deb12u1 | 94.1% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-4863 | HIGH8 | libwebp7 1.2.4-0.2 fixed in 1.2.4-0.2+deb12u1 | 94.1% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-4863 | HIGH8 | libwebpdemux2 1.2.4-0.2 fixed in 1.2.4-0.2+deb12u1 | 94.1% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-4863 | HIGH8 | libwebpmux3 1.2.4-0.2 fixed in 1.2.4-0.2+deb12u1 | 94.1% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2007-0086 | HIGH7.8 | apache2 2.4.57-2 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2007-0086 | HIGH7.8 | apache2-bin 2.4.57-2 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2007-0086 | HIGH7.8 | apache2-data 2.4.57-2 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2007-0086 | HIGH7.8 | apache2-utils 2.4.57-2 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-48962 | HIGH7.8 | libperl5.36 5.36.0-7 No fix yet | — | Directly Exposed |
| CVE-2026-40687 | HIGH7.73 | exim4-base 4.96-15+deb12u1 fixed in 4.96-15+deb12u9 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40687 | HIGH7.73 | exim4-config 4.96-15+deb12u1 fixed in 4.96-15+deb12u9 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40687 | HIGH7.73 | exim4-daemon-light 4.96-15+deb12u1 fixed in 4.96-15+deb12u9 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33845 | HIGH7.73 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33845 | HIGH7.73 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7458 | HIGH7.73 | libsqlite3-0 3.40.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7458 | HIGH7.73 | libsqlite3-dev 3.40.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7598 | HIGH7.73 | libssh2-1 1.10.0-3+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-49794 | HIGH7.73 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-38477 | HIGH7.5 | apache2 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-49975 | HIGH7.5 | apache2 2.4.57-2 fixed in 2.4.67-1~deb12u3 | — | Directly Exposed |
| CVE-2025-49630 | HIGH7.5 | apache2 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-38477 | HIGH7.5 | apache2-bin 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-49975 | HIGH7.5 | apache2-bin 2.4.57-2 fixed in 2.4.67-1~deb12u3 | — | Directly Exposed |
| CVE-2025-49630 | HIGH7.5 | apache2-bin 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-38477 | HIGH7.5 | apache2-data 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-49975 | HIGH7.5 | apache2-data 2.4.57-2 fixed in 2.4.67-1~deb12u3 | — | Directly Exposed |
| CVE-2025-49630 | HIGH7.5 | apache2-data 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-38477 | HIGH7.5 | apache2-utils 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-49975 | HIGH7.5 | apache2-utils 2.4.57-2 fixed in 2.4.67-1~deb12u3 | — | Directly Exposed |
| CVE-2025-49630 | HIGH7.5 | apache2-utils 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-bin 2.36-9+deb12u1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6 2.36-9+deb12u1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5773 | HIGH7.5 | libcurl4 7.88.1-10+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2026-6276 | HIGH7.5 | libcurl4 7.88.1-10+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2024-2398 | HIGH7.5 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u6 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-52425 | HIGH7.5 | libexpat1 2.5.0-1 fixed in 2.5.0-1+deb12u2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45186 | HIGH7.5 | libexpat1 2.5.0-1 No fix yet | — | Directly Exposed |
| CVE-2024-28757 | HIGH7.5 | libexpat1 2.5.0-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0567 | HIGH7.5 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42009 | HIGH7.5 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u7 | — | Directly Exposed |
| CVE-2024-0567 | HIGH7.5 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42009 | HIGH7.5 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | — | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libgssapi-krb5-2 1.20.1-2 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libk5crypto3 1.20.1-2 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5-3 1.20.1-2 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5support0 1.20.1-2 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2953 | HIGH7.5 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2015-3276 | HIGH7.5 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | HIGH7.5 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 6.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42497 | HIGH7.5 | libperl5.36 5.36.0-7 No fix yet | — | Directly Exposed |
| CVE-2026-9538 | HIGH7.5 | libperl5.36 5.36.0-7 No fix yet | — | Directly Exposed |
| CVE-2023-5363 | HIGH7.5 | libssl-dev 3.0.9-1 fixed in 3.0.11-1~deb12u2 | 4.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-6119 | HIGH7.5 | libssl-dev 3.0.9-1 fixed in 3.0.14-1~deb12u2 | 6.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5363 | HIGH7.5 | libssl3 3.0.9-1 fixed in 3.0.11-1~deb12u2 | 4.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-6119 | HIGH7.5 | libssl3 3.0.9-1 fixed in 3.0.14-1~deb12u2 | 6.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-40622 | HIGH7.5 | libunbound8 1.17.1-2 No fix yet | — | Directly Exposed |
| CVE-2026-41292 | HIGH7.5 | libunbound8 1.17.1-2 No fix yet | — | Directly Exposed |
| CVE-2026-42944 | HIGH7.5 | libunbound8 1.17.1-2 No fix yet | — | Directly Exposed |
| CVE-2026-42959 | HIGH7.5 | libunbound8 1.17.1-2 No fix yet | — | Directly Exposed |
| CVE-2025-6021 | HIGH7.5 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u3 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-23918 | HIGH7.48 | apache2 2.4.57-2 fixed in 2.4.67-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23918 | HIGH7.48 | apache2-bin 2.4.57-2 fixed in 2.4.67-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23918 | HIGH7.48 | apache2-data 2.4.57-2 fixed in 2.4.67-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23918 | HIGH7.48 | apache2-utils 2.4.57-2 fixed in 2.4.67-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-1010023 | HIGH7.48 | libc-bin 2.36-9+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2019-1010023 | HIGH7.48 | libc6 2.36-9+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-39573 | HIGH7.4 | apache2 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-39573 | HIGH7.4 | apache2-bin 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-39573 | HIGH7.4 | apache2-data 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-39573 | HIGH7.4 | apache2-utils 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42011 | HIGH7.4 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u7 | — | Directly Exposed |
| CVE-2026-42011 | HIGH7.4 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | — | Directly Exposed |
| CVE-2026-34182 | HIGH7.4 | libssl-dev 3.0.9-1 fixed in 3.0.20-1~deb12u2 | — | Directly Exposed |
| CVE-2026-34182 | HIGH7.4 | libssl3 3.0.9-1 fixed in 3.0.20-1~deb12u2 | — | Directly Exposed |
| CVE-2026-42012 | HIGH7.1 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u7 | — | Directly Exposed |
| CVE-2026-42012 | HIGH7.1 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | — | Directly Exposed |
| CVE-2026-34032 | MEDIUM6.97 | apache2 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34059 | MEDIUM6.97 | apache2 2.4.57-2 fixed in 2.4.67-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34032 | MEDIUM6.97 | apache2-bin 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34059 | MEDIUM6.97 | apache2-bin 2.4.57-2 fixed in 2.4.67-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34032 | MEDIUM6.97 | apache2-data 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34059 | MEDIUM6.97 | apache2-data 2.4.57-2 fixed in 2.4.67-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34032 | MEDIUM6.97 | apache2-utils 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34059 | MEDIUM6.97 | apache2-utils 2.4.57-2 fixed in 2.4.67-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-32988 | MEDIUM6.97 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-32990 | MEDIUM6.97 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-32988 | MEDIUM6.97 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-32990 | MEDIUM6.97 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38473 | MEDIUM6.89 | apache2 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 88.4% Actively Exploited | Directly Exposed |
| CVE-2024-38473 | MEDIUM6.89 | apache2-bin 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 88.4% Actively Exploited | Directly Exposed |
| CVE-2024-38473 | MEDIUM6.89 | apache2-data 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 88.4% Actively Exploited | Directly Exposed |
| CVE-2024-38473 | MEDIUM6.89 | apache2-utils 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 88.4% Actively Exploited | Directly Exposed |
| CVE-2026-28780 | MEDIUM6.88 | apache2 2.4.57-2 fixed in 2.4.67-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28780 | MEDIUM6.88 | apache2-bin 2.4.57-2 fixed in 2.4.67-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28780 | MEDIUM6.88 | apache2-data 2.4.57-2 fixed in 2.4.67-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28780 | MEDIUM6.88 | apache2-utils 2.4.57-2 fixed in 2.4.67-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | MEDIUM6.88 | libcurl4 7.88.1-10+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31486 | MEDIUM6.88 | libperl5.36 5.36.0-7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-25646 | MEDIUM6.88 | libpng-dev 1.6.39-2 fixed in 1.6.39-2+deb12u3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-25646 | MEDIUM6.88 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+deb12u3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | libssl-dev 3.0.9-1 fixed in 3.0.19-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | libssl3 3.0.9-1 fixed in 3.0.19-1~deb12u2 | <0.1% 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-38709 | MEDIUM6.8 | apache2-utils 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-30232 | MEDIUM6.63 | exim4-base 4.96-15+deb12u1 fixed in 4.96-15+deb12u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-30232 | MEDIUM6.63 | exim4-config 4.96-15+deb12u1 fixed in 4.96-15+deb12u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-30232 | MEDIUM6.63 | exim4-daemon-light 4.96-15+deb12u1 fixed in 4.96-15+deb12u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-25210 | MEDIUM6.63 | libexpat1 2.5.0-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-47038 | MEDIUM6.63 | libperl5.36 5.36.0-7 fixed in 5.36.0-7+deb12u1 | 0.1% 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-2026-29111 | MEDIUM6.63 | libsystemd0 252.12-1~deb12u1 fixed in 252.39-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | libudev1 252.12-1~deb12u1 fixed in 252.39-1~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.2% 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.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42535 | MEDIUM6.5 | apache2 2.4.57-2 No fix yet | — | Directly Exposed |
| CVE-2026-42535 | MEDIUM6.5 | apache2-bin 2.4.57-2 No fix yet | — | Directly Exposed |
| CVE-2026-42535 | MEDIUM6.5 | apache2-data 2.4.57-2 No fix yet | — | Directly Exposed |
| CVE-2026-42535 | MEDIUM6.5 | apache2-utils 2.4.57-2 No fix yet | — | Directly Exposed |
| CVE-2026-5545 | MEDIUM6.5 | libcurl4 7.88.1-10+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2026-6429 | MEDIUM6.5 | libcurl4 7.88.1-10+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2023-6129 | MEDIUM6.5 | libssl-dev 3.0.9-1 fixed in 3.0.13-1~deb12u1 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6129 | MEDIUM6.5 | libssl3 3.0.9-1 fixed in 3.0.13-1~deb12u1 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | MEDIUM6.46 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-33599 | MEDIUM6.46 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-33636 | MEDIUM6.46 | libpng-dev 1.6.39-2 fixed in 1.6.39-2+deb12u4 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33636 | MEDIUM6.46 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+deb12u4 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31122 | MEDIUM6.38 | apache2 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-55753 | MEDIUM6.38 | apache2 2.4.57-2 fixed in 2.4.66-1~deb12u1 | <0.1% 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 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-49812 | MEDIUM6.38 | apache2 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-29168 | MEDIUM6.38 | apache2 2.4.57-2 fixed in 2.4.67-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33857 | MEDIUM6.38 | apache2 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-29169 | MEDIUM6.38 | apache2 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31122 | MEDIUM6.38 | apache2-bin 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-55753 | MEDIUM6.38 | apache2-bin 2.4.57-2 fixed in 2.4.66-1~deb12u1 | <0.1% 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 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-49812 | MEDIUM6.38 | apache2-bin 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-29168 | MEDIUM6.38 | apache2-bin 2.4.57-2 fixed in 2.4.67-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33857 | MEDIUM6.38 | apache2-bin 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-29169 | MEDIUM6.38 | apache2-bin 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31122 | MEDIUM6.38 | apache2-data 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-55753 | MEDIUM6.38 | apache2-data 2.4.57-2 fixed in 2.4.66-1~deb12u1 | <0.1% 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 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-49812 | MEDIUM6.38 | apache2-data 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-29168 | MEDIUM6.38 | apache2-data 2.4.57-2 fixed in 2.4.67-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33857 | MEDIUM6.38 | apache2-data 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-29169 | MEDIUM6.38 | apache2-data 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31122 | MEDIUM6.38 | apache2-utils 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-55753 | MEDIUM6.38 | apache2-utils 2.4.57-2 fixed in 2.4.66-1~deb12u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-47252 | MEDIUM6.38 | apache2-utils 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-23048 | MEDIUM6.38 | apache2-utils 2.4.57-2 fixed in 2.4.65-1~deb12u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-49812 | MEDIUM6.38 | apache2-utils 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-29168 | MEDIUM6.38 | apache2-utils 2.4.57-2 fixed in 2.4.67-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33857 | MEDIUM6.38 | apache2-utils 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-29169 | MEDIUM6.38 | apache2-utils 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-40684 | MEDIUM6.38 | exim4-base 4.96-15+deb12u1 fixed in 4.96-15+deb12u9 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40684 | MEDIUM6.38 | exim4-config 4.96-15+deb12u1 fixed in 4.96-15+deb12u9 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40684 | MEDIUM6.38 | exim4-daemon-light 4.96-15+deb12u1 fixed in 4.96-15+deb12u9 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-6779 | MEDIUM6.38 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2019-9192 | MEDIUM6.38 | libc-bin 2.36-9+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-6779 | MEDIUM6.38 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2019-9192 | MEDIUM6.38 | libc6 2.36-9+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-45490 | MEDIUM6.38 | libexpat1 2.5.0-1 fixed in 2.5.0-1+deb12u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-8176 | MEDIUM6.38 | libexpat1 2.5.0-1 fixed in 2.5.0-1+deb12u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-41989 | MEDIUM6.38 | libgcrypt20 1.10.1-3 fixed in 1.10.1-3+deb12u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-6829 | MEDIUM6.38 | libgcrypt20 1.10.1-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-0553 | MEDIUM6.38 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-33846 | MEDIUM6.38 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-0553 | MEDIUM6.38 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-33846 | MEDIUM6.38 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | libgssapi-krb5-2 1.20.1-2 fixed in 1.20.1-2+deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-36325 | MEDIUM6.38 | libjansson4 2.14-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | libk5crypto3 1.20.1-2 fixed in 1.20.1-2+deb12u2 | 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.5% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | libkrb5support0 1.20.1-2 fixed in 1.20.1-2+deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-31115 | MEDIUM6.38 | liblzma5 5.4.1-0.2 fixed in 5.4.1-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27135 | MEDIUM6.38 | libnghttp2-14 1.52.0-1 fixed in 1.52.0-1+deb12u3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33416 | MEDIUM6.38 | libpng-dev 1.6.39-2 fixed in 1.6.39-2+deb12u4 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33416 | MEDIUM6.38 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+deb12u4 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | libssl-dev 3.0.9-1 fixed in 3.0.18-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM6.38 | libssl-dev 3.0.9-1 fixed in 3.0.19-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM6.38 | libssl-dev 3.0.9-1 fixed in 3.0.19-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.38 | libssl-dev 3.0.9-1 fixed in 3.0.19-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | libssl3 3.0.9-1 fixed in 3.0.18-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM6.38 | libssl3 3.0.9-1 fixed in 3.0.19-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM6.38 | libssl3 3.0.9-1 fixed in 3.0.19-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.38 | libssl3 3.0.9-1 fixed in 3.0.19-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5994 | MEDIUM6.38 | libunbound8 1.17.1-2 fixed in 1.17.1-2+deb12u3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-25062 | MEDIUM6.38 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-27113 | MEDIUM6.38 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u2 | <0.1% 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.2% 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.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40476 | MEDIUM6.38 | webonyx/graphql-php v15.5.3 fixed in 15.31.5 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3833 | MEDIUM6.29 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3833 | MEDIUM6.29 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | libssl-dev 3.0.9-1 fixed in 3.0.18-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | libssl3 3.0.9-1 fixed in 3.0.18-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56406 | MEDIUM6.21 | libperl5.36 5.36.0-7 fixed in 5.36.0-7+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-7104 | MEDIUM6.21 | libsqlite3-0 3.40.1-2 fixed in 3.40.1-2+deb12u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-7104 | MEDIUM6.21 | libsqlite3-dev 3.40.1-2 fixed in 3.40.1-2+deb12u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-40725 | MEDIUM6.09 | apache2 2.4.57-2 fixed in 2.4.62-1~deb12u1 | 25.1% High Exploitation Risk | Directly Exposed |
| CVE-2024-40725 | MEDIUM6.09 | apache2-bin 2.4.57-2 fixed in 2.4.62-1~deb12u1 | 25.1% High Exploitation Risk | Directly Exposed |
| CVE-2024-40725 | MEDIUM6.09 | apache2-data 2.4.57-2 fixed in 2.4.62-1~deb12u1 | 25.1% High Exploitation Risk | Directly Exposed |
| CVE-2024-40725 | MEDIUM6.09 | apache2-utils 2.4.57-2 fixed in 2.4.62-1~deb12u1 | 25.1% High Exploitation Risk | Directly Exposed |
| CVE-2023-42114 | MEDIUM6.09 | exim4-base 4.96-15+deb12u1 fixed in 4.96-15+deb12u2 | 13.9% High Exploitation Risk | Directly Exposed |
| CVE-2023-42114 | MEDIUM6.09 | exim4-config 4.96-15+deb12u1 fixed in 4.96-15+deb12u2 | 13.9% High Exploitation Risk | Directly Exposed |
| CVE-2023-42114 | MEDIUM6.09 | exim4-daemon-light 4.96-15+deb12u1 fixed in 4.96-15+deb12u2 | 13.9% High Exploitation Risk | Directly Exposed |
| CVE-2024-28182 | MEDIUM6.09 | libnghttp2-14 1.52.0-1 fixed in 1.52.0-1+deb12u2 | 25.0% High Exploitation Risk | Directly Exposed |
| CVE-2023-4911 | MEDIUM6.08 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u3 | 67.2% Actively Exploited | Post-Exploit |
| CVE-2023-4911 | MEDIUM6.08 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u3 | 67.2% Actively Exploited | Post-Exploit |
| CVE-2024-1086 | MEDIUM6.08 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 85.3% Actively Exploited | Post-Exploit |
| CVE-2025-58098 | MEDIUM6.03 | apache2 2.4.57-2 fixed in 2.4.66-1~deb12u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-58098 | MEDIUM6.03 | apache2-bin 2.4.57-2 fixed in 2.4.66-1~deb12u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-58098 | MEDIUM6.03 | apache2-data 2.4.57-2 fixed in 2.4.66-1~deb12u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-58098 | MEDIUM6.03 | apache2-utils 2.4.57-2 fixed in 2.4.66-1~deb12u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-64720 | MEDIUM6.03 | libpng-dev 1.6.39-2 fixed in 1.6.39-2+deb12u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-65018 | MEDIUM6.03 | libpng-dev 1.6.39-2 fixed in 1.6.39-2+deb12u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66293 | MEDIUM6.03 | libpng-dev 1.6.39-2 fixed in 1.6.39-2+deb12u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22695 | MEDIUM6.03 | libpng-dev 1.6.39-2 fixed in 1.6.39-2+deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-64720 | MEDIUM6.03 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+deb12u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-65018 | MEDIUM6.03 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+deb12u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66293 | MEDIUM6.03 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+deb12u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22695 | MEDIUM6.03 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+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.1% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4878 | MEDIUM5.95 | libcap2 1:2.66-4 fixed in 1:2.66-4+deb12u3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5222 | MEDIUM5.95 | libicu72 72.1-3 fixed in 72.1-3+deb12u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-45802 | MEDIUM5.9 | apache2 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45802 | MEDIUM5.9 | apache2-bin 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45802 | MEDIUM5.9 | apache2-data 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45802 | MEDIUM5.9 | apache2-utils 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u3 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u3 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-11053 | MEDIUM5.9 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u10 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-50219 | MEDIUM5.9 | libexpat1 2.5.0-1 No fix yet | — | Directly Exposed |
| CVE-2024-5535 | MEDIUM5.9 | libssl-dev 3.0.9-1 fixed in 3.0.15-1~deb12u1 | 5.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.9 | libssl-dev 3.0.9-1 fixed in 3.0.20-1~deb12u2 | — | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.9 | libssl-dev 3.0.9-1 fixed in 3.0.20-1~deb12u2 | — | Directly Exposed |
| CVE-2024-5535 | MEDIUM5.9 | libssl3 3.0.9-1 fixed in 3.0.15-1~deb12u1 | 5.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.9 | libssl3 3.0.9-1 fixed in 3.0.20-1~deb12u2 | — | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.9 | libssl3 3.0.9-1 fixed in 3.0.20-1~deb12u2 | — | Directly Exposed |
| CVE-2026-44608 | MEDIUM5.9 | libunbound8 1.17.1-2 No fix yet | — | Directly Exposed |
| CVE-2026-8376 | MEDIUM5.88 | perl 5.36.0-7 No fix yet | — | Post-Exploit |
| CVE-2026-8376 | MEDIUM5.88 | perl-base 5.36.0-7 No fix yet | — | Post-Exploit |
| CVE-2026-8376 | MEDIUM5.88 | perl-modules-5.36 5.36.0-7 No fix yet | — | Post-Exploit |
| CVE-2025-6965 | MEDIUM5.88 | sqlite3 3.40.1-2 fixed in 3.40.1-2+deb12u2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-13410 | MEDIUM5.88 | zip 3.0-13 No fix yet | 7.9% Low-Moderate Risk | Post-Exploit |
| CVE-2024-42516 | MEDIUM5.78 | apache2 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-42516 | MEDIUM5.78 | apache2-bin 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-42516 | MEDIUM5.78 | apache2-data 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-42516 | MEDIUM5.78 | apache2-utils 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-1965 | MEDIUM5.78 | libcurl4 7.88.1-10+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14819 | MEDIUM5.78 | libcurl4 7.88.1-10+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | libsystemd0 252.12-1~deb12u1 fixed in 252.39-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | libudev1 252.12-1~deb12u1 fixed in 252.39-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-65082 | MEDIUM5.52 | apache2 2.4.57-2 fixed in 2.4.66-1~deb12u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33523 | MEDIUM5.52 | apache2 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-65082 | MEDIUM5.52 | apache2-bin 2.4.57-2 fixed in 2.4.66-1~deb12u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33523 | MEDIUM5.52 | apache2-bin 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-65082 | MEDIUM5.52 | apache2-data 2.4.57-2 fixed in 2.4.66-1~deb12u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33523 | MEDIUM5.52 | apache2-data 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-65082 | MEDIUM5.52 | apache2-utils 2.4.57-2 fixed in 2.4.66-1~deb12u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33523 | MEDIUM5.52 | apache2-utils 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | MEDIUM5.52 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-4527 | MEDIUM5.52 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u3 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.36-9+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-4527 | MEDIUM5.52 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u3 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.36-9+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | MEDIUM5.52 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | MEDIUM5.52 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-46218 | MEDIUM5.52 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-7264 | MEDIUM5.52 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u7 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-8096 | MEDIUM5.52 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-9681 | MEDIUM5.52 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u9 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-3784 | MEDIUM5.52 | libcurl4 7.88.1-10+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14524 | MEDIUM5.52 | libcurl4 7.88.1-10+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6395 | MEDIUM5.52 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6395 | MEDIUM5.52 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | MEDIUM5.52 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-36054 | MEDIUM5.52 | libgssapi-krb5-2 1.20.1-2 fixed in 1.20.1-2+deb12u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libgssapi-krb5-2 1.20.1-2 fixed in 1.20.1-2+deb12u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-36054 | MEDIUM5.52 | libk5crypto3 1.20.1-2 fixed in 1.20.1-2+deb12u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libk5crypto3 1.20.1-2 fixed in 1.20.1-2+deb12u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-36054 | MEDIUM5.52 | libkrb5-3 1.20.1-2 fixed in 1.20.1-2+deb12u1 | 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.2% Theoretical Threat | Directly Exposed |
| CVE-2023-36054 | MEDIUM5.52 | libkrb5support0 1.20.1-2 fixed in 1.20.1-2+deb12u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libkrb5support0 1.20.1-2 fixed in 1.20.1-2+deb12u3 | 0.2% 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.1% 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.1% Theoretical Threat | Directly Exposed |
| CVE-2026-44119 | MEDIUM5.5 | apache2 2.4.57-2 No fix yet | — | Directly Exposed |
| CVE-2026-44119 | MEDIUM5.5 | apache2-bin 2.4.57-2 No fix yet | — | Directly Exposed |
| CVE-2026-44119 | MEDIUM5.5 | apache2-data 2.4.57-2 No fix yet | — | Directly Exposed |
| CVE-2026-44119 | MEDIUM5.5 | apache2-utils 2.4.57-2 No fix yet | — | Directly Exposed |
| CVE-2026-7383 | MEDIUM5.5 | libssl-dev 3.0.9-1 fixed in 3.0.20-1~deb12u2 | — | Directly Exposed |
| CVE-2026-7383 | MEDIUM5.5 | libssl3 3.0.9-1 fixed in 3.0.20-1~deb12u2 | — | Directly Exposed |
| CVE-2024-34459 | MEDIUM5.5 | libxml2 2.9.14+dfsg-1.3~deb12u1 fixed in 2.9.14+dfsg-1.3~deb12u2 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45445 | MEDIUM5.46 | openssl 3.0.9-1 fixed in 3.0.20-1~deb12u2 | — | Post-Exploit |
| CVE-2026-42496 | MEDIUM5.46 | perl 5.36.0-7 No fix yet | — | Post-Exploit |
| CVE-2026-42496 | MEDIUM5.46 | perl-base 5.36.0-7 No fix yet | — | Post-Exploit |
| CVE-2026-42496 | MEDIUM5.46 | perl-modules-5.36 5.36.0-7 No fix yet | — | Post-Exploit |
| CVE-2026-40225 | MEDIUM5.44 | libsystemd0 252.12-1~deb12u1 fixed in 252.39-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | MEDIUM5.44 | libsystemd0 252.12-1~deb12u1 fixed in 252.39-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40225 | MEDIUM5.44 | libudev1 252.12-1~deb12u1 fixed in 252.39-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | MEDIUM5.44 | libudev1 252.12-1~deb12u1 fixed in 252.39-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-29170 | MEDIUM5.4 | apache2 2.4.57-2 No fix yet | — | Directly Exposed |
| CVE-2026-29170 | MEDIUM5.4 | apache2-bin 2.4.57-2 No fix yet | — | Directly Exposed |
| CVE-2026-29170 | MEDIUM5.4 | apache2-data 2.4.57-2 No fix yet | — | Directly Exposed |
| CVE-2026-29170 | MEDIUM5.4 | apache2-utils 2.4.57-2 No fix yet | — | Directly Exposed |
| CVE-2023-6246 | MEDIUM5.38 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u4 | 25.5% High Exploitation Risk | Post-Exploit |
| CVE-2023-6246 | MEDIUM5.38 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u4 | 25.5% High Exploitation Risk | Post-Exploit |
| CVE-2024-53104 | MEDIUM5.38 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 14.4% High Exploitation Risk | Post-Exploit |
| CVE-2025-53020 | MEDIUM5.3 | apache2 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-53020 | MEDIUM5.3 | apache2-bin 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-53020 | MEDIUM5.3 | apache2-data 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-53020 | MEDIUM5.3 | apache2-utils 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-51766 | MEDIUM5.3 | exim4-base 4.96-15+deb12u1 fixed in 4.96-15+deb12u4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-51766 | MEDIUM5.3 | exim4-config 4.96-15+deb12u1 fixed in 4.96-15+deb12u4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-51766 | MEDIUM5.3 | exim4-daemon-light 4.96-15+deb12u1 fixed in 4.96-15+deb12u4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-4873 | MEDIUM5.3 | libcurl4 7.88.1-10+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2026-6253 | MEDIUM5.3 | libcurl4 7.88.1-10+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2026-7168 | MEDIUM5.3 | libcurl4 7.88.1-10+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2024-12243 | MEDIUM5.3 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u4 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28834 | MEDIUM5.3 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u3 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42015 | MEDIUM5.3 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u7 | — | Directly Exposed |
| CVE-2024-12243 | MEDIUM5.3 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u4 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28834 | MEDIUM5.3 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u3 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42015 | MEDIUM5.3 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | — | Directly Exposed |
| CVE-2026-42766 | MEDIUM5.3 | libssl-dev 3.0.9-1 fixed in 3.0.20-1~deb12u2 | — | Directly Exposed |
| CVE-2026-42767 | MEDIUM5.3 | libssl-dev 3.0.9-1 No fix yet | — | Directly Exposed |
| CVE-2026-42766 | MEDIUM5.3 | libssl3 3.0.9-1 fixed in 3.0.20-1~deb12u2 | — | Directly Exposed |
| CVE-2026-42767 | MEDIUM5.3 | libssl3 3.0.9-1 No fix yet | — | Directly Exposed |
| CVE-2026-42534 | MEDIUM5.3 | libunbound8 1.17.1-2 No fix yet | — | Directly Exposed |
| CVE-2026-42923 | MEDIUM5.3 | libunbound8 1.17.1-2 No fix yet | — | Directly Exposed |
| CVE-2026-44390 | MEDIUM5.3 | libunbound8 1.17.1-2 No fix yet | — | Directly Exposed |
| CVE-2026-32792 | MEDIUM5.3 | libunbound8 1.17.1-2 No fix yet | — | Directly Exposed |
| CVE-2026-48998 | MEDIUM5.3 | guzzlehttp/psr7 2.5.0 fixed in 2.10.2 | — | Directly Exposed |
| CVE-2023-5178 | MEDIUM5.28 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 8.6% Low-Moderate Risk | Post-Exploit |
| CVE-2024-8805 | MEDIUM5.28 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 2.6% Low-Moderate Risk | Post-Exploit |
| 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 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid1 2.38.1-5+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1390 | MEDIUM5.18 | libcap2 1:2.66-4 fixed in 1:2.66-4+deb12u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount1 2.38.1-5+b1 No fix yet | <0.1% 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.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11411 | MEDIUM5.18 | libunbound8 1.17.1-2 fixed in 1.17.1-2+deb12u4 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid1 2.38.1-5+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-38039 | MEDIUM5.17 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u3 | 12.3% High Exploitation Risk | Post-Exploit |
| CVE-2018-6951 | MEDIUM5.17 | patch 2.7.6-7 No fix yet | 15.3% High Exploitation Risk | Post-Exploit |
| CVE-2018-6952 | MEDIUM5.17 | patch 2.7.6-7 No fix yet | 11.8% High Exploitation Risk | Post-Exploit |
| CVE-2024-28085 | MEDIUM5.06 | libblkid1 2.38.1-5+b1 fixed in 2.38.1-5+deb12u1 | 10.2% High Exploitation Risk | Directly Exposed |
| CVE-2024-28085 | MEDIUM5.06 | libmount1 2.38.1-5+b1 fixed in 2.38.1-5+deb12u1 | 10.2% High Exploitation Risk | Directly Exposed |
| CVE-2024-28085 | MEDIUM5.06 | libsmartcols1 2.38.1-5+b1 fixed in 2.38.1-5+deb12u1 | 10.2% High Exploitation Risk | Directly Exposed |
| CVE-2024-28085 | MEDIUM5.06 | libuuid1 2.38.1-5+b1 fixed in 2.38.1-5+deb12u1 | 10.2% High Exploitation Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.02 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.36-9+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.36-9+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.02 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.02 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-10966 | MEDIUM5.02 | libcurl4 7.88.1-10+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-50602 | MEDIUM5.02 | libexpat1 2.5.0-1 fixed in 2.5.0-1+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.02 | libgcrypt20 1.10.1-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-5981 | MEDIUM5.02 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-5981 | MEDIUM5.02 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.02 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libgssapi-krb5-2 1.20.1-2 fixed in 1.20.1-2+deb12u4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM5.02 | libgssapi-krb5-2 1.20.1-2 fixed in 1.20.1-2+deb12u5 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libgssapi-krb5-2 1.20.1-2 fixed in 1.20.1-2+deb12u5 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssapi-krb5-2 1.20.1-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.02 | libgssapi-krb5-2 1.20.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libk5crypto3 1.20.1-2 fixed in 1.20.1-2+deb12u4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM5.02 | libk5crypto3 1.20.1-2 fixed in 1.20.1-2+deb12u5 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libk5crypto3 1.20.1-2 fixed in 1.20.1-2+deb12u5 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libk5crypto3 1.20.1-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.02 | libk5crypto3 1.20.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libkrb5-3 1.20.1-2 fixed in 1.20.1-2+deb12u4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM5.02 | libkrb5-3 1.20.1-2 fixed in 1.20.1-2+deb12u5 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libkrb5-3 1.20.1-2 fixed in 1.20.1-2+deb12u5 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-3 1.20.1-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.02 | libkrb5-3 1.20.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libkrb5support0 1.20.1-2 fixed in 1.20.1-2+deb12u4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM5.02 | libkrb5support0 1.20.1-2 fixed in 1.20.1-2+deb12u5 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libkrb5support0 1.20.1-2 fixed in 1.20.1-2+deb12u5 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5support0 1.20.1-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.02 | libkrb5support0 1.20.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40909 | MEDIUM5.02 | libperl5.36 5.36.0-7 fixed in 5.36.0-7+deb12u3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.02 | libssl-dev 3.0.9-1 fixed in 3.0.19-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-6237 | MEDIUM5.02 | libssl-dev 3.0.9-1 fixed in 3.0.13-1~deb12u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | libssl-dev 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | libssl-dev 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.02 | libssl3 3.0.9-1 fixed in 3.0.19-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-6237 | MEDIUM5.02 | libssl3 3.0.9-1 fixed in 3.0.13-1~deb12u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | libssl3 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | libssl3 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-7008 | MEDIUM5.02 | libsystemd0 252.12-1~deb12u1 fixed in 252.21-1~deb12u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.02 | libtasn1-6 4.19.0-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-7008 | MEDIUM5.02 | libudev1 252.12-1~deb12u1 fixed in 252.21-1~deb12u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0990 | MEDIUM5.02 | libxml2 2.9.14+dfsg-1.3~deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-1010022 | MEDIUM5 | libc-dev-bin 2.36-9+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-1010022 | MEDIUM5 | libc6-dev 2.36-9+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-25775 | MEDIUM5 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-23112 | MEDIUM5 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31789 | MEDIUM5 | openssl 3.0.9-1 fixed in 3.0.19-1~deb12u2 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15467 | MEDIUM5 | openssl 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-42250 | MEDIUM5 | libbz2-1.0 1.0.8-5+b1 No fix yet | — | Directly Exposed |
| CVE-2026-11850 | MEDIUM5 | libgssapi-krb5-2 1.20.1-2 No fix yet | — | Directly Exposed |
| CVE-2026-11850 | MEDIUM5 | libk5crypto3 1.20.1-2 No fix yet | — | Directly Exposed |
| CVE-2026-11850 | MEDIUM5 | libkrb5-3 1.20.1-2 No fix yet | — | Directly Exposed |
| CVE-2026-11850 | MEDIUM5 | libkrb5support0 1.20.1-2 No fix yet | — | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | libssl-dev 3.0.9-1 fixed in 3.0.20-1~deb12u2 | — | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | libssl3 3.0.9-1 fixed in 3.0.20-1~deb12u2 | — | Directly Exposed |
| CVE-2026-45447 | MEDIUM4.86 | openssl 3.0.9-1 fixed in 3.0.20-1~deb12u2 | — | Post-Exploit |
| CVE-2023-31484 | MEDIUM4.86 | perl 5.36.0-7 fixed in 5.36.0-7+deb12u3 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31484 | MEDIUM4.86 | perl-base 5.36.0-7 fixed in 5.36.0-7+deb12u3 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31484 | MEDIUM4.86 | perl-modules-5.36 5.36.0-7 fixed in 5.36.0-7+deb12u3 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3783 | MEDIUM4.84 | libcurl4 7.88.1-10+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-39929 | MEDIUM4.81 | exim4-base 4.96-15+deb12u1 fixed in 4.96-15+deb12u5 | 60.3% Actively Exploited | Directly Exposed |
| CVE-2024-39929 | MEDIUM4.81 | exim4-config 4.96-15+deb12u1 fixed in 4.96-15+deb12u5 | 60.3% Actively Exploited | Directly Exposed |
| CVE-2024-39929 | MEDIUM4.81 | exim4-daemon-light 4.96-15+deb12u1 fixed in 4.96-15+deb12u5 | 60.3% Actively Exploited | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-9230 | MEDIUM4.76 | libssl-dev 3.0.9-1 fixed in 3.0.17-1~deb12u3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-4741 | MEDIUM4.76 | libssl-dev 3.0.9-1 fixed in 3.0.14-1~deb12u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-9230 | MEDIUM4.76 | libssl3 3.0.9-1 fixed in 3.0.17-1~deb12u3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-4741 | MEDIUM4.76 | libssl3 3.0.9-1 fixed in 3.0.14-1~deb12u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2013-7445 | MEDIUM4.68 | linux-libc-dev 6.1.38-1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-31431 | MEDIUM4.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-43128 | MEDIUM4.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43150 | MEDIUM4.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43196 | MEDIUM4.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43205 | MEDIUM4.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43250 | MEDIUM4.68 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43284 | MEDIUM4.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-3 | — | Post-Exploit |
| CVE-2026-43328 | MEDIUM4.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43378 | MEDIUM4.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43426 | MEDIUM4.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43458 | MEDIUM4.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43500 | MEDIUM4.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-3 | — | Post-Exploit |
| CVE-2026-46163 | MEDIUM4.68 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46180 | MEDIUM4.68 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46189 | MEDIUM4.68 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46219 | MEDIUM4.68 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46234 | MEDIUM4.68 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46241 | MEDIUM4.68 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46243 | MEDIUM4.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.174-1 | — | Post-Exploit |
| CVE-2026-46267 | MEDIUM4.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-46300 | MEDIUM4.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.174-1 | — | Post-Exploit |
| CVE-2026-46323 | MEDIUM4.68 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46333 | MEDIUM4.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.172-1 | — | Post-Exploit |
| CVE-2026-46274 | MEDIUM4.68 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-48962 | MEDIUM4.68 | perl 5.36.0-7 No fix yet | — | Post-Exploit |
| CVE-2026-48962 | MEDIUM4.68 | perl-base 5.36.0-7 No fix yet | — | Post-Exploit |
| CVE-2026-48962 | MEDIUM4.68 | perl-modules-5.36 5.36.0-7 No fix yet | — | Post-Exploit |
| CVE-2026-24072 | MEDIUM4.67 | apache2 2.4.57-2 fixed in 2.4.67-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-24072 | MEDIUM4.67 | apache2-bin 2.4.57-2 fixed in 2.4.67-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-24072 | MEDIUM4.67 | apache2-data 2.4.57-2 fixed in 2.4.67-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-24072 | MEDIUM4.67 | apache2-utils 2.4.57-2 fixed in 2.4.67-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-49582 | MEDIUM4.67 | libapr1 1.7.2-3 fixed in 1.7.2-3+deb12u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libasan8 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libatomic1 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-20673 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-9996 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libblkid1 2.38.1-5+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u10 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u10 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libcc1-0 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-20673 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-9996 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-20673 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-9996 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1 2.5.0-1 No fix yet | <0.1% 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.1% 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.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc-s1 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgomp1 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-20673 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-9996 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26462 | MEDIUM4.67 | libgssapi-krb5-2 1.20.1-2 fixed in 1.20.1-2+deb12u3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libitm1 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26462 | MEDIUM4.67 | libk5crypto3 1.20.1-2 fixed in 1.20.1-2+deb12u3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26462 | MEDIUM4.67 | libkrb5-3 1.20.1-2 fixed in 1.20.1-2+deb12u3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26462 | MEDIUM4.67 | libkrb5support0 1.20.1-2 fixed in 1.20.1-2+deb12u3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | liblsan0 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount1 2.38.1-5+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | MEDIUM4.67 | libpng-dev 1.6.39-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | MEDIUM4.67 | libpng16-16 1.6.39-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libquadmath0 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libsmartcols1 2.38.1-5+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-29088 | MEDIUM4.67 | libsqlite3-0 3.40.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-29088 | MEDIUM4.67 | libsqlite3-dev 3.40.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-0727 | MEDIUM4.67 | libssl-dev 3.0.9-1 fixed in 3.0.13-1~deb12u1 | 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-2024-0727 | MEDIUM4.67 | libssl3 3.0.9-1 fixed in 3.0.13-1~deb12u1 | 0.2% 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-2022-27943 | MEDIUM4.67 | libstdc++6 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libtsan2 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libubsan1 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.38.1-5+b1 No fix yet | <0.1% 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-2026-27171 | MEDIUM4.67 | zlib1g 1:1.2.13.dfsg-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g-dev 1:1.2.13.dfsg-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-47685 | MEDIUM4.64 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-7458 | MEDIUM4.64 | sqlite3 3.40.1-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38428 | MEDIUM4.64 | wget 1.21.3-1+b2 fixed in 1.21.3-1+deb12u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43204 | MEDIUM4.59 | apache2 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-66200 | MEDIUM4.59 | apache2 2.4.57-2 fixed in 2.4.66-1~deb12u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-43204 | MEDIUM4.59 | apache2-bin 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-66200 | MEDIUM4.59 | apache2-bin 2.4.57-2 fixed in 2.4.66-1~deb12u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-43204 | MEDIUM4.59 | apache2-data 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-66200 | MEDIUM4.59 | apache2-data 2.4.57-2 fixed in 2.4.66-1~deb12u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-43204 | MEDIUM4.59 | apache2-utils 2.4.57-2 fixed in 2.4.65-1~deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-66200 | MEDIUM4.59 | apache2-utils 2.4.57-2 fixed in 2.4.66-1~deb12u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-2379 | MEDIUM4.59 | libcurl4 7.88.1-10+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-42115 | MEDIUM4.58 | exim4-base 4.96-15+deb12u1 fixed in 4.96-15+deb12u2 | 70.7% Actively Exploited | Post-Exploit |
| CVE-2023-42115 | MEDIUM4.58 | exim4-config 4.96-15+deb12u1 fixed in 4.96-15+deb12u2 | 70.7% Actively Exploited | Post-Exploit |
| CVE-2023-42115 | MEDIUM4.58 | exim4-daemon-light 4.96-15+deb12u1 fixed in 4.96-15+deb12u2 | 70.7% Actively Exploited | Post-Exploit |
| CVE-2026-5773 | MEDIUM4.5 | curl 7.88.1-10+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2026-6276 | MEDIUM4.5 | curl 7.88.1-10+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2024-2398 | MEDIUM4.5 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u6 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20796 | MEDIUM4.5 | libc-dev-bin 2.36-9+deb12u1 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20796 | MEDIUM4.5 | libc6-dev 2.36-9+deb12u1 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-43501 | MEDIUM4.5 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43186 | MEDIUM4.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43190 | MEDIUM4.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2008-1687 | MEDIUM4.5 | m4 1.4.19-3 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2008-1688 | MEDIUM4.5 | m4 1.4.19-3 No fix yet | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5363 | MEDIUM4.5 | openssl 3.0.9-1 fixed in 3.0.11-1~deb12u2 | 4.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-6119 | MEDIUM4.5 | openssl 3.0.9-1 fixed in 3.0.14-1~deb12u2 | 6.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42497 | MEDIUM4.5 | perl 5.36.0-7 No fix yet | — | Post-Exploit |
| CVE-2026-9538 | MEDIUM4.5 | perl 5.36.0-7 No fix yet | — | Post-Exploit |
| CVE-2026-42497 | MEDIUM4.5 | perl-base 5.36.0-7 No fix yet | — | Post-Exploit |
| CVE-2026-9538 | MEDIUM4.5 | perl-base 5.36.0-7 No fix yet | — | Post-Exploit |
| CVE-2026-42497 | MEDIUM4.5 | perl-modules-5.36 5.36.0-7 No fix yet | — | Post-Exploit |
| CVE-2026-9538 | MEDIUM4.5 | perl-modules-5.36 5.36.0-7 No fix yet | — | Post-Exploit |
| CVE-2026-33007 | MEDIUM4.5 | apache2 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-33007 | MEDIUM4.5 | apache2-bin 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-33007 | MEDIUM4.5 | apache2-data 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-33007 | MEDIUM4.5 | apache2-utils 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-40686 | MEDIUM4.5 | exim4-base 4.96-15+deb12u1 fixed in 4.96-15+deb12u9 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40686 | MEDIUM4.5 | exim4-config 4.96-15+deb12u1 fixed in 4.96-15+deb12u9 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40686 | MEDIUM4.5 | exim4-daemon-light 4.96-15+deb12u1 fixed in 4.96-15+deb12u9 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid1 2.38.1-5+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-6780 | MEDIUM4.5 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-33600 | MEDIUM4.5 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM4.5 | libc-bin 2.36-9+deb12u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-1010025 | MEDIUM4.5 | libc-bin 2.36-9+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-6780 | MEDIUM4.5 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-33600 | MEDIUM4.5 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM4.5 | libc6 2.36-9+deb12u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-1010025 | MEDIUM4.5 | libc6 2.36-9+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-46219 | MEDIUM4.5 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-2004 | MEDIUM4.5 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-59375 | MEDIUM4.5 | libexpat1 2.5.0-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14831 | MEDIUM4.5 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u6 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-32989 | MEDIUM4.5 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-14831 | MEDIUM4.5 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u6 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-32989 | MEDIUM4.5 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | liblzma5 5.4.1-0.2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount1 2.38.1-5+b1 No fix yet | <0.1% 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-3184 | MEDIUM4.5 | libsmartcols1 2.38.1-5+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-2975 | MEDIUM4.5 | libssl-dev 3.0.9-1 fixed in 3.0.10-1~deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-3446 | MEDIUM4.5 | libssl-dev 3.0.9-1 fixed in 3.0.10-1~deb12u1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-3817 | MEDIUM4.5 | libssl-dev 3.0.9-1 fixed in 3.0.10-1~deb12u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-5678 | MEDIUM4.5 | libssl-dev 3.0.9-1 fixed in 3.0.13-1~deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-4603 | MEDIUM4.5 | libssl-dev 3.0.9-1 fixed in 3.0.14-1~deb12u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-2975 | MEDIUM4.5 | libssl3 3.0.9-1 fixed in 3.0.10-1~deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-3446 | MEDIUM4.5 | libssl3 3.0.9-1 fixed in 3.0.10-1~deb12u1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-3817 | MEDIUM4.5 | libssl3 3.0.9-1 fixed in 3.0.10-1~deb12u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-5678 | MEDIUM4.5 | libssl3 3.0.9-1 fixed in 3.0.13-1~deb12u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-4603 | MEDIUM4.5 | libssl3 3.0.9-1 fixed in 3.0.14-1~deb12u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 252.12-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 252.12-1~deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 252.12-1~deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-12133 | MEDIUM4.5 | libtasn1-6 4.19.0-2 fixed in 4.19.0-2+deb12u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libudev1 252.12-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libudev1 252.12-1~deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libudev1 252.12-1~deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-8508 | MEDIUM4.5 | libunbound8 1.17.1-2 fixed in 1.17.1-2+deb12u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.38.1-5+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-1010023 | MEDIUM4.49 | libc-dev-bin 2.36-9+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2019-1010023 | MEDIUM4.49 | libc6-dev 2.36-9+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43037 | MEDIUM4.49 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-25744 | MEDIUM4.49 | linux-libc-dev 6.1.38-1 fixed in 6.1.69-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47659 | MEDIUM4.49 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-23395 | MEDIUM4.49 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | MEDIUM4.44 | openssl 3.0.9-1 fixed in 3.0.20-1~deb12u2 | — | Post-Exploit |
| CVE-2026-43248 | MEDIUM4.38 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2003-1307 | MEDIUM4.3 | apache2 2.4.57-2 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1580 | MEDIUM4.3 | apache2 2.4.57-2 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1307 | MEDIUM4.3 | apache2-bin 2.4.57-2 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1580 | MEDIUM4.3 | apache2-bin 2.4.57-2 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1307 | MEDIUM4.3 | apache2-data 2.4.57-2 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1580 | MEDIUM4.3 | apache2-data 2.4.57-2 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1307 | MEDIUM4.3 | apache2-utils 2.4.57-2 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1580 | MEDIUM4.3 | apache2-utils 2.4.57-2 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2011-3389 | MEDIUM4.3 | libgnutls-dane0 3.7.9-2 No fix yet | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2011-3389 | MEDIUM4.3 | libgnutls30 3.7.9-2 No fix yet | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-53150 | MEDIUM4.26 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-43141 | MEDIUM4.26 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43241 | MEDIUM4.26 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43281 | MEDIUM4.26 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43380 | MEDIUM4.26 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43386 | MEDIUM4.26 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43427 | MEDIUM4.26 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43449 | MEDIUM4.26 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43450 | MEDIUM4.26 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43453 | MEDIUM4.26 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-46191 | MEDIUM4.26 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43126 | MEDIUM4.26 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43414 | MEDIUM4.26 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46056 | MEDIUM4.26 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46120 | MEDIUM4.26 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46135 | MEDIUM4.26 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46150 | MEDIUM4.26 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46209 | MEDIUM4.26 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46259 | MEDIUM4.26 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2008-4609 | MEDIUM4.26 | linux-libc-dev 6.1.38-1 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2024-57360 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.36-9+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.36-9+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.36-9+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.36-9+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-28835 | MEDIUM4.25 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-28835 | MEDIUM4.25 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-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-43125 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43198 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43329 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43494 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43503 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 fixed in 6.1.174-1 | — | Post-Exploit |
| CVE-2026-45852 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45858 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45972 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45984 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45991 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46033 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46053 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46054 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46090 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46099 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46116 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46125 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46181 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46195 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46227 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46319 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46330 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2025-40271 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-43158 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43226 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43233 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43303 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43304 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43334 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43339 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43341 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43491 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43493 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45840 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45856 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45859 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45860 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45886 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45892 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45894 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45899 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45912 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45934 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45942 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45962 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45970 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45983 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45985 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46004 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46015 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46017 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46021 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46023 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46028 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-46032 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46043 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46047 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46052 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46069 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46119 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46123 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46132 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46133 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46149 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46173 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46174 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 fixed in 6.1.174-1 | — | Post-Exploit |
| CVE-2026-46185 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46251 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-46266 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46275 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46294 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46306 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46324 | MEDIUM4.2 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-31788 | MEDIUM4.18 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-39191 | MEDIUM4.18 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2007-3303 | MEDIUM4.17 | apache2 2.4.57-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2007-3303 | MEDIUM4.17 | apache2-bin 2.4.57-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2007-3303 | MEDIUM4.17 | apache2-data 2.4.57-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2007-3303 | MEDIUM4.17 | apache2-utils 2.4.57-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | MEDIUM4.13 | curl 7.88.1-10+deb12u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0861 | MEDIUM4.13 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0861 | MEDIUM4.13 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-25646 | MEDIUM4.13 | libpng-tools 1.6.39-2 fixed in 1.6.39-2+deb12u3 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58087 | MEDIUM4.13 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-28387 | MEDIUM4.13 | openssl 3.0.9-1 fixed in 3.0.19-1~deb12u2 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-31486 | MEDIUM4.13 | perl 5.36.0-7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-31486 | MEDIUM4.13 | perl-base 5.36.0-7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-31486 | MEDIUM4.13 | perl-modules-5.36 5.36.0-7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-2961 | MEDIUM4.12 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u6 | 91.9% Actively Exploited | Post-Exploit |
| CVE-2024-2961 | MEDIUM4.12 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u6 | 91.9% Actively Exploited | Post-Exploit |
| CVE-2026-44631 | MEDIUM4.1 | apache2 2.4.57-2 No fix yet | — | Directly Exposed |
| CVE-2026-44631 | MEDIUM4.1 | apache2-bin 2.4.57-2 No fix yet | — | Directly Exposed |
| CVE-2026-44631 | MEDIUM4.1 | apache2-data 2.4.57-2 No fix yet | — | Directly Exposed |
| CVE-2026-44631 | MEDIUM4.1 | apache2-utils 2.4.57-2 No fix yet | — | Directly Exposed |
| CVE-2023-52434 | MEDIUM4.08 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-33006 | MEDIUM4.08 | apache2 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33006 | MEDIUM4.08 | apache2-bin 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33006 | MEDIUM4.08 | apache2-data 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33006 | MEDIUM4.08 | apache2-utils 2.4.57-2 fixed in 2.4.67-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libasan8 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libatomic1 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libcc1-0 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-10148 | MEDIUM4.08 | libcurl4 7.88.1-10+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14017 | MEDIUM4.08 | libcurl4 7.88.1-10+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libgcc-s1 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libgomp1 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libitm1 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | liblsan0 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libquadmath0 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libstdc++6 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libtsan2 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libubsan1 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43168 | MEDIUM4.08 | libunbound8 1.17.1-2 fixed in 1.17.1-2+deb12u3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-38545 | MEDIUM4.06 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u4 | 26.3% High Exploitation Risk | Post-Exploit |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.38.1-5+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15224 | MEDIUM4 | libcurl4 7.88.1-10+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | MEDIUM4 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount1 2.38.1-5+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.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4 | libssl-dev 3.0.9-1 fixed in 3.0.18-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | libssl3 3.0.9-1 fixed in 3.0.16-1~deb12u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4 | libssl3 3.0.9-1 fixed in 3.0.18-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-4598 | MEDIUM4 | libsystemd0 252.12-1~deb12u1 fixed in 252.38-1~deb12u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-4598 | MEDIUM4 | libudev1 252.12-1~deb12u1 fixed in 252.38-1~deb12u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.38.1-5+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-24795 | MEDIUM4 | apache2 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-24795 | MEDIUM4 | apache2-bin 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-24795 | MEDIUM4 | apache2-data 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-24795 | MEDIUM4 | apache2-utils 2.4.57-2 fixed in 2.4.59-1~deb12u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-11082 | LOW3.98 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22801 | LOW3.98 | libpng-tools 1.6.39-2 fixed in 1.6.39-2+deb12u2 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-19449 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2019-19814 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2021-3847 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-2176 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-34319 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-3611 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-3776 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-3777 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-4004 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-4015 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-40283 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-4147 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-4206 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-4207 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-4208 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-42753 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-4623 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-4921 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-51042 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52436 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52438 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52439 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52440 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-52441 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52444 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52445 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52451 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52452 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52457 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52464 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52469 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52475 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52482 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52483 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52491 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52494 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52509 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52510 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52515 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52524 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52530 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52531 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52572 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52594 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52599 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52600 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52603 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52604 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52612 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52614 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52621 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52624 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52637 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52642 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52664 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52667 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52669 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52679 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52691 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52748 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52751 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52752 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52755 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-52757 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52764 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52772 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52775 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.66-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52777 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52795 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52796 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52799 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52804 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52805 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52807 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52812 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52816 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52818 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52835 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52836 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52837 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52840 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52846 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52851 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52852 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52854 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52859 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52864 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52867 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52868 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52885 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52916 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52922 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52927 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53145 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53148 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53179 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53184 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53187 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53192 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53194 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53205 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53215 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53218 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53252 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53257 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53263 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53286 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53305 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53311 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53316 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53322 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53331 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53338 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53363 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53377 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53386 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53395 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53426 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53432 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53446 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-5345 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53454 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53479 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53485 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53487 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53492 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53495 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53500 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53508 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53510 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53515 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53541 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53543 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53552 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53554 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53556 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53559 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53560 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53570 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53572 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53577 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53596 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53613 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53616 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53619 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53652 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53673 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53676 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54207 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54285 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-5633 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-5717 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-6111 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-6817 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.69-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-0646 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.69-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-0841 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-1085 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-21803 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-22705 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-23307 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26581 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-26582 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26588 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26589 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26592 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26598 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26599 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26610 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26622 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26625 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26689 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26704 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26736 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26739 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26742 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26748 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26749 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26753 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26754 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26782 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26793 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26800 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26836 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26856 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26865 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26882 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26883 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26884 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26885 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26895 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26898 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26907 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26913 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26914 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26928 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26933 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26934 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26936 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26944 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26951 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26952 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26955 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26956 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26957 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26958 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26961 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26965 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26981 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26983 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26988 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26989 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26996 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27000 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27008 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27018 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27022 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27024 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27043 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27045 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27065 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27075 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27395 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27396 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27398 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-35789 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35791 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35847 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35855 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35861 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35862 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35863 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35864 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35866 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35867 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35868 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35886 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35887 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35905 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35932 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36012 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36015 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36880 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36886 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-36898 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36904 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-36906 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36914 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36934 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36940 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36971 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-36973 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36974 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36978 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36979 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38545 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38552 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38555 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38556 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38568 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38569 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38570 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38577 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38578 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38581 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38583 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38586 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38588 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38610 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38627 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38630 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38667 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39277 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39463 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39480 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39494 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39495 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39496 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39502 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39510 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40899 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40900 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40901 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40902 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40903 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40906 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40913 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40920 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40927 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40935 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40939 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40940 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40954 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40956 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40958 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40974 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40989 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40994 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40996 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41000 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41011 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41028 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41039 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41042 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41045 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41046 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41050 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41051 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41058 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41069 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41070 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41073 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41074 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41087 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41092 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41096 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42086 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42092 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42104 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42105 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42118 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42119 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42120 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42121 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42136 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42138 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42147 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42148 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42159 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42160 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42271 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42280 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42284 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42285 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42301 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42302 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42313 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42314 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43830 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43839 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43842 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43858 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43873 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43900 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44934 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44940 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44941 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44942 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44949 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44951 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44967 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44974 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44977 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44985 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44986 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44987 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44998 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-45026 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46673 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46674 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46713 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46725 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46729 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46738 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46740 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46744 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46746 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46759 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46782 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46786 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46798 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46800 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46804 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46811 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46812 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46813 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46814 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46815 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46818 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46821 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46828 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46830 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46836 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46844 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46849 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46852 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46853 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46859 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46871 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47670 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47682 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47691 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47695 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47696 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47697 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47698 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47701 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47718 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47727 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47730 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47742 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47745 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47748 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47750 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47751 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49852 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49853 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49882 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49883 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49884 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49889 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49894 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49895 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49924 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49930 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49936 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49950 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49960 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49966 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49969 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49982 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49983 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49986 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49989 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49991 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49992 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49996 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50007 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50029 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50047 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50051 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50055 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50063 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50067 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50073 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50074 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50088 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50121 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50124 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50125 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50126 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50127 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50131 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50143 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50150 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50151 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50155 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50180 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50186 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50209 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50215 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50217 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50226 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50230 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50235 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50242 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50246 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50257 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50261 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50262 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50264 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50267 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50269 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50276 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50282 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50283 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53057 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53059 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53061 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53068 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53096 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53103 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53106 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53141 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53142 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53156 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53165 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53166 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53168 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53170 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53171 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53173 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53179 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53203 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53206 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53208 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53213 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53214 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53218 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53227 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53237 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53239 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56538 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56548 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56551 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56570 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56581 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56582 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56595 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56596 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56598 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56600 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56601 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56602 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56603 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56604 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56605 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56606 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56608 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56609 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56614 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56615 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56616 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56619 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56626 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56628 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56631 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56633 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56640 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56642 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56651 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56658 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56675 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56704 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56708 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56759 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56765 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56766 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56775 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57792 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57798 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57849 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57850 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57887 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57892 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57896 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57900 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57904 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57917 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57951 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57980 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57998 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58002 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58034 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58055 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58069 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58072 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58093 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58240 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21631 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21671 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21680 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21687 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21692 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21704 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21715 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21724 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21734 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21735 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21756 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21772 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21780 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21785 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21791 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21811 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21812 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21855 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21858 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21863 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21914 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21919 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21927 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21928 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21934 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21945 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21967 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21968 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21969 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21979 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21991 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22020 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22022 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22040 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22041 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22056 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22083 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22088 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22126 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23133 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23142 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23158 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37738 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37750 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37752 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37777 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37778 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37786 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37789 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37796 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37797 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37798 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37803 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37810 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37817 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37819 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37822 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37823 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37839 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37840 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37849 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37854 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37861 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37885 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37890 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37892 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37899 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37903 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37913 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37914 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37921 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37923 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37924 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-37926 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37927 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37928 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-37947 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37952 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37957 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37979 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37991 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38000 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38022 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38024 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38052 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38068 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38069 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38077 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38079 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38117 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38118 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38129 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38131 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38146 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38154 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38157 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38180 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38182 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38183 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38198 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38201 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38206 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38211 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38212 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38226 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38227 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38230 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38236 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38239 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38245 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38248 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38250 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38257 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38259 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38280 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38298 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38313 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38323 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38346 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38348 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38349 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38350 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38352 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38361 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38369 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38375 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38377 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38385 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38389 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38396 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38401 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38403 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38415 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38416 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38422 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38425 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38428 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38437 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38443 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38456 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38459 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38464 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38471 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38476 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38485 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38488 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38494 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38500 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38512 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38527 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38535 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38538 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38548 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38550 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38552 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38555 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38563 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38565 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38572 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38574 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38579 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38582 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38584 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38585 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38593 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38595 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38618 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38627 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38653 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38666 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38676 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38685 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38697 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38699 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38702 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38704 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38707 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38708 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38718 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38722 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38724 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38729 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38734 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39686 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39689 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39691 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39701 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39730 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39738 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39743 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39766 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39776 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39783 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39788 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39790 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39797 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39810 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39823 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39824 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39828 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39835 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39841 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39849 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39859 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39860 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39863 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39864 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39866 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39870 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39871 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39873 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39877 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39880 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39881 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39911 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39913 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39944 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39945 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39951 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39952 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39955 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39957 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39967 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40149 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40364 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68817 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71068 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71071 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71073 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71075 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71078 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71082 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71086 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71089 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71091 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71123 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71137 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71152 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71162 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71220 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71238 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22980 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23001 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23010 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23025 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23068 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23073 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23074 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23078 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23083 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23089 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23098 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23111 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23156 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23171 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23193 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23208 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23209 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23216 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23221 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23226 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23227 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23231 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-23234 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23319 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23343 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23359 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23361 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23378 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23408 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23410 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23411 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23422 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23428 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23447 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23448 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31399 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31402 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31452 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31455 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31485 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31488 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31489 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31493 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31500 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31527 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31532 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31566 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31576 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31578 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31580 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31581 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31583 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31686 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31688 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31696 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31702 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31709 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31715 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31720 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31729 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31747 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31748 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31759 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31787 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43015 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43020 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43027 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43049 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40258 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40277 | LOW3.98 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-12456 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-19378 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2020-11725 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-26934 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-25265 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3238 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-26242 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-3640 | LOW3.98 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-47038 | LOW3.98 | perl 5.36.0-7 fixed in 5.36.0-7+deb12u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-47038 | LOW3.98 | perl-base 5.36.0-7 fixed in 5.36.0-7+deb12u1 | 0.1% 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.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.9 | curl 7.88.1-10+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2026-6429 | LOW3.9 | curl 7.88.1-10+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2026-43239 | LOW3.9 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46012 | LOW3.9 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2023-6129 | LOW3.9 | openssl 3.0.9-1 fixed in 3.0.13-1~deb12u1 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-33599 | LOW3.88 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2024-33599 | LOW3.88 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-33636 | LOW3.88 | libpng-tools 1.6.39-2 fixed in 1.6.39-2+deb12u4 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39971 | LOW3.88 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-0840 | LOW3.82 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW3.82 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-0840 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-0840 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-6779 | LOW3.82 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2019-9192 | LOW3.82 | libc-dev-bin 2.36-9+deb12u1 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2023-6779 | LOW3.82 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2019-9192 | LOW3.82 | libc6-dev 2.36-9+deb12u1 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-33416 | LOW3.82 | libpng-tools 1.6.39-2 fixed in 1.6.39-2+deb12u4 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-39176 | LOW3.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-39179 | LOW3.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-39180 | LOW3.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-39197 | LOW3.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-4458 | LOW3.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-45871 | LOW3.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-46838 | LOW3.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52340 | LOW3.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-6356 | LOW3.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-6535 | LOW3.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-6536 | LOW3.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26620 | LOW3.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42225 | LOW3.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49997 | LOW3.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50083 | LOW3.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57791 | LOW3.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38501 | LOW3.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22998 | LOW3.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53819 | LOW3.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39973 | LOW3.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39982 | LOW3.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40240 | LOW3.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68349 | LOW3.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31669 | LOW3.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43110 | LOW3.82 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-19070 | LOW3.82 | linux-libc-dev 6.1.38-1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2022-0400 | LOW3.82 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69421 | LOW3.82 | openssl 3.0.9-1 fixed in 3.0.18-1~deb12u2 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-28388 | LOW3.82 | openssl 3.0.9-1 fixed in 3.0.19-1~deb12u2 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-28389 | LOW3.82 | openssl 3.0.9-1 fixed in 3.0.19-1~deb12u2 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-28390 | LOW3.82 | openssl 3.0.9-1 fixed in 3.0.19-1~deb12u2 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-31115 | LOW3.82 | xz-utils 5.4.1-0.2 fixed in 5.4.1-1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69277 | LOW3.82 | libsodium23 1.0.18-1 fixed in 1.0.18-1+deb12u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-0565 | LOW3.77 | linux-libc-dev 6.1.38-1 fixed in 6.1.69-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40170 | LOW3.77 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69419 | LOW3.77 | openssl 3.0.9-1 fixed in 3.0.18-1~deb12u2 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2007-1743 | LOW3.74 | apache2 2.4.57-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2007-1743 | LOW3.74 | apache2-bin 2.4.57-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2007-1743 | LOW3.74 | apache2-data 2.4.57-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2007-1743 | LOW3.74 | apache2-utils 2.4.57-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-64505 | LOW3.74 | libpng-dev 1.6.39-2 fixed in 1.6.39-2+deb12u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34757 | LOW3.74 | libpng-dev 1.6.39-2 fixed in 1.6.39-2+deb12u5 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-64505 | LOW3.74 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+deb12u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34757 | LOW3.74 | libpng16-16 1.6.39-2 fixed in 1.6.39-2+deb12u5 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-42093 | LOW3.72 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31607 | LOW3.72 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43038 | LOW3.72 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53752 | LOW3.72 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53781 | LOW3.72 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39981 | LOW3.72 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40141 | LOW3.72 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40176 | LOW3.72 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40269 | LOW3.72 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40294 | LOW3.72 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40304 | LOW3.72 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68800 | LOW3.72 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23243 | LOW3.72 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43078 | LOW3.72 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56406 | LOW3.72 | perl 5.36.0-7 fixed in 5.36.0-7+deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56406 | LOW3.72 | perl-base 5.36.0-7 fixed in 5.36.0-7+deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56406 | LOW3.72 | perl-modules-5.36 5.36.0-7 fixed in 5.36.0-7+deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-7104 | LOW3.72 | sqlite3 3.40.1-2 fixed in 3.40.1-2+deb12u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW3.7 | libapt-pkg6.0 2.6.1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5419 | LOW3.7 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u7 | — | Directly Exposed |
| CVE-2026-5419 | LOW3.7 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | — | Directly Exposed |
| CVE-2024-2511 | LOW3.7 | libssl-dev 3.0.9-1 fixed in 3.0.14-1~deb12u1 | 4.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45446 | LOW3.7 | libssl-dev 3.0.9-1 fixed in 3.0.20-1~deb12u2 | — | Directly Exposed |
| CVE-2024-2511 | LOW3.7 | libssl3 3.0.9-1 fixed in 3.0.14-1~deb12u1 | 4.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45446 | LOW3.7 | libssl3 3.0.9-1 fixed in 3.0.20-1~deb12u2 | — | Directly Exposed |
| CVE-2024-33655 | LOW3.7 | libunbound8 1.17.1-2 fixed in 1.17.1-2+deb12u3 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-43134 | LOW3.66 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2021-45346 | LOW3.65 | libsqlite3-0 3.40.1-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-45346 | LOW3.65 | libsqlite3-dev 3.40.1-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-44466 | LOW3.64 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 15.9% High Exploitation Risk | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-64720 | LOW3.62 | libpng-tools 1.6.39-2 fixed in 1.6.39-2+deb12u1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-65018 | LOW3.62 | libpng-tools 1.6.39-2 fixed in 1.6.39-2+deb12u1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66293 | LOW3.62 | libpng-tools 1.6.39-2 fixed in 1.6.39-2+deb12u1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22695 | LOW3.62 | libpng-tools 1.6.39-2 fixed in 1.6.39-2+deb12u2 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-3867 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52501 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52504 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52507 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52519 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52525 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52565 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52588 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52598 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52628 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52640 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52682 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52766 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52842 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53034 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53222 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53238 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53272 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53321 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53333 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53357 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53420 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53465 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53486 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53600 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53659 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53668 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-6606 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26593 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26594 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2024-26597 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26664 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26665 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26669 | LOW3.62 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26673 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26763 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26791 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26954 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26982 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27401 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-34777 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35785 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35849 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35871 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35896 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35937 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35939 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35963 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35964 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35965 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35966 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35967 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36032 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36033 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36883 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36915 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36916 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36931 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36960 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-37078 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38381 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38538 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38560 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38585 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38599 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38621 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38635 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38659 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39467 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39469 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39471 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39487 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39499 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40929 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40978 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41013 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41014 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41059 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41090 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41091 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41935 | LOW3.62 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42094 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42292 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43877 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44983 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44999 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46722 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46723 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46724 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46731 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46743 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46747 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46774 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46854 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46865 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47686 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47723 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47757 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49860 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49861 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49900 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50033 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50035 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50115 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50128 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50164 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50193 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50247 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50250 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50268 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50278 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50279 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50301 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-52332 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53082 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53099 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53147 | LOW3.62 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53155 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56597 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56627 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56650 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56663 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57838 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57906 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57907 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57908 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57910 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57911 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57912 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57925 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57929 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57945 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57982 | LOW3.62 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58007 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58014 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58054 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21647 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21719 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21782 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21794 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21905 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21920 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21946 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21950 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21985 | LOW3.62 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21993 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22038 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22039 | LOW3.62 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22079 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22104 | LOW3.62 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22107 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22121 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23156 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23157 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37739 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37749 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37780 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37785 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37879 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38004 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38027 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38081 | LOW3.62 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38088 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38103 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38111 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38153 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38159 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38204 | LOW3.62 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38249 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38286 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38320 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38342 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38395 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38445 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38482 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38483 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38497 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38502 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38529 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38530 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38556 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38616 | LOW3.62 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38636 | LOW3.62 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38652 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38670 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38677 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38679 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38680 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38713 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38714 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38715 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38728 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38736 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39682 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39683 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39685 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39687 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39710 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39719 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39735 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39744 | LOW3.62 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39757 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39760 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39806 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39817 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39839 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39853 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39869 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39883 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39891 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39901 | LOW3.62 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39943 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40082 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71093 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71112 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71116 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71133 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71136 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22984 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23076 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23099 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23102 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23187 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23204 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23235 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23315 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23318 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23327 | LOW3.62 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23388 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23397 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31568 | LOW3.62 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31778 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43040 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43052 | LOW3.62 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52502 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-25742 | LOW3.62 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-25743 | LOW3.62 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36013 | LOW3.62 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53174 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53216 | LOW3.62 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56558 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58013 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21753 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21762 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21887 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40064 | LOW3.62 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40301 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40322 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40349 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40351 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68168 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68183 | LOW3.62 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68324 | LOW3.62 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68347 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68366 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68724 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23455 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31613 | LOW3.62 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31685 | LOW3.62 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31786 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43051 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-48502 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-6610 | LOW3.62 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2005-2541 | LOW3.6 | tar 1.34+dfsg-1.2 No fix yet | 3.8% Low-Moderate Risk | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gpgv 2.2.40-1.1 fixed in 2.2.40-1.1+deb12u2 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-4802 | LOW3.57 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u11 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-4802 | LOW3.57 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u11 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-3864 | LOW3.57 | linux-libc-dev 6.1.38-1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-1989 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-35827 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-4244 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-4622 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-46813 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-51043 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-51780 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.69-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-51781 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.69-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-51782 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.69-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52480 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52503 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52517 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52578 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52586 | LOW3.57 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52847 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53622 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-6270 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-6531 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.69-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-6546 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-6931 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.69-1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-6932 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.66-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26654 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26872 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26939 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26974 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27020 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27397 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36899 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38561 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39503 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41040 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41049 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41057 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42162 | LOW3.57 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42228 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43882 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43883 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46858 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47747 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49855 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49903 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49981 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50036 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50059 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50061 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50086 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50154 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50234 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50275 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50286 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56664 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56672 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57876 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21702 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21718 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37776 | LOW3.57 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37915 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38051 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38102 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38107 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38108 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39702 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39749 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39759 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39826 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40186 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40248 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68287 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71221 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23191 | LOW3.57 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23454 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31419 | LOW3.57 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31663 | LOW3.57 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43050 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-51779 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.69-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53762 | LOW3.57 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53821 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54148 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26852 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57984 | LOW3.57 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21703 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21726 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21727 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21761 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21764 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21867 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22004 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39993 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40096 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40135 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40154 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40158 | LOW3.57 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40168 | LOW3.57 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40259 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40318 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40328 | LOW3.57 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68285 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68301 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23050 | LOW3.57 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23270 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23392 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31408 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31508 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31586 | LOW3.57 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31694 | LOW3.57 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43023 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43116 | LOW3.57 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-1247 | LOW3.57 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-2961 | LOW3.57 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-45884 | LOW3.57 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-45885 | LOW3.57 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23054 | LOW3.57 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8058 | LOW3.57 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u13 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u13 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2020-15719 | LOW3.57 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-11053 | LOW3.54 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u10 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-4806 | LOW3.54 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u3 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2023-4806 | LOW3.54 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u3 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2018-1121 | LOW3.54 | linux-libc-dev 6.1.38-1 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2024-5535 | LOW3.54 | openssl 3.0.9-1 fixed in 3.0.15-1~deb12u1 | 5.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42770 | LOW3.54 | openssl 3.0.9-1 fixed in 3.0.20-1~deb12u2 | — | Post-Exploit |
| CVE-2026-9076 | LOW3.54 | openssl 3.0.9-1 fixed in 3.0.20-1~deb12u2 | — | Post-Exploit |
| CVE-2024-53197 | LOW3.48 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-43279 | LOW3.48 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-46065 | LOW3.48 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46113 | LOW3.48 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2010-4651 | LOW3.48 | patch 2.7.6-7 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | curl 7.88.1-10+deb12u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | curl 7.88.1-10+deb12u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-24023 | LOW3.47 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-24857 | LOW3.47 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40345 | LOW3.47 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68346 | LOW3.47 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2020-36694 | LOW3.42 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-21264 | LOW3.42 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-4273 | LOW3.42 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52447 | LOW3.42 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52512 | LOW3.42 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52584 | LOW3.42 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-0193 | LOW3.42 | linux-libc-dev 6.1.38-1 fixed in 6.1.69-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26586 | LOW3.42 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53095 | LOW3.42 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56678 | LOW3.42 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56693 | LOW3.42 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57795 | LOW3.42 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21714 | LOW3.42 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21731 | LOW3.42 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21739 | LOW3.42 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22035 | LOW3.42 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22097 | LOW3.42 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40257 | LOW3.42 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68237 | LOW3.42 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26828 | LOW3.42 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-5742 | LOW3.42 | nano 7.2-1 fixed in 7.2-1+deb12u1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46024 | LOW3.42 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2010-4756 | LOW3.4 | libc-bin 2.36-9+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-33601 | LOW3.4 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | LOW3.4 | libc6 2.36-9+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-33601 | LOW3.4 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc6 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-0725 | LOW3.4 | libcurl4 7.88.1-10+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-9820 | LOW3.4 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u6 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-9820 | LOW3.4 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u6 | <0.1% 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-2024-53589 | LOW3.37 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53589 | LOW3.37 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53589 | LOW3.37 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-5197 | LOW3.37 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53729 | LOW3.37 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54179 | LOW3.37 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54300 | LOW3.37 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-0607 | LOW3.37 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21759 | LOW3.37 | linux-libc-dev 6.1.38-1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-40018 | LOW3.37 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40261 | LOW3.37 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-20712 | LOW3.31 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-20712 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-20712 | LOW3.31 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2016-2781 | LOW3.31 | coreutils 9.1-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-46218 | LOW3.31 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-7264 | LOW3.31 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u7 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2024-8096 | LOW3.31 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u8 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-9681 | LOW3.31 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u9 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | curl 7.88.1-10+deb12u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | curl 7.88.1-10+deb12u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-4527 | LOW3.31 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u3 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4437 | LOW3.31 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW3.31 | libc-dev-bin 2.36-9+deb12u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-4527 | LOW3.31 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u3 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4437 | LOW3.31 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW3.31 | libc6-dev 2.36-9+deb12u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68284 | LOW3.31 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-40982 | LOW3.31 | linux-libc-dev 6.1.38-1 fixed in 6.1.38-4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-1192 | LOW3.31 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-1193 | LOW3.31 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-28746 | LOW3.31 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53785 | LOW3.31 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54094 | LOW3.31 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54292 | LOW3.31 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-6240 | LOW3.31 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26808 | LOW3.31 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36968 | LOW3.31 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47692 | LOW3.31 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47693 | LOW3.31 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47726 | LOW3.31 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50076 | LOW3.31 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53135 | LOW3.31 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39969 | LOW3.31 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40273 | LOW3.31 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68354 | LOW3.31 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68362 | LOW3.31 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68380 | LOW3.31 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31588 | LOW3.31 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-0564 | LOW3.31 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-10524 | LOW3.31 | wget 1.21.3-1+b2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-20588 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | 6.9% Low-Moderate Risk | Post-Exploit |
| CVE-2023-20593 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.38-2 | 5.9% Low-Moderate Risk | Post-Exploit |
| CVE-2024-35960 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-50302 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2025-71272 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2025-71273 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2025-71285 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2025-71287 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2025-71288 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2025-71289 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2025-71291 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2025-71292 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2025-71295 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2025-71297 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2025-71305 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2025-71313 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43123 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43124 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43129 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43130 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43132 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43133 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43135 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43136 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43137 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43139 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43140 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43143 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43145 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43147 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43148 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43149 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43152 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43153 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43156 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43157 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43159 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43161 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43162 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43167 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43168 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43170 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43171 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43172 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43173 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43180 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43182 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43183 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43187 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43200 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43202 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43204 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43209 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43213 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43214 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43215 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43216 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43218 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43219 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43221 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43223 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43225 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43227 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43230 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43231 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43234 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43238 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43240 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43242 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43244 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43246 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43251 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43252 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43255 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43257 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43261 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43262 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43264 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43265 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43266 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43268 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43269 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43270 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43271 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43273 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43277 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43278 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43287 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43288 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43289 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43295 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43296 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43299 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43302 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43308 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43309 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43310 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43312 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43313 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43314 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43315 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43316 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43317 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43318 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43327 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43333 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43338 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43340 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43343 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43344 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43350 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43352 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43353 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43355 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43357 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43359 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43360 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43361 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43362 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43363 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43365 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43366 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43381 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43382 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43387 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43405 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43406 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43407 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43409 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43411 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43412 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43413 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43416 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43420 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43421 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43424 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43425 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43428 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43429 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43432 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43436 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43437 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43441 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43443 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43445 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43451 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43452 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43455 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43456 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43457 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43459 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43466 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43468 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43469 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43472 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43473 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43475 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43492 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43502 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45834 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45835 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45836 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45838 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45841 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45842 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45843 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45844 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45846 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45855 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45857 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45862 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45891 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45914 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45943 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45944 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45949 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45960 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45974 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45981 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45988 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45994 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45996 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45999 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46000 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46022 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46027 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46037 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46050 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46051 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46064 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46070 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46078 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46079 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46082 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46086 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46102 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46107 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46111 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46127 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46130 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46137 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46146 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46147 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46148 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46151 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46153 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46156 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46157 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46158 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46160 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46161 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46165 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46167 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46168 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46169 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46170 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46172 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46179 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46184 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46186 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46190 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46193 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46196 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46200 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46214 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46220 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46225 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46226 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46229 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46231 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46233 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46235 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46236 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46245 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46247 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-46249 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-46252 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46253 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-46254 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46262 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-46273 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46280 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46291 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46304 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46307 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46312 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46320 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46321 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46322 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2025-71315 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43194 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43211 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43253 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43419 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-43483 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43484 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43496 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45847 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45868 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45870 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45871 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45872 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45873 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45877 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45897 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45901 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45904 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45905 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45911 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45915 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45917 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45919 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45920 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45923 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45941 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45948 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45961 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45963 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45964 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45968 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45982 | LOW3.3 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-45987 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-45997 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46002 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46003 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46005 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46014 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46018 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46026 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46038 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46040 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46046 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46049 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46059 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46068 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46071 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46083 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46088 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46092 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46101 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46103 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46136 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46178 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46292 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46299 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46302 | LOW3.3 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-7383 | LOW3.3 | openssl 3.0.9-1 fixed in 3.0.20-1~deb12u2 | — | Post-Exploit |
| CVE-2022-45888 | LOW3.26 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-39198 | LOW3.26 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52886 | LOW3.26 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54156 | LOW3.26 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54164 | LOW3.26 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-21823 | LOW3.26 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36016 | LOW3.26 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57979 | LOW3.26 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21700 | LOW3.26 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21999 | LOW3.26 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39978 | LOW3.26 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40074 | LOW3.26 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40309 | LOW3.26 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40321 | LOW3.26 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68371 | LOW3.26 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23178 | LOW3.26 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23383 | LOW3.26 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23450 | LOW3.26 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23456 | LOW3.26 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31502 | LOW3.26 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31516 | LOW3.26 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-44032 | LOW3.26 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-44033 | LOW3.26 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-44034 | LOW3.26 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-3397 | LOW3.21 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52644 | LOW3.21 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54072 | LOW3.21 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-24861 | LOW3.21 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26830 | LOW3.21 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27030 | LOW3.21 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38544 | LOW3.21 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41012 | LOW3.21 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42161 | LOW3.21 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57893 | LOW3.21 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40307 | LOW3.21 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68282 | LOW3.21 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31504 | LOW3.21 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40918 | LOW3.21 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5958 | LOW3.21 | sed 4.9-1 fixed in 4.9-1+deb12u1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW3.18 | curl 7.88.1-10+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2026-6253 | LOW3.18 | curl 7.88.1-10+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2026-7168 | LOW3.18 | curl 7.88.1-10+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2026-42766 | LOW3.18 | openssl 3.0.9-1 fixed in 3.0.20-1~deb12u2 | — | Post-Exploit |
| CVE-2026-42767 | LOW3.18 | openssl 3.0.9-1 No fix yet | — | Post-Exploit |
| CVE-2025-28162 | LOW3.16 | libpng-tools 1.6.39-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54081 | LOW3.16 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54169 | LOW3.16 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50251 | LOW3.16 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-21722 | LOW3.16 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40048 | LOW3.16 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40146 | LOW3.16 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68757 | LOW3.16 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71066 | LOW3.16 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23253 | LOW3.16 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36387 | LOW3.15 | apache2 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36387 | LOW3.15 | apache2-bin 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36387 | LOW3.15 | apache2-data 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36387 | LOW3.15 | apache2-utils 2.4.57-2 fixed in 2.4.61-1~deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-38546 | LOW3.15 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41080 | LOW3.15 | libexpat1 2.5.0-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-9143 | LOW3.15 | libssl-dev 3.0.9-1 fixed in 3.0.15-1~deb12u1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-9143 | LOW3.15 | libssl3 3.0.9-1 fixed in 3.0.15-1~deb12u1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-0989 | LOW3.15 | libxml2 2.9.14+dfsg-1.3~deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.11 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.38.1-5+b1 No fix yet | <0.1% 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-2023-52497 | LOW3.11 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52810 | LOW3.11 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53808 | LOW3.11 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53850 | LOW3.11 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54096 | LOW3.11 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42224 | LOW3.11 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57874 | LOW3.11 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40019 | LOW3.11 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40071 | LOW3.11 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40080 | LOW3.11 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40190 | LOW3.11 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40279 | LOW3.11 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40355 | LOW3.11 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68245 | LOW3.11 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68342 | LOW3.11 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68343 | LOW3.11 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68736 | LOW3.11 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68764 | LOW3.11 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68815 | LOW3.11 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68819 | LOW3.11 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31449 | LOW3.11 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31464 | LOW3.11 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31505 | LOW3.11 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31570 | LOW3.11 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31700 | LOW3.11 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31708 | LOW3.11 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.38.1-5+b1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.38.1-5+b1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux-extra 2.38.1-5+b1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-31879 | LOW3.11 | wget 1.21.3-1+b2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-39189 | LOW3.06 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-39192 | LOW3.06 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-39193 | LOW3.06 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26843 | LOW3.06 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56662 | LOW3.06 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31649 | LOW3.06 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52481 | LOW3.06 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52511 | LOW3.06 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52529 | LOW3.06 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26702 | LOW3.06 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26894 | LOW3.06 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-28085 | LOW3.04 | bsdutils 1:2.38.1-5+b1 fixed in 2.38.1-5+deb12u1 | 10.2% High Exploitation Risk | Post-Exploit |
| CVE-2024-28085 | LOW3.04 | mount 2.38.1-5+b1 fixed in 2.38.1-5+deb12u1 | 10.2% High Exploitation Risk | Post-Exploit |
| CVE-2024-28085 | LOW3.04 | util-linux 2.38.1-5+b1 fixed in 2.38.1-5+deb12u1 | 10.2% High Exploitation Risk | Post-Exploit |
| CVE-2024-28085 | LOW3.04 | util-linux-extra 2.38.1-5+b1 fixed in 2.38.1-5+deb12u1 | 10.2% High Exploitation Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.01 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1153 | LOW3.01 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1153 | LOW3.01 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | curl 7.88.1-10+deb12u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5435 | LOW3.01 | libc-dev-bin 2.36-9+deb12u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15281 | LOW3.01 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5435 | LOW3.01 | libc6-dev 2.36-9+deb12u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15281 | LOW3.01 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54048 | LOW3.01 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54302 | LOW3.01 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35870 | LOW3.01 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40083 | LOW3.01 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40242 | LOW3.01 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40324 | LOW3.01 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-3714 | LOW3.01 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31790 | LOW3.01 | openssl 3.0.9-1 fixed in 3.0.19-1~deb12u2 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-6237 | LOW3.01 | openssl 3.0.9-1 fixed in 3.0.13-1~deb12u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69420 | LOW3.01 | openssl 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-22796 | LOW3.01 | openssl 3.0.9-1 fixed in 3.0.18-1~deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40909 | LOW3.01 | perl 5.36.0-7 fixed in 5.36.0-7+deb12u3 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40909 | LOW3.01 | perl-base 5.36.0-7 fixed in 5.36.0-7+deb12u3 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40909 | LOW3.01 | perl-modules-5.36 5.36.0-7 fixed in 5.36.0-7+deb12u3 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-42250 | LOW3 | bzip2 1.0.8-5+b1 No fix yet | — | Post-Exploit |
| CVE-2004-0230 | LOW3 | linux-libc-dev 6.1.38-1 No fix yet | 9.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34180 | LOW3 | openssl 3.0.9-1 fixed in 3.0.20-1~deb12u2 | — | Post-Exploit |
| CVE-2023-53706 | LOW2.96 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54045 | LOW2.96 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54107 | LOW2.96 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54136 | LOW2.96 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54141 | LOW2.96 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35910 | LOW2.96 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39994 | LOW2.96 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39998 | LOW2.96 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40111 | LOW2.96 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40118 | LOW2.96 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40167 | LOW2.96 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40194 | LOW2.96 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40201 | LOW2.96 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40214 | LOW2.96 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40272 | LOW2.96 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40323 | LOW2.96 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68742 | LOW2.96 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23239 | LOW2.96 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23240 | LOW2.96 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23271 | LOW2.96 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23317 | LOW2.96 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31392 | LOW2.96 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31414 | LOW2.96 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31426 | LOW2.96 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | curl 7.88.1-10+deb12u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-1206 | LOW2.91 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53996 | LOW2.91 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49569 | LOW2.91 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53240 | LOW2.91 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40319 | LOW2.91 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-23039 | LOW2.91 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-4155 | LOW2.86 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53828 | LOW2.86 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54251 | LOW2.86 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-28956 | LOW2.86 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36350 | LOW2.86 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36357 | LOW2.86 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68801 | LOW2.86 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68816 | LOW2.86 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-9230 | LOW2.86 | openssl 3.0.9-1 fixed in 3.0.17-1~deb12u3 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-4741 | LOW2.86 | openssl 3.0.9-1 fixed in 3.0.14-1~deb12u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-20569 | LOW2.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.38-4 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-71274 | LOW2.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43163 | LOW2.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43275 | LOW2.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43342 | LOW2.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43383 | LOW2.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43430 | LOW2.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43439 | LOW2.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-43448 | LOW2.82 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Post-Exploit |
| CVE-2026-46159 | LOW2.82 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2026-46187 | LOW2.82 | linux-libc-dev 6.1.38-1 No fix yet | — | Post-Exploit |
| CVE-2017-13716 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2018-20673 | LOW2.8 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-9996 | LOW2.8 | binutils 2.40-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW2.8 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2018-20673 | LOW2.8 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-9996 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW2.8 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2018-20673 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-9996 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.38.1-5+b1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | cpp-12 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | g++-12 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | gcc-12 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | gcc-12-base 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-0395 | LOW2.8 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u10 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-0395 | LOW2.8 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u10 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | libgcc-12-dev 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-4214 | LOW2.8 | libpng-tools 1.6.39-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | libstdc++-12-dev 12.2.0-14 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40347 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68192 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68291 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68307 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-36402 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-38096 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-48628 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-48772 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-49034 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-0160 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-0597 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-23005 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-2430 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-31082 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-37454 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-4130 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-4132 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-4133 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-4194 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-42752 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-42754 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-42755 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-4515 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-4569 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-46343 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-50431 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-5090 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-5158 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52429 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52435 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52442 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52443 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52448 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52449 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52454 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52456 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52458 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52462 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52463 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52467 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52470 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52476 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52477 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52479 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52484 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52485 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52486 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52488 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52493 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52498 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52499 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52500 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52506 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52513 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52516 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52518 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52520 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52522 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52523 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52526 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52527 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52528 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52532 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52559 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52560 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52562 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52563 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52564 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52566 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52567 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52570 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52573 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52574 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52577 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52580 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52582 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52583 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52587 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52590 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52591 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52593 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52595 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52601 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52606 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52607 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52610 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52615 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52616 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52619 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52622 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52623 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52625 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52629 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52632 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52635 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52638 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52641 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52643 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52648 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52650 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52652 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52655 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.69-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52656 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52658 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52660 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52661 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52662 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52670 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52671 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52672 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52675 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52676 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52677 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52678 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52680 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52683 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52686 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52687 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52690 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52692 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52693 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52694 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52698 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52699 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52750 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52753 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52754 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52761 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52762 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52763 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52767 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52770 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52773 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52774 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.66-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52778 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52780 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52781 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.66-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52784 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52787 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52788 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52789 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52791 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52792 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52797 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52803 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52806 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52808 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52809 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52813 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52814 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52815 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52817 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52821 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52825 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52826 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52828 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52831 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52832 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52833 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52834 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52841 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52843 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52845 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52849 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52850 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52853 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52856 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52857 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52860 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52863 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52865 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52869 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52871 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52873 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52875 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52876 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52877 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52878 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52879 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52880 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52881 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.69-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52882 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52887 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52888 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52889 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52915 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52918 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52919 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52920 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52923 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52924 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53071 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53146 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53147 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53149 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53150 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53151 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53152 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53165 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53167 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53174 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53175 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53177 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53181 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53185 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53189 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53195 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53196 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53201 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53207 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53208 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53209 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53210 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53220 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53221 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53226 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53228 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53230 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53231 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53243 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53245 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53247 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53248 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53249 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53251 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53255 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53258 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53260 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53261 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53264 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53275 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53280 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53287 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53288 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53291 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53292 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53304 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53309 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53312 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53313 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53314 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53323 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53324 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53325 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53328 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53336 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53339 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53342 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53343 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53352 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53353 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53354 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53356 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53360 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53361 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53362 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53365 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53367 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53369 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53370 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53371 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53379 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53380 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53384 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53385 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53391 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53394 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53397 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53421 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53424 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53425 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53429 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53436 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53438 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53441 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53442 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53444 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53448 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53451 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53456 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53457 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53460 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53461 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53462 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53463 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53472 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53480 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53488 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53491 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53505 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53518 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53519 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53523 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53526 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53529 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53531 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53538 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53539 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53540 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53545 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53546 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53548 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53557 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53558 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53563 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53568 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53574 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53579 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53580 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53583 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53585 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53588 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53593 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53597 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53601 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53602 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53603 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53611 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53617 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53618 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53627 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53631 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53647 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53648 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53649 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53650 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53653 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53654 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53656 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53657 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53658 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53660 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53662 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53663 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53666 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53670 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53672 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53674 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53681 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53687 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53698 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53825 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53829 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53846 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53856 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53989 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53995 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53999 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54013 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54052 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54106 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54137 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54271 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54280 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54299 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-6039 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-6622 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.69-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-6915 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-7042 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-0340 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-0639 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-0641 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-1151 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-2193 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2024-22099 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-23848 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-23849 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-23850 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-23851 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-25739 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-25740 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-25741 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26584 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26590 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26591 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26595 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26596 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26600 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26601 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26602 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26603 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26605 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26606 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26608 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26615 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26618 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26621 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26626 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26629 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26632 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26634 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26635 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26636 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26640 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26641 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26642 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26643 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26644 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26645 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26646 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26651 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26656 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26659 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26660 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26663 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26667 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26668 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26670 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26675 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26677 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26679 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26680 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26681 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26684 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26686 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26687 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26688 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26691 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26695 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26696 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26697 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26700 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26706 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26707 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26714 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26715 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26717 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26718 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26722 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26726 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26727 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26731 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26733 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26735 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26737 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26740 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26741 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26743 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26744 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26750 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26751 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26752 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26756 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26759 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26760 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26761 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26765 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26766 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26767 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26771 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26772 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26773 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26774 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26775 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26776 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26777 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26778 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26779 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26780 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26781 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26783 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26787 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26788 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26789 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26790 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26795 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26798 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26799 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26801 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26802 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26803 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26804 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-26805 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26807 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26809 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26811 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26812 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26813 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26814 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26815 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26816 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26817 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26820 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26822 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26825 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26826 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26829 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26832 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26833 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26834 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26835 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26838 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26839 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26840 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26841 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26844 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26845 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26849 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26851 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26853 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26855 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26860 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26863 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26864 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26866 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26868 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26870 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26876 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26877 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26879 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26880 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26881 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26889 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26891 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26893 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26896 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26900 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26901 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26902 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26903 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26906 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26916 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26917 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26919 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26920 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26921 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26922 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26925 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26926 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26931 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26935 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26937 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26940 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26943 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26946 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26947 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26948 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26953 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26962 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26963 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26964 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26966 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26969 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26970 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26973 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26976 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26977 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26978 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26980 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26984 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26987 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26993 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26994 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26997 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26999 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27001 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27002 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27003 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27004 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27010 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27011 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27012 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27013 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27014 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27015 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27016 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27017 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27023 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27025 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27028 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27032 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27034 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27035 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27037 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27038 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27039 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27041 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27044 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27046 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27047 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27051 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27052 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27053 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27054 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27056 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27057 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27059 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27062 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27072 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27074 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27076 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27077 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27078 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27079 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27388 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27389 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27390 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27391 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27399 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27400 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27402 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27403 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27405 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27407 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27410 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27412 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27413 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27414 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27416 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27417 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27418 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27431 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27432 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27435 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27436 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27437 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-31076 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-33619 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-33621 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-33847 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-34027 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35247 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35784 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35790 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35794 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35796 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35799 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35800 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35801 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35803 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35804 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35805 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35806 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35807 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35808 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35811 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35813 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35815 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35817 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35818 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35819 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35821 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35822 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35823 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-35824 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35825 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35826 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35827 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35828 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35829 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35830 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35833 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35835 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35837 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35838 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35839 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35840 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35842 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35844 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35851 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35852 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35860 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35872 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35875 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35877 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35879 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35884 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35885 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35890 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35891 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35892 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35893 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35895 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35897 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35898 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35899 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35900 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35902 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35904 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35907 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35908 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35909 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35912 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35915 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35916 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35922 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35924 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35925 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35930 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35931 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35933 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35934 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35936 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35938 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35940 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35942 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35943 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35944 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35945 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35946 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35950 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35951 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35952 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35955 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-35956 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35958 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35959 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35961 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35962 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35969 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35970 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35971 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35978 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35981 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35982 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35983 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35984 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35986 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35988 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35989 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35990 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35992 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35995 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35996 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35997 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35998 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35999 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36000 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36004 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36005 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36006 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36007 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36008 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36009 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36014 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36017 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36020 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36021 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36023 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36025 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36026 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36029 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36244 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36270 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36286 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36288 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36476 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36478 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36479 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36484 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36489 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36882 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36889 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36890 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36891 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36893 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36897 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36900 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36901 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36902 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36903 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36905 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36908 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36909 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36911 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36917 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36918 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36919 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36920 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36922 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36924 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36926 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36929 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36930 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36933 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36937 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36938 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36939 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36941 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36945 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36946 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36947 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36951 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36953 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36954 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36957 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36959 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36962 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36964 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36965 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36967 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36969 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36972 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36975 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36977 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-37021 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-37356 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38390 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38543 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38546 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38547 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38549 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38553 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38554 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38557 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38558 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38564 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38565 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38567 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38571 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38575 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38579 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38582 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38587 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38589 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38590 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38591 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38594 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38597 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38598 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38600 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38602 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38603 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38607 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38608 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38611 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38612 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38615 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38618 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38619 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38620 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38622 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38623 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38624 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38625 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38632 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38633 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38634 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38636 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38637 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38661 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38780 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39282 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39292 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39298 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39301 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39371 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39466 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39468 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39472 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39474 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39475 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39476 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39481 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39482 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39484 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39488 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39489 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39490 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39493 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39497 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39505 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39506 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39507 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39509 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40904 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40908 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40910 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40911 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40912 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40914 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40915 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40916 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40919 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40921 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40924 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40931 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40932 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40934 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40937 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40938 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40941 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40942 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40945 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40947 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40948 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40957 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40959 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40960 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40961 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40963 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40965 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40966 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40967 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40968 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40969 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40970 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40971 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40972 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40973 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40975 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40976 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40977 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40980 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40981 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40983 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40984 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40987 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40988 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40990 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40993 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40995 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40998 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40999 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41001 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41002 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41004 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41006 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41008 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41009 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41015 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41016 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41017 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41019 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41022 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41023 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41030 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41031 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41034 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41035 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41036 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41038 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41041 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41044 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41047 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41048 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41055 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41056 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41060 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41062 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41063 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41064 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41065 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41066 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41068 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41072 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41075 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41076 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41077 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41078 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41079 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41080 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41081 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41082 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41088 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41089 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41093 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41095 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41097 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41098 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42063 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42068 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42069 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42070 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42073 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42076 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42077 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42079 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42080 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42082 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42084 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42085 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42087 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42089 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42090 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42095 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42096 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42097 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42098 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42101 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42103 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42106 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42109 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42110 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42115 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42122 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42124 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42126 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42127 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42128 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42129 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42137 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42139 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42140 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42142 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42145 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42153 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42223 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42232 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42236 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42237 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42238 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42239 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42240 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42241 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42243 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42244 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42245 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42246 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42247 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42250 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42252 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42258 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42259 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42265 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42267 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42268 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42269 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42270 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42272 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42273 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42274 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42276 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42277 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42279 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42281 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42283 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42286 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42288 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42289 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42290 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42291 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42295 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42296 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42297 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42299 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42304 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42305 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42306 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42307 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42309 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42310 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42311 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42312 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42315 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42316 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42317 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42318 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42319 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42320 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42321 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42322 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43098 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43817 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43818 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43819 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43823 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43824 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43828 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43829 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43831 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43832 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43833 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43834 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43835 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43837 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43840 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43846 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43849 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43850 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43851 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43853 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43854 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43855 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43856 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43859 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43860 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43861 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43863 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43867 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43868 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43869 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43870 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43871 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43872 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43875 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43876 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43879 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43880 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43884 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43889 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43890 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43893 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43894 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43897 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-3 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43899 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43901 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43902 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43904 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43905 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43907 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43908 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43909 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43912 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43913 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43914 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44931 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44935 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44938 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44939 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44944 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44946 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44947 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-44948 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44950 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44958 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44960 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44963 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44965 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44966 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44968 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44969 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44970 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44971 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44982 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44988 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44989 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44990 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44991 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44995 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-45000 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-45001 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-45002 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-45006 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-45007 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-45008 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-45009 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-45010 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-45011 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-45015 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-45016 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-45018 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-45019 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-45021 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-45022 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-45025 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-45028 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-45029 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-45828 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46675 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46676 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46677 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46678 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46681 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46685 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46686 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46689 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46694 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46698 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46702 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46707 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46714 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46715 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46716 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46717 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46719 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46720 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46721 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46726 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46727 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46728 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46730 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46732 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46733 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46735 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46737 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46739 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46742 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46745 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46750 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46751 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46752 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46753 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46754 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46755 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46760 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46761 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46763 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46765 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46770 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46771 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46772 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46773 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46775 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46776 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46777 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46780 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46781 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46783 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46784 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46791 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46795 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46802 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46805 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46806 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46807 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46808 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46809 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46810 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46816 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46817 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46819 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46822 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46826 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46829 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46832 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46834 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46835 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46840 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46841 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46846 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46848 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46855 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46857 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46860 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46896 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47141 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47143 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47408 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47658 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47661 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47662 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47663 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47664 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47665 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47666 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47667 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47669 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47671 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47673 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47674 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47678 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47683 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47684 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47690 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47699 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47703 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47704 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47705 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47706 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47707 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47709 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47710 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47712 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47713 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47720 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47728 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47731 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47734 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47735 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47736 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47737 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47739 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47740 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47743 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47749 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47752 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47753 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47754 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47756 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47794 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47809 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-48881 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49568 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49571 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49850 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49851 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49856 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49858 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49863 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49867 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49868 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49870 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49871 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49875 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49877 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49878 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49879 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49881 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49886 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49890 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49891 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49892 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49893 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49896 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49897 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49898 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49899 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49901 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49902 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49905 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49906 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49907 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49908 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49909 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49910 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49911 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49912 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49913 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49914 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49915 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49916 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49917 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49918 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49919 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49920 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49921 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49922 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49923 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49925 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49926 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49927 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49929 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49933 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49935 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49937 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49938 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49939 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49940 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49944 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49945 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49946 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49948 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49949 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49951 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49952 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49954 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49955 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49957 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49958 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49959 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49961 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49962 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49963 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49965 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49968 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49970 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49973 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49974 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49975 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49977 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49978 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49985 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49988 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49994 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50000 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50001 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50002 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50003 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50008 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50009 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50012 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50013 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50015 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50017 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50019 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50022 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50024 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50026 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50028 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50031 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50038 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50039 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50040 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50041 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50045 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50046 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50048 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50049 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50056 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50058 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50060 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50062 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50069 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50072 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50077 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50078 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50085 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50087 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50093 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50095 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50096 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50098 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50099 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50101 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50103 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50108 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50110 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50111 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50116 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50117 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50133 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50134 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50136 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50138 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50141 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50142 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50145 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50146 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50147 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50148 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50153 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50156 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50160 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50162 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50163 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50166 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50167 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50168 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50171 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50176 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50179 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50182 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50184 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50185 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50187 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50188 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50189 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50194 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50195 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50196 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50198 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50199 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50200 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50201 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50202 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50205 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50208 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50210 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50218 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50229 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50232 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50233 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50236 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50237 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50243 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50244 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50245 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50248 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50249 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50252 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50255 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50256 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50258 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50259 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50265 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50271 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50272 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50273 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50284 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50285 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50287 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50289 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50290 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50292 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50295 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50296 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50298 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50299 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50304 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-52559 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-52560 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53042 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53043 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53051 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53055 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53056 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53058 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53060 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53063 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53066 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53070 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53072 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53079 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53081 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53085 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53089 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53090 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53091 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53093 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53094 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53097 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53101 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53105 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53110 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53112 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53113 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53114 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53119 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53120 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53121 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53122 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53123 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53125 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53127 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53128 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53129 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53130 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53131 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53134 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53138 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53140 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53144 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53145 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53146 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53148 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53151 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53154 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53157 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53158 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53161 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53164 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53172 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53175 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53180 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53181 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53183 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53184 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53187 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53190 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53194 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53195 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53196 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53198 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53207 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53209 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53210 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53215 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53217 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53219 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53220 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53221 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53224 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53226 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53229 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53230 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53231 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53233 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53234 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53241 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53680 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53685 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53687 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53690 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-54031 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-54683 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-55881 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-55916 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56369 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56531 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56532 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56533 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56539 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56544 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56546 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56549 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56557 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56562 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56565 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56566 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56567 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56569 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56572 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56574 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56575 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56578 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56579 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56583 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56584 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56585 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56586 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56587 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56588 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56589 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56590 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56591 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56592 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56593 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56594 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56599 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56610 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56611 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56622 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56623 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56625 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56629 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56630 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56634 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56636 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56641 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56643 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56644 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56645 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56647 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56648 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56657 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56659 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56660 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56661 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56665 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56670 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56677 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56679 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56681 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56683 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56687 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56688 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56690 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56691 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56692 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56694 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56698 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56700 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56701 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56703 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56705 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56707 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56709 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56712 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56715 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56716 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56717 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56718 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56719 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56720 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56722 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56723 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56724 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56725 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56726 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56727 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56728 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56739 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56742 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56745 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56746 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56747 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56748 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56751 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56754 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56755 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56756 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56758 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56763 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56767 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56769 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56770 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56774 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56776 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56777 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56778 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56779 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56780 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56783 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56785 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56787 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57802 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57804 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57807 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57809 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57834 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57841 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57872 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57882 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57883 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57884 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57888 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57889 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57890 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57895 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57897 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57901 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57902 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57903 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57916 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57922 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57924 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57930 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57931 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57938 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57939 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57940 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57946 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57947 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57948 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57949 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57973 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57975 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57976 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57977 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57978 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57981 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57986 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57993 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57996 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57997 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57999 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58001 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58005 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58006 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58009 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58010 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58011 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58012 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58016 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58017 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58020 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58051 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58052 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58053 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58056 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58058 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58061 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58063 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58068 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58071 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58076 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58079 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58080 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58083 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58085 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58086 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58089 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58090 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58094 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58095 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58096 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58097 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58098 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58100 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58237 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58239 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58241 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21629 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.124-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21634 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21635 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21636 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21637 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21638 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21639 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21640 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21645 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21646 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21648 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21649 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21653 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21656 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21658 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21660 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21662 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21664 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21665 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21666 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21667 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21668 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21669 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21673 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21675 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21676 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21678 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21681 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21682 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21683 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21684 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21689 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21690 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21693 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21694 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21696 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21697 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21699 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21705 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21706 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21707 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21708 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21711 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21712 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21716 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21721 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21723 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21725 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21728 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21729 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21736 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21738 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21744 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21745 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21748 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21749 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21750 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21758 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21760 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21763 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21765 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21766 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21767 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21768 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21775 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21776 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21779 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21781 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21787 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21790 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21792 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21795 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21796 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21799 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21801 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21802 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21804 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21806 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21814 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21816 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21819 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21820 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21821 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21823 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21826 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21829 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21830 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21831 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21832 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21835 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21836 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21838 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21839 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21844 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21846 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21848 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21853 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21859 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21861 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21862 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21864 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21865 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21866 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21870 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21871 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21872 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21875 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21877 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21878 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21881 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21885 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21888 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21891 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21894 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21898 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21899 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21904 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21907 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21909 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21910 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21912 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21913 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21916 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21917 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21918 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21922 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21924 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21925 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21926 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21931 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21935 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21936 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21937 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21941 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21944 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21948 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21949 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21951 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21955 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21956 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21957 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21959 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21960 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21961 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21962 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21963 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21964 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21970 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21971 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21972 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21975 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21976 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21978 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21980 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21981 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21986 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21992 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21994 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21996 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21997 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22005 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22007 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22008 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22010 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22014 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22015 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22018 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22021 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22025 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22026 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22028 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22033 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22037 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22042 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22043 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22044 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22045 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22048 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22049 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22053 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22054 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22055 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22057 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22058 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22062 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22063 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22066 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22070 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22071 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22072 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22073 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22075 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22081 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22086 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22089 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22090 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22093 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22095 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22103 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22105 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22109 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22111 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22113 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22119 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22125 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22127 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23129 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23130 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23131 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23132 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23136 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23138 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23140 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23141 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23143 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23144 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23145 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23146 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23147 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23148 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23150 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23155 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23159 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23160 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23161 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23163 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37740 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37741 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37742 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37747 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37748 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37756 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37757 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37758 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37765 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37766 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37767 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37768 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37769 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37770 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37771 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37772 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37773 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37775 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37781 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37787 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37788 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37790 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37792 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37794 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37800 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37801 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37802 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37805 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37806 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37807 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37808 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37811 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37812 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37815 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37818 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37820 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37824 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37829 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37830 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37833 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37834 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37836 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37841 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37842 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37844 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37850 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37851 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37852 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37853 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37856 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37857 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37858 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37859 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37860 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37862 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37864 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37865 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37867 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37871 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37875 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37880 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37881 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37883 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37889 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37893 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37897 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37901 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37905 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37909 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37911 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37912 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37917 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37925 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37929 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37930 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37931 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37932 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37936 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37937 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37938 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37940 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37945 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37948 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37949 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37951 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37953 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37956 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37958 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37959 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37961 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37962 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37963 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37964 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37967 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37968 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37969 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37970 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37972 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37977 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37980 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37982 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37983 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37989 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37990 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37992 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37994 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.139-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37995 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.139-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37997 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.139-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37998 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.139-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38001 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38003 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38005 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38006 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38007 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38009 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38014 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38015 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38018 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38020 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38023 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38029 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38031 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38034 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38035 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38037 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38038 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38039 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38040 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38041 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38042 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38043 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38044 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38045 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38057 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38058 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38059 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38061 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38062 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38063 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38064 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38065 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38066 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38067 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38071 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38072 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38074 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38075 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38080 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38084 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38086 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38090 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38094 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38095 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38096 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38097 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38100 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38105 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38113 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38115 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38119 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38120 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38122 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38124 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38125 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38126 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38127 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38132 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38135 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38136 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38138 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38140 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38142 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38143 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38145 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38147 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38148 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38151 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38152 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38158 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38160 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38161 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38162 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38163 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38165 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38166 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38167 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38170 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38173 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38174 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38177 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.139-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38181 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38184 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38185 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38190 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38191 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38192 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38193 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38194 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38195 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38197 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38200 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38202 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38203 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38207 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38214 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38215 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38218 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38219 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38222 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38225 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38229 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38231 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38237 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38244 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38246 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38251 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38260 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38261 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38262 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38263 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38264 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38272 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38273 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38275 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38277 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38282 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38283 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38285 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38293 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38300 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38303 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38304 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38305 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38310 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38311 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38312 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38319 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38322 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38324 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38326 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38328 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38331 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38332 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38333 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38334 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38335 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38336 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38337 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38344 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38345 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38347 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38354 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38359 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38362 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38363 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38364 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38371 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38382 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38384 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38386 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38387 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38391 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38399 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38400 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38404 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38406 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38408 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38409 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38410 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38412 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38418 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38419 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38420 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38424 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38426 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38429 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38430 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38436 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38438 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38439 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38441 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38444 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38449 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38451 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38455 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38457 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38458 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38460 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38465 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38466 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38467 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38468 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38470 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38472 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38473 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38474 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38478 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38480 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38481 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38487 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38491 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38495 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38498 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38499 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38503 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38507 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38510 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38513 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38514 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38516 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38520 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38528 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38531 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38539 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38540 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38542 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38543 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38544 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38546 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38553 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38560 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38562 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38569 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38575 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38576 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38577 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38578 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38581 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38583 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38587 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38588 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38590 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38591 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38597 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38601 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38602 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38604 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38608 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38609 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38610 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38612 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38614 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38615 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38622 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38623 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38624 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38626 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38630 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38634 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38635 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38637 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38639 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38643 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38644 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38645 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38650 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38659 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38663 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38664 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38665 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38668 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38671 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38678 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38683 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38684 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38691 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38692 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38693 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38694 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38695 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38696 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38698 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38700 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38701 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38705 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38706 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38709 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38710 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38711 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38712 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38716 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38721 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38723 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38725 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38727 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38732 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38735 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39675 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39676 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39677 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39681 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39684 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39692 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39693 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39694 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39703 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39705 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39706 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39707 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39709 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39714 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39715 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39716 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39718 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39720 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39721 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39724 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39728 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39731 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39732 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39734 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39736 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39737 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39742 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39746 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39747 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39748 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39752 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39756 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39762 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39763 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39764 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39767 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39770 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39772 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39773 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39779 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39782 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39787 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39789 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39794 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39795 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39798 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39800 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39801 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39805 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39808 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39812 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39819 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39827 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39829 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39833 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39838 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39842 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39843 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39844 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39845 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39846 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39847 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39848 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39850 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39851 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39857 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39865 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39876 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39885 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39886 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39889 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39894 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39902 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39907 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39909 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39910 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39914 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39916 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39920 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39923 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39925 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39929 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39931 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39932 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39933 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39934 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39937 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39938 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39940 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39942 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39946 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39947 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39949 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39953 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39989 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40005 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40020 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40026 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40027 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40029 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40030 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40040 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40044 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40051 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40053 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40070 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40075 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40078 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40102 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40104 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40109 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40115 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40140 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40153 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40160 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40164 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40171 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40211 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40231 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40251 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40264 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40280 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40283 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40284 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40292 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40293 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40297 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40300 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40325 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40339 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40363 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68176 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68185 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68188 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68209 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68211 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68223 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68229 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68231 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68236 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68259 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68261 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68265 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68283 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68304 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68310 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68331 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68337 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68340 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68358 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68365 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68372 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68379 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68725 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68774 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68776 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68803 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68814 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68821 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68823 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71064 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71077 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71079 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71081 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71083 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71084 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71085 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71087 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71088 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71094 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71095 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71096 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71097 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71098 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71102 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71104 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71105 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71108 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71109 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71113 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71114 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71118 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71119 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71120 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71121 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71125 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71126 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71127 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71129 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71130 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71131 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71132 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71138 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71144 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71147 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71150 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71154 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71160 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71161 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71163 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71180 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71182 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71183 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71184 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71185 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71186 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71188 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71189 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71190 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71191 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71200 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71202 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71222 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71227 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71232 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71233 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71235 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71236 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71237 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71265 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71266 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71267 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71268 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71269 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22976 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22977 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22979 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22982 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22990 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22991 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22992 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22994 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22996 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22997 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22999 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23000 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23003 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23005 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23006 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23011 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23019 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23020 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23021 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23026 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23031 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23038 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23047 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23058 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23060 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23061 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23063 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23064 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23066 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23069 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23075 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23080 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23084 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23085 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23086 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23087 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23088 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23090 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23091 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23093 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23095 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23096 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23097 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23100 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23103 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23105 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23107 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23108 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23113 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23116 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23119 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23120 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23121 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23124 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23125 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23128 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23133 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23137 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23138 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23139 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23140 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23141 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23142 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23144 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23145 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23146 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23150 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23154 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23157 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23164 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23168 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23170 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23172 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23190 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23198 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23202 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23205 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23206 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23213 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23214 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23220 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23222 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23228 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23229 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23230 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23236 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23237 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23238 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23242 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23247 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23255 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23256 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23257 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23258 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23262 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23264 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23265 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23266 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23267 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23272 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23273 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23274 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23276 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23277 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23278 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23279 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23284 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23286 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23287 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23289 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23290 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23291 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23292 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23293 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23296 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23298 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23300 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23303 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23304 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23306 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23307 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23310 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23312 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23321 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23324 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23330 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23335 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23336 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23339 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23340 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23346 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23351 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23352 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23356 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23357 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23362 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23365 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23367 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23368 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23370 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23371 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23374 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23379 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23381 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23382 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23389 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23391 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23396 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23398 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23399 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23401 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23403 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23404 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23405 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23409 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23414 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23419 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23420 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23426 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23434 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23438 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23439 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23442 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23444 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23446 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23449 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23460 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23462 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23465 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23468 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23472 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23474 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23475 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31391 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31400 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31403 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31407 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31410 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31411 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31412 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31415 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31416 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31418 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31420 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31421 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31422 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31423 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31424 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31425 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31427 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31428 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31434 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31441 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31446 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31447 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31448 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31450 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31451 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31453 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31454 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31458 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31462 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31467 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31469 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31473 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31480 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31483 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31487 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31492 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31495 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31496 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31497 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31498 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31503 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31507 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31509 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31510 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31512 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31515 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31518 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31519 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31520 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31521 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31522 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31524 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31531 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31533 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31537 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31540 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31545 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31546 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31548 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31549 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31550 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31551 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31552 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31555 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31557 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31560 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31565 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31577 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31579 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31585 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31590 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31592 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31594 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31595 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31596 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31599 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31603 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31605 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31606 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31610 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31615 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31616 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31617 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31618 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31619 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31623 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31624 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31625 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31628 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31630 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31634 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31637 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31642 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31648 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31651 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31655 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31658 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31660 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31661 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31662 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31664 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31665 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31667 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31670 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31671 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31672 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31673 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31674 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31675 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31676 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31677 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31678 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31679 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31680 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31681 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31682 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31684 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31687 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31689 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31692 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31698 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31699 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31701 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31704 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31721 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31722 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31723 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31724 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31725 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31726 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31737 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31738 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31749 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31752 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31754 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31755 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31756 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31758 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31762 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31763 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31767 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31770 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31771 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31773 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31777 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31779 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31781 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43009 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43010 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43013 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43014 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43016 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43017 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43018 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43022 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43024 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43025 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43026 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43028 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43032 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43033 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43035 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43036 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43041 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43042 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43043 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43046 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43048 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43054 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43057 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43058 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43060 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43061 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43062 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43064 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43065 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43066 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43068 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43069 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43071 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43072 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43073 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43077 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43079 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43080 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43083 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43085 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43088 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43089 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43091 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43093 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43094 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43098 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43099 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43101 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43103 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43104 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43105 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43107 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43111 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43112 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43113 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43114 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43115 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43118 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43119 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2008-2544 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-4915 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-4916 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-4917 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2014-9892 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2014-9900 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2016-10723 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2016-8660 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-13693 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-13694 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-12928 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-12378 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-12379 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-12380 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-12381 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-12382 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-12455 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-47432 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-4543 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-48669 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-31081 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-31085 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-4134 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52576 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52631 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52653 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52674 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52696 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52811 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52819 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53704 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53711 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53712 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53728 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53730 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53731 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53743 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53768 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53792 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53793 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53823 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53836 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53842 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53844 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53847 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53852 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53857 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53858 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53863 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54001 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54006 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54014 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54019 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54023 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54030 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54031 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54032 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54051 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54064 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54066 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54067 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54069 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54088 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54091 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54093 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54095 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54099 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54117 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54121 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54134 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54154 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54170 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54173 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54189 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54224 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54254 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54264 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54281 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54296 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54303 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54313 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54314 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54318 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54324 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54326 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26627 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26633 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26676 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26685 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26924 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26927 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26950 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26960 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27073 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27393 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35843 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35853 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35854 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35865 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35888 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35947 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35973 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35976 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36896 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36955 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38573 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38576 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39276 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-54458 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39990 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40010 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40042 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40049 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40057 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40088 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40092 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40094 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40099 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40100 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40103 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40105 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40125 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40196 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40205 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40219 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40253 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40346 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40360 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68171 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68173 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68194 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68200 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68204 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68206 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68218 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68219 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68227 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68233 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68244 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68288 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68295 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68308 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68321 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68334 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68336 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68345 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68363 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68378 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68732 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68734 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68753 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68758 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68778 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68780 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68783 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68785 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68794 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68795 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68798 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68813 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68818 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68820 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68822 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71194 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31486 | LOW2.8 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43030 | LOW2.8 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-4641 | LOW2.8 | login 1:4.13+dfsg1-1+b1 fixed in 1:4.13+dfsg1-1+deb12u1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.38.1-5+b1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6843 | LOW2.8 | nano 7.2-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-0727 | LOW2.8 | openssl 3.0.9-1 fixed in 3.0.13-1~deb12u1 | 0.2% 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-2023-4641 | LOW2.8 | passwd 1:4.13+dfsg1-1+b1 fixed in 1:4.13+dfsg1-1+deb12u1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-45261 | LOW2.8 | patch 2.7.6-7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2018-21232 | LOW2.8 | re2c 3.0-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-29088 | LOW2.8 | sqlite3 3.40.1-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.34+dfsg-1.2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-48303 | LOW2.8 | tar 1.34+dfsg-1.2 fixed in 1.34+dfsg-1.2+deb12u1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.38.1-5+b1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux-extra 2.38.1-5+b1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW2.8 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW2.8 | libperl5.36 5.36.0-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4016 | LOW2.8 | libproc2-0 2:4.0.2-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | libsqlite3-0 3.40.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | libsqlite3-dev 3.40.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 252.12-1~deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 252.12-1~deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 252.12-1~deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 252.12-1~deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8732 | LOW2.8 | libxml2 2.9.14+dfsg-1.3~deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-2379 | LOW2.75 | curl 7.88.1-10+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.38.1-5+b1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-46219 | LOW2.7 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u5 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-2004 | LOW2.7 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u6 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2023-6780 | LOW2.7 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-33600 | LOW2.7 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-0915 | LOW2.7 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4046 | LOW2.7 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-1010024 | LOW2.7 | libc-dev-bin 2.36-9+deb12u1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2019-1010025 | LOW2.7 | libc-dev-bin 2.36-9+deb12u1 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2023-6780 | LOW2.7 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-33600 | LOW2.7 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-0915 | LOW2.7 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4046 | LOW2.7 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-1010024 | LOW2.7 | libc6-dev 2.36-9+deb12u1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2019-1010025 | LOW2.7 | libc6-dev 2.36-9+deb12u1 No fix yet | 0.8% 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-2023-53713 | LOW2.7 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53726 | LOW2.7 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54092 | LOW2.7 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-24858 | LOW2.7 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-24860 | LOW2.7 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26886 | LOW2.7 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35857 | LOW2.7 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36881 | LOW2.7 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39968 | LOW2.7 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39972 | LOW2.7 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40204 | LOW2.7 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68367 | LOW2.7 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71225 | LOW2.7 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23457 | LOW2.7 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54181 | LOW2.7 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.38.1-5+b1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-2975 | LOW2.7 | openssl 3.0.9-1 fixed in 3.0.10-1~deb12u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-3446 | LOW2.7 | openssl 3.0.9-1 fixed in 3.0.10-1~deb12u1 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2023-3817 | LOW2.7 | openssl 3.0.9-1 fixed in 3.0.10-1~deb12u1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-5678 | LOW2.7 | openssl 3.0.9-1 fixed in 3.0.13-1~deb12u1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-4603 | LOW2.7 | openssl 3.0.9-1 fixed in 3.0.14-1~deb12u1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | 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-extra 2.38.1-5+b1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-34743 | LOW2.7 | xz-utils 5.4.1-0.2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53841 | LOW2.65 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39970 | LOW2.65 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40338 | LOW2.65 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40343 | LOW2.65 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-42119 | LOW2.63 | exim4-base 4.96-15+deb12u1 fixed in 4.96-15+deb12u3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-42119 | LOW2.63 | exim4-config 4.96-15+deb12u1 fixed in 4.96-15+deb12u3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-42119 | LOW2.63 | exim4-daemon-light 4.96-15+deb12u1 fixed in 4.96-15+deb12u3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-9232 | LOW2.63 | libssl-dev 3.0.9-1 fixed in 3.0.17-1~deb12u3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-9232 | LOW2.63 | libssl3 3.0.9-1 fixed in 3.0.17-1~deb12u3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53843 | LOW2.6 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40178 | LOW2.6 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71193 | LOW2.6 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23035 | LOW2.6 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2003-1581 | LOW2.6 | apache2 2.4.57-2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2008-0456 | LOW2.6 | apache2 2.4.57-2 No fix yet | 7.6% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1581 | LOW2.6 | apache2-bin 2.4.57-2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2008-0456 | LOW2.6 | apache2-bin 2.4.57-2 No fix yet | 7.6% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1581 | LOW2.6 | apache2-data 2.4.57-2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2008-0456 | LOW2.6 | apache2-data 2.4.57-2 No fix yet | 7.6% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1581 | LOW2.6 | apache2-utils 2.4.57-2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2008-0456 | LOW2.6 | apache2-utils 2.4.57-2 No fix yet | 7.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-57360 | LOW2.55 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5450 | LOW2.55 | libc-dev-bin 2.36-9+deb12u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5928 | LOW2.55 | libc-dev-bin 2.36-9+deb12u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5450 | LOW2.55 | libc6-dev 2.36-9+deb12u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5928 | LOW2.55 | libc6-dev 2.36-9+deb12u1 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-2023-52633 | LOW2.55 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40121 | LOW2.55 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23180 | LOW2.55 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2010-4563 | LOW2.55 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-34324 | LOW2.5 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2005-3660 | LOW2.5 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | login 1:4.13+dfsg1-1+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.13+dfsg1-1+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-0992 | LOW2.46 | libxml2 2.9.14+dfsg-1.3~deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | LOW2.45 | cpp-12 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-10148 | LOW2.45 | curl 7.88.1-10+deb12u1 No fix yet | 0.1% 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.2% Theoretical Threat | Post-Exploit |
| CVE-2023-4039 | LOW2.45 | gcc-12 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-4039 | LOW2.45 | gcc-12-base 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-4039 | LOW2.45 | libgcc-12-dev 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-4039 | LOW2.45 | libstdc++-12-dev 12.2.0-14 fixed in 12.2.0-14+deb12u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-24859 | LOW2.45 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <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.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl 7.88.1-10+deb12u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgv 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgv 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-20794 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-2898 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-31083 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-42756 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-46862 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52478 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52489 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52505 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52568 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52589 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52602 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52608 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52609 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52639 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52645 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52654 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.69-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52749 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.66-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52771 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53204 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53368 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53401 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53447 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53490 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53501 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53520 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53581 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53615 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53697 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53703 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53766 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53777 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53794 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53799 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53815 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53839 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53848 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53860 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53861 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54166 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54201 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-6176 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-2201 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-22386 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-23196 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-24855 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-24864 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26583 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26585 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26607 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26631 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26671 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26698 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26837 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26859 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26861 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26862 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26869 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26874 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26878 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26897 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26910 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26923 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27009 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27019 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27404 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27408 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27415 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-27419 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35809 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35848 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36024 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36028 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36927 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.140-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36949 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36952 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-37354 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38580 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38596 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38601 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38613 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38662 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39500 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-39508 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40905 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40943 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-40953 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41005 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41020 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42102 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42107 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42152 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42253 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42287 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43866 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43892 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-44954 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-45003 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46679 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46710 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46711 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46734 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46787 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46870 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47660 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47668 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47679 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49859 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49866 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49998 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50006 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50010 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50082 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50135 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50183 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50192 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53088 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53100 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53124 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53136 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53176 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53178 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56568 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56576 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56637 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56729 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57857 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57913 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57974 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21651 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21655 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21688 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.128-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21701 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.129-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21732 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21825 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21892 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21938 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21943 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21947 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.133-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22027 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22050 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22060 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22115 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23151 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37920 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37985 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38048 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38078 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38083 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38085 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38104 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38112 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38232 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38234 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38365 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38393 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38448 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38461 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38462 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38477 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38515 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38524 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38561 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38617 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.148-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38681 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38687 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38717 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39673 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39697 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39713 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39726 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39754 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39813 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39825 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.153-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39927 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39961 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39977 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39980 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39996 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40006 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40011 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40016 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40039 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40056 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40085 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40110 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40120 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40134 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40139 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40179 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40187 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40197 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40215 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40220 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40244 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40252 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40254 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40331 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40342 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68214 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68239 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68241 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68296 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68312 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68745 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71074 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71111 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23004 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23071 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23101 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23110 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23118 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23126 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23167 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23169 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23207 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23212 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23302 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23348 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23394 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23452 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23463 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31389 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31393 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31466 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31523 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31697 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31728 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31751 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43047 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43053 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-0630 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2019-16230 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-16234 | LOW2.4 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54026 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54035 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54042 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54185 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54289 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54309 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26915 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68264 | LOW2.4 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% 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.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68160 | LOW2.4 | openssl 3.0.9-1 fixed in 3.0.18-1~deb12u2 | <0.1% 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-2025-69644 | LOW2.38 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libbinutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf-nobfd0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libgprofng0 2.40-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-43167 | LOW2.38 | libunbound8 1.17.1-2 fixed in 1.17.1-2+deb12u3 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-15213 | LOW2.35 | linux-libc-dev 6.1.38-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-37453 | LOW2.35 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-4010 | LOW2.35 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-49934 | LOW2.35 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2012-4542 | LOW2.35 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54113 | LOW2.29 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40308 | LOW2.29 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40312 | LOW2.29 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-45896 | LOW2.29 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53831 | LOW2.29 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils 9.1-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-64505 | LOW2.24 | libpng-tools 1.6.39-2 fixed in 1.6.39-2+deb12u1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-34757 | LOW2.24 | libpng-tools 1.6.39-2 fixed in 1.6.39-2+deb12u5 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2020-14304 | LOW2.24 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-3772 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-3773 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-39194 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52508 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52585 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52617 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52627 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53722 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53733 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54155 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54253 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54263 | LOW2.24 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26810 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35845 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-36950 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38540 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38541 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.137-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42114 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42123 | LOW2.24 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42131 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42154 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42230 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46695 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-53052 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40001 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40081 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40206 | LOW2.24 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40281 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68768 | LOW2.24 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-17977 | LOW2.24 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52492 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52618 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52765 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52768 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52798 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52800 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52838 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52844 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52855 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52858 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52861 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52870 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52884 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53718 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54209 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54210 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54247 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26638 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26661 | LOW2.24 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26662 | LOW2.24 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26672 | LOW2.24 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26712 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26723 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26745 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26747 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26757 | LOW2.24 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26758 | LOW2.24 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26768 | LOW2.24 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26769 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26846 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26857 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26875 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36031 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36894 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.99-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36910 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36912 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36913 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36944 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38388 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38548 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38550 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38559 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-38605 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38616 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38628 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40021 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40123 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40183 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40198 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40200 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23458 | LOW2.24 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 2.6.1 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2511 | LOW2.22 | openssl 3.0.9-1 fixed in 3.0.14-1~deb12u1 | 4.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45446 | LOW2.22 | openssl 3.0.9-1 fixed in 3.0.20-1~deb12u2 | — | Post-Exploit |
| CVE-2023-47233 | LOW2.19 | linux-libc-dev 6.1.38-1 fixed in 6.1.85-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-6121 | LOW2.19 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2010-5321 | LOW2.19 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40275 | LOW2.19 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-45346 | LOW2.19 | sqlite3 3.40.1-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW2.16 | login 1:4.13+dfsg1-1+b1 No fix yet | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-56433 | LOW2.16 | passwd 1:4.13+dfsg1-1+b1 No fix yet | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-8058 | LOW2.14 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u13 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8058 | LOW2.14 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u13 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-41848 | LOW2.14 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-24515 | LOW2.12 | libexpat1 2.5.0-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.1% Theoretical Threat | Directly Exposed |
| CVE-2019-16089 | LOW2.09 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-3863 | LOW2.09 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52872 | LOW2.09 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-36928 | LOW2.09 | linux-libc-dev 6.1.38-1 fixed in 6.1.94-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42156 | LOW2.09 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42157 | LOW2.09 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42158 | LOW2.09 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42229 | LOW2.09 | linux-libc-dev 6.1.38-1 fixed in 6.1.98-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40173 | LOW2.09 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-16229 | LOW2.09 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-16231 | LOW2.09 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-16232 | LOW2.09 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-16233 | LOW2.09 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-0725 | LOW2.04 | curl 7.88.1-10+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2010-4756 | LOW2.04 | libc-dev-bin 2.36-9+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-33601 | LOW2.04 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-33602 | LOW2.04 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-4438 | LOW2.04 | libc-dev-bin 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2010-4756 | LOW2.04 | libc6-dev 2.36-9+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-33601 | LOW2.04 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-33602 | LOW2.04 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-4438 | LOW2.04 | libc6-dev 2.36-9+deb12u1 fixed in 2.36-9+deb12u14 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54229 | LOW2.04 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52597 | LOW2.04 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53708 | LOW2.04 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53994 | LOW2.04 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| 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.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-38546 | LOW1.89 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-9143 | LOW1.89 | openssl 3.0.9-1 fixed in 3.0.15-1~deb12u1 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2001-1534 | LOW1.78 | apache2 2.4.57-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2001-1534 | LOW1.78 | apache2-bin 2.4.57-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2001-1534 | LOW1.78 | apache2-data 2.4.57-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2001-1534 | LOW1.78 | apache2-utils 2.4.57-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2020-35501 | LOW1.73 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68740 | LOW1.73 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgv 2.2.40-1.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68191 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2015-2877 | LOW1.68 | linux-libc-dev 6.1.38-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52561 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52571 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.64-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52926 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.123-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53763 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53992 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53998 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54083 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54127 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54145 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54153 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54171 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54172 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54177 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54194 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54211 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54220 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54221 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54227 | LOW1.68 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54230 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54233 | LOW1.68 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54235 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54282 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54315 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54322 | LOW1.68 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26612 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26614 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.76-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26764 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-26992 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-35935 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41007 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-41027 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43841 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.106-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-46794 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.112-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-47738 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50044 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.115-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50057 | LOW1.68 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50211 | LOW1.68 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50280 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.119-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39964 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40035 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40268 | LOW1.68 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40303 | LOW1.68 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40341 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68746 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68782 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71224 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22978 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31668 | LOW1.68 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-29383 | LOW1.68 | login 1:4.13+dfsg1-1+b1 fixed in 1:4.13+dfsg1-1+deb12u1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-29383 | LOW1.68 | passwd 1:4.13+dfsg1-1+b1 fixed in 1:4.13+dfsg1-1+deb12u1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl 5.36.0-7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-base 5.36.0-7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-modules-5.36 5.36.0-7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-4016 | LOW1.68 | procps 2:4.0.2-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-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.1% Theoretical Threat | Post-Exploit |
| CVE-2023-39804 | LOW1.68 | tar 1.34+dfsg-1.2 fixed in 1.34+dfsg-1.2+deb12u1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-4217 | LOW1.68 | unzip 6.0-28 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-9232 | LOW1.58 | openssl 3.0.9-1 fixed in 3.0.17-1~deb12u3 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-common 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-11191 | LOW1.27 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-52620 | LOW1.27 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54246 | LOW1.27 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54267 | LOW1.27 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54283 | LOW1.27 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54312 | LOW1.27 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54316 | LOW1.27 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68788 | LOW1.27 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6842 | LOW1.27 | nano 7.2-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2007-3719 | LOW1.07 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-42155 | LOW0.97 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | NONE0 | libncursesw6 6.4-4 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6020 | NONE0 | libpam-modules 1.5.2-6 fixed in 1.5.2-6+deb12u2 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6020 | NONE0 | libpam-modules-bin 1.5.2-6 fixed in 1.5.2-6+deb12u2 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6020 | NONE0 | libpam-runtime 1.5.2-6 fixed in 1.5.2-6+deb12u2 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6020 | NONE0 | libpam0g 1.5.2-6 fixed in 1.5.2-6+deb12u2 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.4-4 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.4-4 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.4-4 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libncursesw6 6.4-4 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libtinfo6 6.4-4 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.4-4 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-bin 6.4-4 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam-modules 1.5.2-6 fixed in 1.5.2-6+deb12u2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam-modules-bin 1.5.2-6 fixed in 1.5.2-6+deb12u2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam-runtime 1.5.2-6 fixed in 1.5.2-6+deb12u2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam0g 1.5.2-6 fixed in 1.5.2-6+deb12u2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-modules 1.5.2-6 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-modules-bin 1.5.2-6 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-runtime 1.5.2-6 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam0g 1.5.2-6 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncursesw6 6.4-4 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.4-4 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.4-4 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-bin 6.4-4 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-29167 | NONE0 | apache2 2.4.57-2 No fix yet | — | Not Applicable |
| CVE-2026-34355 | NONE0 | apache2 2.4.57-2 No fix yet | — | Not Applicable |
| CVE-2026-34356 | NONE0 | apache2 2.4.57-2 No fix yet | — | Not Applicable |
| CVE-2026-42536 | NONE0 | apache2 2.4.57-2 No fix yet | — | Not Applicable |
| CVE-2026-44185 | NONE0 | apache2 2.4.57-2 No fix yet | — | Not Applicable |
| CVE-2026-44186 | NONE0 | apache2 2.4.57-2 No fix yet | — | Not Applicable |
| CVE-2026-48913 | NONE0 | apache2 2.4.57-2 No fix yet | — | Not Applicable |
| CVE-2026-43951 | NONE0 | apache2 2.4.57-2 No fix yet | — | Not Applicable |
| DSA-5729-2 | NONE0 | apache2 2.4.57-2 fixed in 2.4.62-1~deb12u2 | — | Not Applicable |
| CVE-2026-29167 | NONE0 | apache2-bin 2.4.57-2 No fix yet | — | Not Applicable |
| CVE-2026-34355 | NONE0 | apache2-bin 2.4.57-2 No fix yet | — | Not Applicable |
| CVE-2026-34356 | NONE0 | apache2-bin 2.4.57-2 No fix yet | — | Not Applicable |
| CVE-2026-42536 | NONE0 | apache2-bin 2.4.57-2 No fix yet | — | Not Applicable |
| CVE-2026-44185 | NONE0 | apache2-bin 2.4.57-2 No fix yet | — | Not Applicable |
| CVE-2026-44186 | NONE0 | apache2-bin 2.4.57-2 No fix yet | — | Not Applicable |
| CVE-2026-48913 | NONE0 | apache2-bin 2.4.57-2 No fix yet | — | Not Applicable |
| CVE-2026-43951 | NONE0 | apache2-bin 2.4.57-2 No fix yet | — | Not Applicable |
| DSA-5729-2 | NONE0 | apache2-bin 2.4.57-2 fixed in 2.4.62-1~deb12u2 | — | Not Applicable |
| CVE-2026-29167 | NONE0 | apache2-data 2.4.57-2 No fix yet | — | Not Applicable |
| CVE-2026-34355 | NONE0 | apache2-data 2.4.57-2 No fix yet | — | Not Applicable |
| CVE-2026-34356 | NONE0 | apache2-data 2.4.57-2 No fix yet | — | Not Applicable |
| CVE-2026-42536 | NONE0 | apache2-data 2.4.57-2 No fix yet | — | Not Applicable |
| CVE-2026-44185 | NONE0 | apache2-data 2.4.57-2 No fix yet | — | Not Applicable |
| CVE-2026-44186 | NONE0 | apache2-data 2.4.57-2 No fix yet | — | Not Applicable |
| CVE-2026-48913 | NONE0 | apache2-data 2.4.57-2 No fix yet | — | Not Applicable |
| CVE-2026-43951 | NONE0 | apache2-data 2.4.57-2 No fix yet | — | Not Applicable |
| DSA-5729-2 | NONE0 | apache2-data 2.4.57-2 fixed in 2.4.62-1~deb12u2 | — | Not Applicable |
| CVE-2026-29167 | NONE0 | apache2-utils 2.4.57-2 No fix yet | — | Not Applicable |
| CVE-2026-34355 | NONE0 | apache2-utils 2.4.57-2 No fix yet | — | Not Applicable |
| CVE-2026-34356 | NONE0 | apache2-utils 2.4.57-2 No fix yet | — | Not Applicable |
| CVE-2026-42536 | NONE0 | apache2-utils 2.4.57-2 No fix yet | — | Not Applicable |
| CVE-2026-44185 | NONE0 | apache2-utils 2.4.57-2 No fix yet | — | Not Applicable |
| CVE-2026-44186 | NONE0 | apache2-utils 2.4.57-2 No fix yet | — | Not Applicable |
| CVE-2026-48913 | NONE0 | apache2-utils 2.4.57-2 No fix yet | — | Not Applicable |
| CVE-2026-43951 | NONE0 | apache2-utils 2.4.57-2 No fix yet | — | 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-2025-0167 | NONE0 | curl 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u11 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-2219 | NONE0 | dpkg 1.21.22 fixed in 1.21.23 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6297 | NONE0 | dpkg 1.21.22 fixed in 1.21.23 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-2219 | NONE0 | dpkg-dev 1.21.22 fixed in 1.21.23 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6297 | NONE0 | dpkg-dev 1.21.22 fixed in 1.21.23 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45185 | NONE0 | exim4-base 4.96-15+deb12u1 fixed in 4.96-15+deb12u9 | — | Not Applicable |
| CVE-2026-48840 | NONE0 | exim4-base 4.96-15+deb12u1 fixed in 4.96-15+deb12u10 | — | Not Applicable |
| CVE-2026-45185 | NONE0 | exim4-config 4.96-15+deb12u1 fixed in 4.96-15+deb12u9 | — | Not Applicable |
| CVE-2026-48840 | NONE0 | exim4-config 4.96-15+deb12u1 fixed in 4.96-15+deb12u10 | — | Not Applicable |
| CVE-2026-45185 | NONE0 | exim4-daemon-light 4.96-15+deb12u1 fixed in 4.96-15+deb12u9 | — | Not Applicable |
| CVE-2026-48840 | NONE0 | exim4-daemon-light 4.96-15+deb12u1 fixed in 4.96-15+deb12u10 | — | Not Applicable |
| CVE-2025-0167 | NONE0 | libcurl4 7.88.1-10+deb12u1 fixed in 7.88.1-10+deb12u11 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-2219 | NONE0 | libdpkg-perl 1.21.22 fixed in 1.21.23 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6297 | NONE0 | libdpkg-perl 1.21.22 fixed in 1.21.23 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42014 | NONE0 | libgnutls-dane0 3.7.9-2 fixed in 3.7.9-2+deb12u7 | — | Not Applicable |
| CVE-2026-42014 | NONE0 | libgnutls30 3.7.9-2 fixed in 3.7.9-2+deb12u7 | — | Not Applicable |
| CVE-2026-48959 | NONE0 | libperl5.36 5.36.0-7 No fix yet | — | Not Applicable |
| CVE-2025-15649 | NONE0 | libperl5.36 5.36.0-7 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | libperl5.36 5.36.0-7 No fix yet | — | Not Applicable |
| CVE-2026-48961 | NONE0 | libperl5.36 5.36.0-7 No fix yet | — | Not Applicable |
| CVE-2025-7709 | 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.1% Theoretical Threat | Not Applicable |
| CVE-2025-27587 | NONE0 | libssl-dev 3.0.9-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-27587 | NONE0 | libssl3 3.0.9-1 No fix yet | 0.2% Theoretical Threat | 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.1% Theoretical Threat | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | 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-31405 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31478 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31657 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31659 | 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 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53693 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53699 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53707 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53714 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53725 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53727 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53732 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53782 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53801 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53807 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53817 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53834 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53855 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53865 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54005 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54017 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54025 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54049 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54104 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54112 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54115 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54125 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54140 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54142 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54143 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54178 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54183 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54196 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54219 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54225 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54240 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54241 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54255 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54266 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54272 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.82-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54293 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54297 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54304 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54319 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% 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.2% Theoretical Threat | Not Applicable |
| CVE-2025-37838 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.135-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39985 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39986 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39987 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39988 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39995 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40003 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40008 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40013 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40022 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40032 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40036 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40043 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40055 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40060 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40062 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40068 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40077 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40084 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40087 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40093 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40095 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40097 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40106 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40107 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40112 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40116 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40124 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40126 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40127 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40137 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40156 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40180 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40188 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40193 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40202 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40207 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40223 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40233 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40243 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40245 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40262 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40263 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40266 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40278 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40282 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40285 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40286 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40288 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40289 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40306 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40311 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40313 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40314 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40315 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40317 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40333 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40337 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40354 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40358 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68177 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68190 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68201 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68217 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68220 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68238 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68246 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68249 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.158-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68254 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68255 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68256 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68257 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68258 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68263 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68266 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68286 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68289 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68290 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68302 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68303 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68315 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68320 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68322 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68325 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68327 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68328 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68330 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68332 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68335 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68339 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.159-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68344 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68364 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68369 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68727 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68728 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68733 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68750 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.147-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68759 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68765 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68766 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68767 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68769 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68771 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68772 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68773 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68777 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68781 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68786 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68787 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68796 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68797 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68799 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68804 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68806 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68808 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68809 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71065 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71067 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71069 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71192 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71196 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71197 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71198 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71199 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71304 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-23030 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23033 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23037 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23049 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23056 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.162-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23176 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23182 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% 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-23281 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-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.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-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.1% Theoretical Threat | Not Applicable |
| CVE-2026-23407 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.164-1 | <0.1% 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.1% Theoretical Threat | Not Applicable |
| CVE-2026-31417 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31432 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31433 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31476 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31477 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% 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.1% Theoretical Threat | Not Applicable |
| CVE-2026-31587 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31597 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31598 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31602 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31611 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31612 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31622 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31626 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31627 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31629 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <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-31683 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | <0.1% 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-31706 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <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 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31712 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31716 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <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-31768 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-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 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43076 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43117 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43184 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-43203 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-43206 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-43207 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-43212 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-43232 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-43236 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-43249 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-43256 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-43258 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-43283 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-43291 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-43324 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-43336 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-43370 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-43373 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-43377 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-43476 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-43480 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-43490 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-43495 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-43497 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-43499 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-45839 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-45848 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45849 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45850 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-45864 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45865 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45866 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45867 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45869 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45875 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45879 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45881 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45883 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45885 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45890 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45893 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-45902 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45916 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45924 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45930 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-45935 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45936 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-45946 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45954 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45957 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-45958 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45965 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45969 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45978 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-45986 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-45993 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46006 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46009 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46019 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46031 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46044 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46058 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46062 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46072 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46075 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46077 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46080 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46091 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46098 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46108 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46109 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46110 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46112 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46122 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46124 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46128 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46129 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46143 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46164 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46177 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46197 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46198 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46199 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46204 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46205 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46206 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46208 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46212 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46218 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46230 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46238 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46303 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46314 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46328 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-46250 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-46265 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-46270 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.170-1 | — | Not Applicable |
| CVE-2026-46276 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46282 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46285 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46293 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46296 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | Not Applicable |
| CVE-2026-46301 | NONE0 | linux-libc-dev 6.1.38-1 No fix yet | — | 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.1% Theoretical Threat | Not Applicable |
| CVE-2023-53864 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.55-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54000 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54027 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54101 | NONE0 | linux-libc-dev 6.1.38-1 fixed in 6.1.52-1 | <0.1% Theoretical Threat | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login 1:4.13+dfsg1-1+b1 No fix yet | — | Not Applicable |
| CVE-2025-27587 | NONE0 | openssl 3.0.9-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.13+dfsg1-1+b1 No fix yet | — | Not Applicable |
| CVE-2026-48959 | NONE0 | perl 5.36.0-7 No fix yet | — | Not Applicable |
| CVE-2025-15649 | NONE0 | perl 5.36.0-7 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl 5.36.0-7 No fix yet | — | Not Applicable |
| CVE-2026-48961 | NONE0 | perl 5.36.0-7 No fix yet | — | Not Applicable |
| CVE-2026-48959 | NONE0 | perl-base 5.36.0-7 No fix yet | — | Not Applicable |
| CVE-2025-15649 | NONE0 | perl-base 5.36.0-7 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.36.0-7 No fix yet | — | Not Applicable |
| CVE-2026-48961 | NONE0 | perl-base 5.36.0-7 No fix yet | — | Not Applicable |
| CVE-2026-48959 | NONE0 | perl-modules-5.36 5.36.0-7 No fix yet | — | Not Applicable |
| CVE-2025-15649 | NONE0 | perl-modules-5.36 5.36.0-7 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-modules-5.36 5.36.0-7 No fix yet | — | Not Applicable |
| CVE-2026-48961 | NONE0 | perl-modules-5.36 5.36.0-7 No fix yet | — | Not Applicable |
| CVE-2025-7709 | 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-2025-45769 | NONE0 | firebase/php-jwt v6.8.1 fixed in 7.0.0 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-49214 | NONE0 | guzzlehttp/psr7 2.5.0 fixed in 2.10.2 | — | Not Applicable |
| CVE-2026-45133 | NONE0 | symfony/yaml v6.3.3 fixed in 6.4.40, 7.4.0, 5.1.0, 5.2.0, 7.4.12, 5.0.0, 5.3.0, 6.2.0, 7.1.0, 7.2.0, 7.3.0, 8.0.12, 3.0.0, 4.0.0, 5.4.0, 6.1.0, 6.3.0, 5.4.52, 6.4.0 | — | Not Applicable |
| CVE-2026-45304 | NONE0 | symfony/yaml v6.3.3 fixed in 4.0.0, 5.0.0, 6.4.40, 7.1.0, 7.4.12, 5.3.0, 5.4.52, 7.2.0, 5.2.0, 6.1.0, 7.4.0, 8.0.12, 3.0.0, 5.1.0, 5.4.0, 6.2.0, 6.3.0, 6.4.0, 7.3.0 | — | Not Applicable |
| CVE-2026-45305 | NONE0 | symfony/yaml v6.3.3 fixed in 5.2.0, 5.3.0, 6.3.0, 6.4.40, 7.4.12, 3.0.0, 5.1.0, 6.4.0, 7.1.0, 7.3.0, 7.4.0, 8.0.12, 4.0.0, 5.0.0, 6.2.0, 7.2.0, 5.4.0, 5.4.52, 6.1.0 | — | 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 |