Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker could achieve denial of service or remote code execution by exploiting CVE-2026-6653 via crafted XML input or CVE-2023-45853 via malicious zip files. Disabling file upload functionality would fully eliminate the risk from CVE-2023-45853, and a WAF can help filter malicious XML. Note that the glibc CVEs require crafted regex patterns, which are unlikely in typical Drupal usage. Updating the base image or applying vendor patches is the recommended long-term solution.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-6653 | HIGH8.33 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2023-45853 | HIGH7.84 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 2.9% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| 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-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-2025-11082 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48962 | MEDIUM6.63 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11979 | MEDIUM6.63 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.1% Theoretical Threat | 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-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-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-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.3% 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.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-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-2026-22185 | MEDIUM5.78 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 0.1% 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-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.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libbinutils 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libctf-nobfd0 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libctf0 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libgprofng0 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-15649 | MEDIUM5.52 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libbinutils 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libbinutils 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libbinutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf-nobfd0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libctf-nobfd0 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libctf-nobfd0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libctf0 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libctf0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libgprofng0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libgprofng0 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libgprofng0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-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-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-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-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-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-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-2008-4609 | MEDIUM4.9 | linux-libc-dev 6.1.176-1 No fix yet | 32.1% High Exploitation Risk | Post-Exploit |
| CVE-2023-31486 | MEDIUM4.86 | perl 5.36.0-7+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | MEDIUM4.86 | perl-base 5.36.0-7+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | MEDIUM4.86 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1178 | MEDIUM4.76 | libbinutils 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf-nobfd0 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf0 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libgprofng0 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2013-7445 | MEDIUM4.68 | linux-libc-dev 6.1.176-1 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19449 | MEDIUM4.68 | linux-libc-dev 6.1.176-1 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19814 | MEDIUM4.68 | linux-libc-dev 6.1.176-1 No fix yet | 3.3% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19378 | MEDIUM4.68 | linux-libc-dev 6.1.176-1 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-25265 | MEDIUM4.68 | linux-libc-dev 6.1.176-1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27943 | MEDIUM4.67 | libasan8 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libatomic1 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.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-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-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-42496 | MEDIUM4.64 | perl-base 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-2019-19070 | MEDIUM4.5 | linux-libc-dev 6.1.176-1 No fix yet | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-0400 | MEDIUM4.5 | linux-libc-dev 6.1.176-1 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2008-1687 | MEDIUM4.5 | m4 1.4.19-3 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2008-1688 | MEDIUM4.5 | m4 1.4.19-3 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6951 | MEDIUM4.5 | patch 2.7.6-7 No fix yet | 8.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6952 | MEDIUM4.5 | patch 2.7.6-7 No fix yet | 8.4% Low-Moderate Risk | Post-Exploit |
| CVE-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.3% 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-2021-45346 | MEDIUM4.3 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| 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.3% 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.3% 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.3% 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.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-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-2026-55200 | MEDIUM4.23 | libssh2-1 1.10.0-3+b1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2020-15719 | MEDIUM4.2 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-39191 | MEDIUM4.18 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% 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.5% 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-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-6846 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-3847 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-52452 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52624 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-52751 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53218 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-21803 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-26836 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26913 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-26914 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26944 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35887 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38570 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38630 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41045 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-42118 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44941 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44942 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44951 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46729 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46811 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46813 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47691 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50029 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50217 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50226 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50282 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53068 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53168 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53179 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53218 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56538 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56775 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57900 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-58093 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21927 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21967 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21969 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23133 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37750 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37777 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37861 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-37952 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37957 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38069 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38117 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38182 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38206 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38248 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38369 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38582 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38585 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38595 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38722 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38734 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39797 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39810 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39859 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39952 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71068 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71073 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71152 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23171 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23208 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23226 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-23361 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23447 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23448 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31493 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31527 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31729 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43049 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43250 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46068 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46219 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46241 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53129 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53143 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53156 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53157 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53262 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53272 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53359 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53362 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46274 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-12456 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2020-11725 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2021-26934 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3238 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-26242 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-3640 | LOW3.98 | linux-libc-dev 6.1.176-1 No fix yet | 0.7% 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-2025-21759 | LOW3.96 | linux-libc-dev 6.1.176-1 No fix yet | 7.2% Low-Moderate Risk | Post-Exploit |
| 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-2026-11856 | LOW3.9 | curl 7.88.1-10+deb12u15 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-11856 | LOW3.9 | libcurl4 7.88.1-10+deb12u15 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2004-0230 | LOW3.9 | linux-libc-dev 6.1.176-1 No fix yet | 80.9% Actively Exploited | 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.6% 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.8% 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.6% 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.8% 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.4% 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-2025-22037 | LOW3.79 | linux-libc-dev 6.1.176-1 No fix yet | 28.2% High Exploitation Risk | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-40170 | LOW3.77 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53781 | LOW3.72 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39981 | LOW3.72 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43248 | LOW3.72 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW3.7 | libapt-pkg6.0 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-3441 | LOW3.62 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26669 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41935 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53147 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57982 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21985 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22039 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-22104 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38081 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38204 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38616 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38636 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39744 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39901 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23327 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31568 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45893 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45943 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45957 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46130 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46293 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53138 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53179 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-25742 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-25743 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36013 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-53216 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40064 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68183 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68324 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43126 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43414 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-46135 | LOW3.62 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% 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-2021-3864 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-52586 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42162 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37776 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23191 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31419 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31663 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43125 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43198 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-46054 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46181 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52991 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53000 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53091 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53762 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57984 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40158 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40168 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40328 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23050 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45859 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-45894 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45942 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46090 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46266 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-46324 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46330 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52956 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53005 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53009 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53053 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53078 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53089 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53132 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53185 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53224 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53230 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53246 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53361 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-1247 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-2961 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-45884 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-45885 | LOW3.57 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils-common 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2018-1121 | LOW3.54 | linux-libc-dev 6.1.176-1 No fix yet | 4.2% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3714 | LOW3.54 | linux-libc-dev 6.1.176-1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2023-6879 | LOW3.53 | libaom3 3.6.0-1+deb12u2 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-bin 2.36-9+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-2010-4651 | LOW3.48 | patch 2.7.6-7 No fix yet | 4.8% Low-Moderate Risk | Post-Exploit |
| 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-2020-36694 | LOW3.42 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-21264 | LOW3.42 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53095 | LOW3.42 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57795 | LOW3.42 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21714 | LOW3.42 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% 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-2026-53267 | LOW3.37 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils 2.40-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2016-2781 | LOW3.31 | coreutils 9.1-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-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-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-2025-15661 | LOW3.31 | libssh2-1 1.10.0-3+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-6240 | LOW3.31 | linux-libc-dev 6.1.176-1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2024-36968 | LOW3.31 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43239 | LOW3.31 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-0564 | LOW3.31 | linux-libc-dev 6.1.176-1 No fix yet | 0.6% 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-2193 | LOW3.3 | linux-libc-dev 6.1.176-1 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2018-21232 | LOW3.3 | re2c 3.0-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-13221 | LOW3.28 | libperl5.36 5.36.0-7+deb12u3 No fix yet | — | Post-Exploit |
| CVE-2026-13221 | LOW3.28 | perl 5.36.0-7+deb12u3 No fix yet | — | Post-Exploit |
| CVE-2026-13221 | LOW3.28 | perl-base 5.36.0-7+deb12u3 No fix yet | — | Post-Exploit |
| CVE-2026-13221 | LOW3.28 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | — | Post-Exploit |
| CVE-2025-40074 | LOW3.26 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23383 | LOW3.26 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31502 | LOW3.26 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31516 | LOW3.26 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53090 | LOW3.26 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-44032 | LOW3.26 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-44033 | LOW3.26 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-44034 | LOW3.26 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | 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-2023-3397 | LOW3.21 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40307 | LOW3.21 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-40918 | LOW3.21 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | 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-40146 | LOW3.16 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW3.15 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-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-2025-40071 | LOW3.11 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40355 | LOW3.11 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68342 | LOW3.11 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68736 | LOW3.11 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31505 | LOW3.11 | linux-libc-dev 6.1.176-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-2026-57432 | LOW3.02 | libperl5.36 5.36.0-7+deb12u3 No fix yet | — | Post-Exploit |
| CVE-2026-57432 | LOW3.02 | perl 5.36.0-7+deb12u3 No fix yet | — | Post-Exploit |
| CVE-2026-57432 | LOW3.02 | perl-base 5.36.0-7+deb12u3 No fix yet | — | Post-Exploit |
| CVE-2026-57432 | LOW3.02 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | — | 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-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-2010-4563 | LOW3 | linux-libc-dev 6.1.176-1 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-53706 | LOW2.96 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54107 | LOW2.96 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54141 | LOW2.96 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23239 | LOW2.96 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23240 | LOW2.96 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | 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-2024-49569 | LOW2.91 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-23039 | LOW2.91 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils 2.40-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-common 2.40-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2017-0630 | LOW2.82 | linux-libc-dev 6.1.176-1 No fix yet | 1.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-27943 | LOW2.8 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2023-0597 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-23005 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-31082 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-37454 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-4133 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52485 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52590 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52591 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52625 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52629 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52648 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52671 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52676 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52761 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52770 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52797 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-52888 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52920 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53149 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53231 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53261 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53336 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53353 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53367 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53394 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53429 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53460 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53491 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53523 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53529 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53538 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53574 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-53627 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53846 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53999 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54013 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54280 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-6039 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-25740 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26670 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26677 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26691 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26740 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26756 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26799 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26841 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26866 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26876 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26902 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26947 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26948 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26953 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26962 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27010 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27011 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27041 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-27057 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27062 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27079 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35784 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35794 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35799 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35808 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35860 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35904 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35924 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35931 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35942 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35945 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35946 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35951 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35961 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36911 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36951 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38557 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38564 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38594 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38608 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38620 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38622 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-38625 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-40965 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-40969 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-40975 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-40998 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-40999 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41008 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-41023 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41031 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-41082 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42128 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42139 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42239 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42241 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42243 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42279 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42317 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43819 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43824 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43850 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43872 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43899 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43901 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43913 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-44963 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-45015 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46678 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46681 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46698 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46727 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46728 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46730 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46754 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46760 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46765 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46775 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46776 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46806 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46808 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46834 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46860 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47141 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47658 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47661 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47662 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47664 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47703 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47752 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-47794 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49568 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49893 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49901 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49906 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49908 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49910 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49914 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49916 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49918 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49919 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49920 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49921 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49922 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49923 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49926 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49940 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49945 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49970 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-49988 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50009 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50017 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50028 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50111 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50166 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50285 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-50289 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-52559 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-52560 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53051 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53056 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53079 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53085 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53089 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53090 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53091 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53094 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53114 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53134 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53187 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53195 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53219 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53224 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53687 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-54683 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56544 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56565 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56566 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56583 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56588 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56591 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56592 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56611 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56641 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56692 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56712 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56742 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57804 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57809 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57872 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57888 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57975 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57976 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57999 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58006 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58012 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58053 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58089 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58094 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58095 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58096 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58097 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58098 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58100 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58237 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-58241 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21634 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21635 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21649 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21656 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21658 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21673 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21693 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21696 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21723 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21729 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21768 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21801 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21831 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21836 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21870 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21872 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21885 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21888 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21894 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21907 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21949 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21955 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21961 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21972 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21976 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22028 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22043 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22048 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22053 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22057 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22070 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22103 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22109 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22113 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22125 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-22127 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23129 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23130 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23131 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-23132 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37747 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37800 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37802 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37806 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37807 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37833 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37834 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37842 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37853 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37856 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37860 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37880 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37893 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-37956 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37977 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38006 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38014 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38029 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38038 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38039 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38041 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38042 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38045 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38059 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38064 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38080 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38096 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38127 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38132 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38140 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38195 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38203 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38207 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38237 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38244 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38246 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38261 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38264 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38272 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38283 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38311 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38333 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38359 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38426 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38429 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38438 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-38449 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38507 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38531 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38544 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38590 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38597 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38615 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38692 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38705 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38709 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38716 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39677 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39705 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39707 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39720 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39732 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39746 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39747 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39762 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39767 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39779 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39789 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39829 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39833 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39850 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39851 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39886 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39910 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39925 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39932 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39933 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39940 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39947 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39989 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40075 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40102 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40160 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40325 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40339 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68188 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68209 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68236 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68304 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68379 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71109 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71129 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71138 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71160 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71184 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71188 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71202 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71227 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71272 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71273 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71285 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71289 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71313 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71315 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22996 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23000 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23088 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23137 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23138 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23213 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23214 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23247 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23265 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23272 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23276 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23278 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23330 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23346 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23371 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23374 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23419 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23465 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23472 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31410 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31420 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31451 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31458 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31462 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31487 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31531 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31537 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31557 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31560 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31579 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31592 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31606 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31610 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31648 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31655 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31675 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31677 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31692 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31722 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31723 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31724 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31725 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31767 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31771 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31777 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43009 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43010 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43016 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43022 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43036 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43042 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43048 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43073 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43083 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43088 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43091 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43101 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43107 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43115 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43118 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43119 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43129 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43137 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43153 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43161 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43167 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43170 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43172 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43173 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43204 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43213 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43215 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43216 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43234 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43244 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43271 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43288 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43299 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43308 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43309 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43310 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43317 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43318 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43338 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43344 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43352 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43353 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43362 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43409 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43413 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43416 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43419 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43443 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43456 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43491 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45855 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45858 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45877 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45892 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45897 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45899 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45901 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45917 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45934 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45940 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45944 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45961 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45963 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45981 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45985 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45988 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-45993 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46000 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46012 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46014 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46032 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46059 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46071 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46092 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46111 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46147 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46148 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46153 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46156 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46157 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46158 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46170 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46200 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46225 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46226 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46229 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46245 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46252 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46254 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46282 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46302 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46312 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52928 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52936 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52937 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52944 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52961 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-52988 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-52990 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53015 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53017 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53018 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53027 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53070 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53076 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53108 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53115 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53117 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53118 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53120 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53122 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53139 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53158 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53163 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53167 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53220 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53226 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53229 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53232 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53237 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53258 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53265 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53285 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53292 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53297 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53313 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53317 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53325 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53358 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2008-2544 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2011-4915 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-4916 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2011-4917 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2014-9892 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2014-9900 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2016-10723 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2016-8660 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2017-13693 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2017-13694 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2018-12928 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2019-12378 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2019-12379 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2019-12380 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2019-12381 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2019-12382 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2019-12455 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-4543 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2023-31081 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-31085 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-4134 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-52653 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-53823 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53857 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54030 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-54088 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-35843 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-39990 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40057 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40196 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68219 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68334 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68378 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68794 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68822 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31486 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43253 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53083 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53102 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53106 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53284 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53327 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53353 | LOW2.8 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-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-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-2026-42496 | LOW2.78 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-7458 | LOW2.78 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2018-20796 | LOW2.7 | libc-bin 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2015-3276 | LOW2.7 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 5.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-17740 | LOW2.7 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 7.0% Low-Moderate Risk | 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.6% 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.6% Theoretical Threat | Post-Exploit |
| CVE-2024-36881 | LOW2.7 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71225 | LOW2.7 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% 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.3% 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-40338 | LOW2.65 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% 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-2025-71193 | LOW2.6 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23035 | LOW2.6 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | 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-2005-3660 | LOW2.5 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% 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.9% 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-2025-30258 | LOW2.4 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% 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.9% 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-2019-20794 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-52771 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-53447 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-24864 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26869 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-27408 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36024 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-36949 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-39508 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42107 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46787 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-46870 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-50135 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53176 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53178 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56729 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57857 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57974 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21651 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21732 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21825 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-21892 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22115 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38234 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38524 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38717 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39726 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39754 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39927 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39961 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40139 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68296 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68745 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-71074 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23004 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23118 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23207 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23302 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23348 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23394 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43053 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45949 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46017 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-16230 | LOW2.4 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2019-16234 | LOW2.4 | linux-libc-dev 6.1.176-1 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-2019-15213 | LOW2.35 | linux-libc-dev 6.1.176-1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-4010 | LOW2.35 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2012-4542 | LOW2.35 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils 9.1-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2020-14304 | LOW2.24 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-54263 | LOW2.24 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42123 | LOW2.24 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40206 | LOW2.24 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68768 | LOW2.24 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2018-17977 | LOW2.24 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-26661 | LOW2.24 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26662 | LOW2.24 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26672 | LOW2.24 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26757 | LOW2.24 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26758 | LOW2.24 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-26768 | LOW2.24 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2010-5321 | LOW2.19 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-41848 | LOW2.14 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2019-16089 | LOW2.09 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-42156 | LOW2.09 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42158 | LOW2.09 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2019-16229 | LOW2.09 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2019-16231 | LOW2.09 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2019-16232 | LOW2.09 | linux-libc-dev 6.1.176-1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2019-16233 | LOW2.09 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-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-2020-35501 | LOW1.73 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2015-2877 | LOW1.68 | linux-libc-dev 6.1.176-1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2023-54227 | LOW1.68 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-54233 | LOW1.68 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50057 | LOW1.68 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-50211 | LOW1.68 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40268 | LOW1.68 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40303 | LOW1.68 | linux-libc-dev 6.1.176-1 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-2026-2903 | LOW1.68 | re2c 3.0-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| 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-2026-57062 | LOW1.48 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils 2.40-2 No fix yet | 0.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-2019-11191 | LOW1.27 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2007-3719 | LOW1.07 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-42155 | LOW0.97 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| 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 | libtinfo6 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-bin 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-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-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-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 |
| 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.5% 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.5% 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-58055 | NONE0 | libnghttp2-14 1.52.0-1+deb12u3 No fix yet | 0.2% 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-57433 | NONE0 | libperl5.36 5.36.0-7+deb12u3 No fix yet | — | 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.176-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31432 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31706 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43490 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40003 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40077 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40097 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40137 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40180 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40266 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40289 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40311 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40333 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40337 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40354 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68190 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68320 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68322 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68809 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71065 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71198 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23393 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31707 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43258 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46204 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53107 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53330 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53332 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53345 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43249 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | — | Not Applicable |
| CVE-2023-53851 | NONE0 | linux-libc-dev 6.1.176-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-7010 | NONE0 | perl 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl 5.36.0-7+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-7017 | NONE0 | perl 5.36.0-7+deb12u3 No fix yet | 0.3% 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-57433 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.3% 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-57433 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | — | 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 |
Want to check another image? Run a full scan with the Docker Security Scanner.