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