Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker with network access could potentially corrupt data or read/write arbitrary files via Perl and Archive::Tar vulnerabilities (CVE-2026-13221, CVE-2026-42496), while CVE-2022-25265 might enable local privilege escalation if a foothold is gained. With 1,624 exposed vulnerabilities and 26 high-severity findings, the attack surface is broad. Upgrading the base OS packages (e.g., glibc, perl, sqlite) would eliminate the cited vulnerabilities.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2022-25265 | HIGH7.8 | linux-libc-dev 6.1.177-1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-13221 | HIGH7.73 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | HIGH7.73 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-7458 | HIGH7.73 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-bin 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-bin 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6-dev 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6-dev 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28757 | HIGH7.5 | libexpat1 2.5.0-1+deb12u2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2018-6829 | HIGH7.5 | libgcrypt20 1.10.1-3+deb12u1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2953 | HIGH7.5 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2015-3276 | HIGH7.5 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | HIGH7.5 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19070 | HIGH7.5 | linux-libc-dev 6.1.177-1 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0400 | HIGH7.5 | linux-libc-dev 6.1.177-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-22037 | HIGH7.15 | linux-libc-dev 6.1.177-1 No fix yet | 65.7% Actively Exploited | Directly Exposed |
| CVE-2026-57432 | HIGH7.14 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63797 | HIGH7.14 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-39191 | MEDIUM6.97 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6653 | MEDIUM6.66 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-11082 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25210 | MEDIUM6.63 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48962 | MEDIUM6.63 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11979 | MEDIUM6.63 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-3847 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-52452 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52624 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-52751 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53218 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-21803 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-26836 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26913 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26914 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26944 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35887 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38570 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38630 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41045 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42118 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44941 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44942 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44951 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46729 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46811 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46813 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47691 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50029 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50217 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50226 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50282 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53068 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53168 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53179 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53218 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56538 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56775 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57900 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-21927 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-21967 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-21969 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23133 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37750 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-37777 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37861 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37952 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37957 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38069 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38117 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38182 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38206 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38248 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-38369 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38582 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38585 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38595 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38722 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38734 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-39797 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39810 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39859 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39952 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71068 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-71073 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71152 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23171 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23208 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23226 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23361 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23447 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23448 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31493 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31527 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31729 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43049 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43250 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46068 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46219 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46241 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53089 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53115 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53117 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53118 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53120 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53129 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53143 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53156 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53262 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53272 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64530 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64531 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64600 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46274 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-12456 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-11725 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-26934 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3238 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-26242 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-3640 | MEDIUM6.63 | linux-libc-dev 6.1.177-1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-21759 | MEDIUM6.6 | linux-libc-dev 6.1.177-1 No fix yet | 7.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libbinutils 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libctf-nobfd0 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libctf0 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libgprofng0 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2004-0230 | MEDIUM6.5 | linux-libc-dev 6.1.177-1 No fix yet | 80.3% Actively Exploited | Directly Exposed |
| CVE-2026-56208 | MEDIUM6.46 | libaom3 3.6.0-1+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-39616 | MEDIUM6.38 | libaom3 3.6.0-1+deb12u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45186 | MEDIUM6.38 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42497 | MEDIUM6.38 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM6.38 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40170 | MEDIUM6.29 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2007-0086 | MEDIUM6.24 | apache2 2.4.68-1~deb12u1 No fix yet | 9.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2007-0086 | MEDIUM6.24 | apache2-bin 2.4.68-1~deb12u1 No fix yet | 9.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-53781 | MEDIUM6.21 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39981 | MEDIUM6.21 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43248 | MEDIUM6.21 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54369 | MEDIUM6.03 | libacl1 2.3.1-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56209 | MEDIUM6.03 | libaom3 3.6.0-1+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56210 | MEDIUM6.03 | libaom3 3.6.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56211 | MEDIUM6.03 | libaom3 3.6.0-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26669 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41935 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53147 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57982 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21985 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22039 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-22104 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38081 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38204 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38616 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38636 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39744 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39901 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23327 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31568 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45893 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45943 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45957 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46130 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46293 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53179 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53330 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-14040 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-25742 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-25743 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36013 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-53216 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40064 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68183 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68324 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43126 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43414 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46135 | MEDIUM6.03 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-3864 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-52586 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42162 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37776 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23191 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31419 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31663 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43125 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43198 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46054 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46181 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52991 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53000 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53091 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53399 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63829 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63962 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64017 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64026 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64268 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-64271 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64276 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64277 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64296 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64303 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-64304 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64364 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64375 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64378 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64434 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64483 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64534 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64552 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64556 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53762 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57984 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40158 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40168 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-40328 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23050 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45859 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45894 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45942 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46090 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46204 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46266 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46324 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46330 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52956 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53005 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53009 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53053 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53078 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53132 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53185 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53224 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53230 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53246 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53361 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53392 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63826 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63940 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64001 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64025 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64109 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64160 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64189 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64192 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64266 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64280 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64298 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64305 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64306 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64312 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64317 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64319 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64320 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-64322 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64323 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64324 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64340 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64341 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64342 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64355 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64372 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64379 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64380 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64401 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64422 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64448 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64456 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64470 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64471 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64475 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64481 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64508 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64539 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64543 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64548 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64551 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64554 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64557 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64560 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-1247 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-2961 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-45884 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-45885 | MEDIUM5.95 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libbinutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libctf-nobfd0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libctf0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt20 1.10.1-3+deb12u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libgprofng0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1-6 4.19.0-2+deb12u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-1121 | MEDIUM5.9 | linux-libc-dev 6.1.177-1 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3714 | MEDIUM5.9 | linux-libc-dev 6.1.177-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56132 | MEDIUM5.87 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM5.87 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56404 | MEDIUM5.87 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56405 | MEDIUM5.87 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM5.87 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56407 | MEDIUM5.87 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56410 | MEDIUM5.87 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56411 | MEDIUM5.87 | libexpat1 2.5.0-1+deb12u2 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-2020-36694 | MEDIUM5.7 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-21264 | MEDIUM5.7 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53095 | MEDIUM5.7 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57795 | MEDIUM5.7 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21714 | MEDIUM5.7 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53267 | MEDIUM5.61 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libbinutils 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libbinutils 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf-nobfd0 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libctf-nobfd0 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf0 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libctf0 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libgprofng0 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libgprofng0 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-15649 | MEDIUM5.52 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-6240 | MEDIUM5.52 | linux-libc-dev 6.1.177-1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-36968 | MEDIUM5.52 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43239 | MEDIUM5.52 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64535 | MEDIUM5.52 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-0564 | MEDIUM5.52 | linux-libc-dev 6.1.177-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libbinutils 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libbinutils 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libbinutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf-nobfd0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libctf-nobfd0 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libctf-nobfd0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libctf0 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libctf0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libgprofng0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libgprofng0 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libgprofng0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2193 | MEDIUM5.5 | linux-libc-dev 6.1.177-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-40074 | MEDIUM5.44 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23383 | MEDIUM5.44 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31502 | MEDIUM5.44 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31516 | MEDIUM5.44 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53090 | MEDIUM5.44 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-44032 | MEDIUM5.44 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-44033 | MEDIUM5.44 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-44034 | MEDIUM5.44 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54370 | MEDIUM5.35 | libacl1 2.3.1-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | MEDIUM5.35 | libattr1 1:2.5.1-4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-3397 | MEDIUM5.35 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40307 | MEDIUM5.35 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-40918 | MEDIUM5.35 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-bin 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-bin 2.36-9+deb12u14 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6 2.36-9+deb12u14 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6-dev 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6-dev 2.36-9+deb12u14 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-59375 | MEDIUM5.3 | libexpat1 2.5.0-1+deb12u2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-45440 | MEDIUM5.3 | drupal/core 9.8.0 fixed in 10.3.6, 11.0.5, 10.2.9 | 9.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-45440 | MEDIUM5.3 | drupal/core-recommended 9.8.0 fixed in 10.3.6, 11.0.5, 10.2.9 | 9.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | libp11-kit0 0.24.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-28162 | MEDIUM5.27 | libpng16-16 1.6.39-2+deb12u5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40146 | MEDIUM5.27 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40071 | MEDIUM5.18 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40355 | MEDIUM5.18 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68342 | MEDIUM5.18 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68736 | MEDIUM5.18 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31505 | MEDIUM5.18 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-32570 | MEDIUM5.02 | libdav1d6 1.0.0-2+deb12u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | MEDIUM5.02 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56412 | MEDIUM5.02 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2010-4563 | MEDIUM5 | linux-libc-dev 6.1.177-1 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-53706 | MEDIUM4.93 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54107 | MEDIUM4.93 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54141 | MEDIUM4.93 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23239 | MEDIUM4.93 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23240 | MEDIUM4.93 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-49569 | MEDIUM4.84 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-23039 | MEDIUM4.84 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libbinutils 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | 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.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | 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.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | 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.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | MEDIUM4.76 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-0630 | MEDIUM4.7 | linux-libc-dev 6.1.177-1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libasan8 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libatomic1 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libcc1-0 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32776 | MEDIUM4.67 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | MEDIUM4.67 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | MEDIUM4.67 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52426 | MEDIUM4.67 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc-12-dev 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgomp1 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libitm1 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | liblsan0 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | MEDIUM4.67 | libpng16-16 1.6.39-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libquadmath0 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-29088 | MEDIUM4.67 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libstdc++-12-dev 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libtsan2 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libubsan1 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-0597 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-23005 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31082 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-37454 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-4133 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52485 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52590 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52591 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52625 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52629 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52648 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52671 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52676 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52761 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52770 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52797 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52888 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52920 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53149 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53231 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53261 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53336 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53353 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53367 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53394 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53429 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53460 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53491 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53523 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53529 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53538 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53574 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53627 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53846 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53999 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54013 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54280 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-6039 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-25740 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26670 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26677 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26691 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26740 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26756 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26799 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26841 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26866 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26876 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26902 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26947 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26948 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26953 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26962 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27010 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27011 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27041 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27057 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27062 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27079 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35784 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35794 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35799 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35808 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35860 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35904 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35924 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35931 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35942 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35945 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35946 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35951 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35961 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36911 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36951 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38557 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38564 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38594 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38608 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38620 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38622 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38625 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40965 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40969 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40975 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40998 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40999 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41008 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41023 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41031 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41082 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42128 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42139 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42239 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42241 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42243 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42279 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42317 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43819 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43824 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43850 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43872 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-43899 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43901 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43913 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44963 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45015 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46678 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46681 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46698 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46727 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46728 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46730 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46754 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46760 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46765 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46775 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46776 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46806 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46808 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46834 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46860 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47141 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47658 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47661 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47662 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47664 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47703 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47752 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47794 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49568 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49893 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49901 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49906 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49908 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49910 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49914 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49916 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49918 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49919 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49920 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49921 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49922 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49923 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49926 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49940 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49945 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49970 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49988 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50009 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50017 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50028 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50111 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50166 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50285 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50289 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-52559 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-52560 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53051 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53056 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53079 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53085 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53089 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53090 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53091 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53094 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53114 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53134 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53187 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53195 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53219 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53224 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53687 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-54683 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56544 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56565 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56566 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56583 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56588 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56591 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56592 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56611 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56641 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56692 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56712 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56742 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57804 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57809 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57872 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57888 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57975 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57976 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57999 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58006 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58012 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58053 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58089 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58094 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58095 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58096 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58097 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58098 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58100 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58237 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58241 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21634 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21635 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21649 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21656 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21658 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21673 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-21693 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21696 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21723 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21729 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21768 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21801 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21831 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21836 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21870 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21872 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21885 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-21888 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21894 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21907 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21949 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21955 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-21961 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-21972 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21976 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22028 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22043 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-22048 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22053 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22057 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22070 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22103 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22109 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22113 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22125 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22127 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23129 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23130 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23132 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37747 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37800 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37802 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37806 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37807 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37833 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37834 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37842 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37853 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37856 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37860 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37880 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37893 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37956 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37977 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38006 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38014 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38029 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38038 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38039 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38041 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38042 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38045 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38059 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38064 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38080 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38096 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38127 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38132 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38140 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38195 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38203 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38207 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38237 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38244 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38246 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-38261 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38264 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-38272 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38283 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38311 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38333 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38359 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38426 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38429 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-38438 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38449 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38507 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38531 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38544 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38590 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-38597 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38615 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38692 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38705 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38709 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38716 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39677 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39705 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39707 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39720 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-39732 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39746 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39747 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39762 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39767 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39779 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39789 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39829 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39833 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39850 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39851 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-39886 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39910 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39925 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39932 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-39933 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39940 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39947 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39989 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40075 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40102 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40160 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40325 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40339 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68188 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68209 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68236 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68304 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68379 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71109 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71129 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71138 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71160 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71184 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71188 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71202 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71227 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71272 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71273 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71285 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71289 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-71313 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71315 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22996 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23000 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23088 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23137 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23138 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23213 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23214 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23247 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23265 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23276 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23330 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23346 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23371 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23374 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23419 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23465 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23472 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31410 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31420 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31458 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31462 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31487 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31531 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31537 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31557 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31560 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31579 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31592 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31606 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31610 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31648 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31655 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31675 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31677 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31692 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31722 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31723 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31724 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31725 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31767 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31771 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31777 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43009 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43010 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43016 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43022 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43036 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43042 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43048 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43073 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43083 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43088 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43091 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43101 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43107 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43115 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43118 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43119 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43129 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43137 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43153 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43161 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43167 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43170 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43172 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43173 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43204 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43213 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43215 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43216 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43234 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43244 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43271 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43288 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43299 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43308 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43309 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43310 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43317 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43318 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43338 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43344 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43352 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43353 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43362 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43409 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43413 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43416 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43419 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43443 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43456 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43491 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45855 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45858 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45877 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45892 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45897 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45899 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45901 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45917 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45934 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45940 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45944 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45961 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45963 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45981 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45985 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45988 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45993 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46000 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46012 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46014 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46032 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46059 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46071 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46111 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46147 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46148 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46153 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46156 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46157 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46158 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46170 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46200 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46225 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46226 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46229 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46245 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46254 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46282 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46302 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46312 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52936 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52937 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52944 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52961 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52988 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52990 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53015 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53017 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53018 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53027 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53070 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53076 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53083 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53102 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53106 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53107 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53122 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53220 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53226 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53229 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53232 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53237 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53258 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53265 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53285 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53292 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53297 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53313 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53317 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53332 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53345 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53353 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53358 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53376 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53377 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53393 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53400 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53402 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63847 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63848 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63854 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63856 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63858 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63963 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63983 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64006 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64036 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64038 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64076 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64077 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64079 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64112 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64190 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64206 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64210 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64212 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64279 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64299 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64313 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64315 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64316 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64329 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64330 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64333 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64336 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64338 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64343 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64344 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64346 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64347 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64351 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64360 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64362 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64363 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64365 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64373 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64374 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64381 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64403 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64406 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64408 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64409 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64411 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64412 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64413 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64423 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64424 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64436 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64452 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64454 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64455 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64458 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64463 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64472 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64478 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64487 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64496 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64507 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64510 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64540 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64541 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64542 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64545 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64546 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64547 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64553 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2008-2544 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2011-4915 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2011-4916 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2011-4917 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2014-9892 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2014-9900 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2016-10723 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-8660 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-13693 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-13694 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-12928 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12378 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12379 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12380 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-12381 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12382 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-12455 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-4543 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-31081 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31085 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-4134 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52653 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-53823 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53857 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54030 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54088 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35843 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39990 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40057 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40196 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68219 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68334 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68378 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68794 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-68822 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31486 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43253 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53284 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63810 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63845 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63846 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63853 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63855 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63871 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63872 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63974 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63999 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64060 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64078 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64144 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64146 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64163 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64187 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64213 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64275 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64294 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64297 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64301 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64332 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64334 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64335 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64352 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64370 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64376 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64388 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64417 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64419 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64428 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64430 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64435 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64465 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64476 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64480 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64482 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64486 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64488 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64489 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64512 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64513 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64514 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64537 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64544 | MEDIUM4.67 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7598 | MEDIUM4.64 | libssh2-1 1.10.0-3+b1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | MEDIUM4.64 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | MEDIUM4.64 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58055 | MEDIUM4.59 | libnghttp2-14 1.52.0-1+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2008-1687 | MEDIUM4.5 | m4 1.4.19-3 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2008-1688 | MEDIUM4.5 | m4 1.4.19-3 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6951 | MEDIUM4.5 | patch 2.7.6-7 No fix yet | 8.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6952 | MEDIUM4.5 | patch 2.7.6-7 No fix yet | 8.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1147 | MEDIUM4.5 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-12087 | MEDIUM4.5 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3713 | MEDIUM4.5 | libpng16-16 1.6.39-2+deb12u5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | libssl3 3.0.20-1~deb12u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libudev1 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libudev1 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libudev1 252.39-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-36881 | MEDIUM4.5 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71225 | MEDIUM4.5 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64538 | MEDIUM4.5 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40338 | MEDIUM4.42 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71193 | MEDIUM4.33 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23035 | MEDIUM4.33 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2003-1307 | MEDIUM4.3 | apache2 2.4.68-1~deb12u1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1580 | MEDIUM4.3 | apache2 2.4.68-1~deb12u1 No fix yet | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1307 | MEDIUM4.3 | apache2-bin 2.4.68-1~deb12u1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1580 | MEDIUM4.3 | apache2-bin 2.4.68-1~deb12u1 No fix yet | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-45346 | MEDIUM4.3 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-57432 | MEDIUM4.28 | perl 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | MEDIUM4.28 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | MEDIUM4.28 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM4.25 | libbz2-1.0 1.0.8-5+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48959 | MEDIUM4.25 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48961 | MEDIUM4.25 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-28164 | MEDIUM4.25 | libpng16-16 1.6.39-2+deb12u5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2020-15719 | MEDIUM4.2 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3303 | MEDIUM4.17 | apache2 2.4.68-1~deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2007-3303 | MEDIUM4.17 | apache2-bin 2.4.68-1~deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2005-3660 | MEDIUM4.17 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8286 | MEDIUM4.13 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | MEDIUM4 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-20794 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-52771 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53447 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-24864 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26869 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27408 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36024 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36949 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39508 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42107 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46787 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46870 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-50135 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53176 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53178 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56729 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57857 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57974 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21651 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21732 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21825 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21892 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22115 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38234 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38524 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-38717 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39726 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39754 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39927 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39961 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40139 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68296 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68745 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-71074 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23004 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23118 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23207 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23348 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23394 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43053 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45949 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46017 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53108 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-16230 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16234 | MEDIUM4 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-bin 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6-dev 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-11082 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18220 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18220 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18220 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2019-15213 | LOW3.91 | linux-libc-dev 6.1.177-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4010 | LOW3.91 | linux-libc-dev 6.1.177-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2012-4542 | LOW3.91 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | LOW3.9 | binutils 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20712 | LOW3.9 | binutils-common 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20712 | LOW3.9 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2025-15661 | LOW3.9 | libssh2-1 1.10.0-3+b1 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0840 | LOW3.82 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW3.82 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-0840 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-0840 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW3.82 | gzip 1.12-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-55199 | LOW3.82 | libssh2-1 1.10.0-3+b1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-56131 | LOW3.82 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | LOW3.77 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2007-1743 | LOW3.74 | apache2 2.4.68-1~deb12u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2007-1743 | LOW3.74 | apache2-bin 2.4.68-1~deb12u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2020-14304 | LOW3.74 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-54263 | LOW3.74 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42123 | LOW3.74 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40206 | LOW3.74 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68768 | LOW3.74 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-17977 | LOW3.74 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26661 | LOW3.74 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26662 | LOW3.74 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26672 | LOW3.74 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26757 | LOW3.74 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26758 | LOW3.74 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26768 | LOW3.74 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-3374 | LOW3.7 | libapt-pkg6.0 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2010-5321 | LOW3.65 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | LOW3.62 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2005-2541 | LOW3.6 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-41848 | LOW3.57 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | LOW3.54 | binutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils-common 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-6879 | LOW3.53 | libaom3 3.6.0-1+deb12u2 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-bin 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6-dev 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-45853 | LOW3.53 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2010-4651 | LOW3.48 | patch 2.7.6-7 No fix yet | 4.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-16089 | LOW3.48 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-42156 | LOW3.48 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42158 | LOW3.48 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-16229 | LOW3.48 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16231 | LOW3.48 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16232 | LOW3.48 | linux-libc-dev 6.1.177-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-16233 | LOW3.48 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-1965 | LOW3.47 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53589 | LOW3.37 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53589 | LOW3.37 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53589 | LOW3.37 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils 2.40-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils 2.40-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2016-2781 | LOW3.31 | coreutils 9.1-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | curl 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-66032 | LOW3.31 | libssh2-1 1.10.0-3+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-66033 | LOW3.31 | libssh2-1 1.10.0-3+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl 5.36.0-7+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-common 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils-common 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils-common 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2379 | LOW3.24 | curl 7.88.1-10+deb12u15 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2379 | LOW3.24 | libcurl4 7.88.1-10+deb12u15 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-bin 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6-dev 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1152 | LOW3.15 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-41080 | LOW3.15 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.11 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56391 | LOW3.11 | coreutils 9.1-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-66034 | LOW3.01 | libssh2-1 1.10.0-3+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-55200 | LOW2.99 | libssh2-1 1.10.0-3+b1 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2008-0456 | LOW2.99 | apache2 2.4.68-1~deb12u1 No fix yet | 19.0% High Exploitation Risk | Directly Exposed |
| CVE-2008-0456 | LOW2.99 | apache2-bin 2.4.68-1~deb12u1 No fix yet | 19.0% High Exploitation Risk | Directly Exposed |
| CVE-2008-4609 | LOW2.94 | linux-libc-dev 6.1.177-1 No fix yet | 32.1% High Exploitation Risk | Post-Exploit |
| CVE-2023-31486 | LOW2.92 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | LOW2.92 | perl 5.36.0-7+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | LOW2.92 | perl-base 5.36.0-7+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | LOW2.92 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2020-35501 | LOW2.89 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | LOW2.86 | binutils 2.40-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-15003 | 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.8% Theoretical Threat | Post-Exploit |
| CVE-2026-15003 | 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.8% Theoretical Threat | Post-Exploit |
| CVE-2026-15003 | LOW2.86 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2007-0086 | LOW2.81 | apache2-utils 2.4.68-1~deb12u1 No fix yet | 9.6% Low-Moderate Risk | Post-Exploit |
| CVE-2013-7445 | LOW2.81 | linux-libc-dev 6.1.177-1 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19449 | LOW2.81 | linux-libc-dev 6.1.177-1 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19814 | LOW2.81 | linux-libc-dev 6.1.177-1 No fix yet | 3.3% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19378 | LOW2.81 | linux-libc-dev 6.1.177-1 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | cpp-12 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | g++-12 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | gcc-12 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-45261 | LOW2.8 | patch 2.7.6-7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-56288 | LOW2.8 | patch 2.7.6-7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56289 | LOW2.8 | patch 2.7.6-7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW2.8 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-4016 | LOW2.8 | libproc2-0 2:4.0.2-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2015-2877 | LOW2.8 | linux-libc-dev 6.1.177-1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-54227 | LOW2.8 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54233 | LOW2.8 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50057 | LOW2.8 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50211 | LOW2.8 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40268 | LOW2.8 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40303 | LOW2.8 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13221 | LOW2.78 | perl 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | curl 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-66035 | LOW2.7 | libssh2-1 1.10.0-3+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | mount 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42767 | LOW2.7 | openssl 3.0.20-1~deb12u2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2003-1581 | LOW2.6 | apache2 2.4.68-1~deb12u1 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1581 | LOW2.6 | apache2-bin 2.4.68-1~deb12u1 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1307 | LOW2.58 | apache2-utils 2.4.68-1~deb12u1 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2003-1580 | LOW2.58 | apache2-utils 2.4.68-1~deb12u1 No fix yet | 3.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-42250 | LOW2.55 | bzip2 1.0.8-5+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2007-3303 | LOW2.5 | apache2-utils 2.4.68-1~deb12u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | curl 7.88.1-10+deb12u15 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 9.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.12-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-0725 | LOW2.4 | curl 7.88.1-10+deb12u15 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0725 | LOW2.4 | libcurl4 7.88.1-10+deb12u15 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-69644 | LOW2.38 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2007-1743 | LOW2.24 | apache2-utils 2.4.68-1~deb12u1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils 9.1-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW2.24 | coreutils 9.1-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-24515 | LOW2.12 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-11191 | LOW2.12 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW1.89 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2008-0456 | LOW1.79 | apache2-utils 2.4.68-1~deb12u1 No fix yet | 19.0% High Exploitation Risk | Post-Exploit |
| CVE-2001-1534 | LOW1.78 | apache2 2.4.68-1~deb12u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2001-1534 | LOW1.78 | apache2-bin 2.4.68-1~deb12u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2007-3719 | LOW1.78 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW1.68 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-4016 | LOW1.68 | procps 2:4.0.2-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42155 | LOW1.61 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2003-1581 | LOW1.56 | apache2-utils 2.4.68-1~deb12u1 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2001-1534 | LOW1.07 | apache2-utils 2.4.68-1~deb12u1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2007-0086 | NONE0 | apache2-data 2.4.68-1~deb12u1 No fix yet | 9.6% Low-Moderate Risk | Not Applicable |
| CVE-2025-69720 | NONE0 | libncursesw6 6.4-4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.4-4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.4-4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.4-4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libncursesw6 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libtinfo6 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-bin 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2018-21232 | NONE0 | re2c 3.0-2 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2007-3303 | NONE0 | apache2-data 2.4.68-1~deb12u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules-bin 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-runtime 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam0g 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-30258 | NONE0 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68972 | NONE0 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-modules 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-modules-bin 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-runtime 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam0g 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2007-1743 | NONE0 | apache2-data 2.4.68-1~deb12u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2003-1307 | NONE0 | apache2-data 2.4.68-1~deb12u1 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2003-1580 | NONE0 | apache2-data 2.4.68-1~deb12u1 No fix yet | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2022-3219 | NONE0 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncursesw6 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-bin 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-2903 | NONE0 | re2c 3.0-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-57062 | NONE0 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2003-1581 | NONE0 | apache2-data 2.4.68-1~deb12u1 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2008-0456 | NONE0 | apache2-data 2.4.68-1~deb12u1 No fix yet | 19.0% High Exploitation Risk | Not Applicable |
| CVE-2001-1534 | NONE0 | apache2-data 2.4.68-1~deb12u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.2.15-2+b13 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-8458 | NONE0 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53910 | NONE0 | diffutils 1:3.8-4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libblkid1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56408 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56409 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libmount1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-57433 | NONE0 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2025-7709 | NONE0 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11822 | NONE0 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50812 | NONE0 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50813 | NONE0 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-27587 | NONE0 | libssl3 3.0.20-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libuuid1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libuuid1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31432 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31706 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43490 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64437 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40003 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40077 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40097 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40137 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40180 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40266 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40289 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40311 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40333 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40337 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40354 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68190 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68320 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68322 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68809 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-71065 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71198 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23393 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31707 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43258 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53368 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53401 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63805 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63806 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63815 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63816 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63818 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63819 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63825 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63959 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64082 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64138 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64139 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64241 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64248 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64250 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64269 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64270 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64272 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64273 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64274 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64318 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64331 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64337 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64345 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64348 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64350 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64359 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64361 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64371 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64389 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64390 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64391 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64392 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64393 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64394 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64395 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64396 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64397 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64398 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64399 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64400 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64420 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64425 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64429 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64432 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64438 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64440 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64441 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64442 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64443 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64444 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64445 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64446 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64449 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64450 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64461 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64462 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64468 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64469 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64484 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64494 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64495 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64497 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64500 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64503 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64504 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64505 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64532 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64533 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64536 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64549 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64550 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43249 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2023-53851 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | mount 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | mount 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2025-27587 | NONE0 | openssl 3.0.20-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | — | Not Applicable |
| CVE-2026-57433 | NONE0 | perl 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.3% 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+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | util-linux 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | util-linux 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-9082 | NONE0 | drupal/core 9.8.0 fixed in 10.4.10, 10.5.10, 10.6.9, 11.1.10, 11.2.12, 11.3.10 | 88.3% Actively Exploited | Not Applicable |
| CVE-2024-55637 | NONE0 | drupal/core 9.8.0 fixed in 10.2.11, 10.3.9, 11.0.8 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-55638 | NONE0 | drupal/core 9.8.0 fixed in 10.2.11, 10.3.9, 7.102 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-12393 | NONE0 | drupal/core 9.8.0 fixed in 10.2.11, 10.3.9, 11.0.8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-55634 | NONE0 | drupal/core 9.8.0 fixed in 10.2.11, 10.3.9, 11.0.8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-13081 | NONE0 | drupal/core 9.8.0 fixed in 10.4.9, 10.5.6, 11.1.9, 11.2.8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3057 | NONE0 | drupal/core 9.8.0 fixed in 10.3.13, 10.4.3, 11.0.12, 11.1.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-31673 | NONE0 | drupal/core 9.8.0 fixed in 10.3.13, 10.4.3, 11.0.12, 11.1.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-31674 | NONE0 | drupal/core 9.8.0 fixed in 10.3.13, 10.4.3, 11.0.12, 11.1.3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-6365 | NONE0 | drupal/core 9.8.0 fixed in 10.5.9, 10.6.7, 11.2.11, 11.3.7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6366 | NONE0 | drupal/core 9.8.0 fixed in 10.5.9, 10.6.7, 11.2.11, 11.3.7 | 0.4% Theoretical Threat | Not Applicable |
| GHSA-6ccv-8fgf-cjpw | NONE0 | drupal/core 9.8.0 fixed in 10.1.8, 10.2.2 | — | Not Applicable |
| CVE-2024-55636 | NONE0 | drupal/core 9.8.0 fixed in 10.2.11, 10.3.9, 11.0.8 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-13080 | NONE0 | drupal/core 9.8.0 fixed in 10.4.9, 10.5.6, 11.1.9, 11.2.8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-13082 | NONE0 | drupal/core 9.8.0 fixed in 10.4.9, 10.5.6, 11.1.9, 11.2.8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-13083 | NONE0 | drupal/core 9.8.0 fixed in 10.4.9, 10.5.6, 11.1.9, 11.2.8, 7.103 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-31675 | NONE0 | drupal/core 9.8.0 fixed in 10.3.14, 10.4.5, 11.0.13, 11.1.5 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-55637 | NONE0 | drupal/core-recommended 9.8.0 fixed in 10.2.11, 10.3.9, 11.0.8 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-55638 | NONE0 | drupal/core-recommended 9.8.0 fixed in 10.2.11, 10.3.9, 7.102 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-12393 | NONE0 | drupal/core-recommended 9.8.0 fixed in 10.2.11, 10.3.9, 11.0.8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-55634 | NONE0 | drupal/core-recommended 9.8.0 fixed in 10.2.11, 10.3.9, 11.0.8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-55636 | NONE0 | drupal/core-recommended 9.8.0 fixed in 10.2.11, 10.3.9, 11.0.8 | 0.9% Theoretical Threat | Not Applicable |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.