This base/runtime image carries significant vulnerabilities that any image built on it would inherit; remediate them in the final image before production. An attacker could cause denial of service via uncontrolled recursion in glibc (CVE-2019-9192) or XML entity expansion in expat (CVE-2024-28757). Note: this is a general-purpose base/runtime image — many findings live in components that an application built on top may never load, so actual exploitability depends on the final image. For an accurate risk picture, re-scan the final application image with context.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2019-9192 | HIGH7.5 | libc-bin 2.36-9+deb12u14 No fix yet | 2.4% 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-2019-9192 | HIGH7.5 | libc6 2.36-9+deb12u14 No fix yet | 2.4% 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-2020-36325 | HIGH7.5 | libjansson4 2.14-2 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2953 | HIGH7.5 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-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-6846 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | MEDIUM6.63 | libncurses-dev 6.4-4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | MEDIUM6.63 | libncurses6 6.4-4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | MEDIUM6.63 | libncursesw6 6.4-4 No fix yet | 0.4% 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-2025-69720 | MEDIUM6.63 | libtinfo-dev 6.4-4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | MEDIUM6.63 | libtinfo6 6.4-4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libbinutils 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-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-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.5% 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.5% 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.5% 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.5% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42497 | MEDIUM6.38 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM6.38 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libbinutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libctf-nobfd0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libctf0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt20 1.10.1-3+deb12u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libgprofng0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1-6 4.19.0-2+deb12u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libbinutils 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libctf-nobfd0 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libctf0 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libgprofng0 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | MEDIUM5.52 | libncurses-dev 6.4-4 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | MEDIUM5.52 | libncurses6 6.4-4 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | MEDIUM5.52 | libncursesw6 6.4-4 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-15649 | MEDIUM5.52 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | MEDIUM5.52 | libtinfo-dev 6.4-4 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | MEDIUM5.52 | libtinfo6 6.4-4 No fix yet | 1.0% 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-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.2% Low-Moderate Risk | 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-2026-50219 | 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-2025-1178 | MEDIUM4.76 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libgprofng0 2.40-2 No fix yet | 0.7% 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.2% 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.2% 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.2% 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.1% 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.1% 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.2% 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-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-27171 | MEDIUM4.67 | zlib1g-dev 1:1.2.13.dfsg-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7598 | MEDIUM4.64 | libssh2-1 1.10.0-3+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-24975 | MEDIUM4.5 | git 1:2.39.5-0+deb12u3 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6951 | MEDIUM4.5 | patch 2.7.6-7 No fix yet | 8.9% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6952 | MEDIUM4.5 | patch 2.7.6-7 No fix yet | 8.7% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1147 | MEDIUM4.5 | libbinutils 2.40-2 No fix yet | 0.6% 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.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | liblzma5 5.4.1-1 No fix yet | 0.4% 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.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | libssl3 3.0.20-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libudev1 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libudev1 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libudev1 252.39-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-52005 | MEDIUM4.49 | git 1:2.39.5-0+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2021-45346 | MEDIUM4.3 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.6% 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.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM4.25 | libbz2-1.0 1.0.8-5+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.6% 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.5% 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.6% 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.5% 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.6% 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.5% 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-2020-15719 | MEDIUM4.2 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-15079 | MEDIUM4.13 | curl 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | MEDIUM4.08 | libpam-modules 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam-modules-bin 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam-runtime 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam0g 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| 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-2024-10041 | MEDIUM4 | libpam-modules 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-10041 | MEDIUM4 | libpam-modules-bin 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-10041 | MEDIUM4 | libpam-runtime 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-10041 | MEDIUM4 | libpam0g 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-bin 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6-dev 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-11082 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW3.98 | ncurses-bin 6.4-4 No fix yet | 0.4% 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-common 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20712 | LOW3.9 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2025-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.5% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-0840 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-0840 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.5% 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-5773 | LOW3.82 | curl 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | curl 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.3% 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-2011-3374 | LOW3.7 | libapt-pkg6.0 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-3441 | LOW3.62 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-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-common 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-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 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2023-45853 | LOW3.53 | zlib1g-dev 1:1.2.13.dfsg-1 No fix yet | 2.9% 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+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | curl 7.88.1-10+deb12u14 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-53589 | LOW3.37 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53589 | LOW3.37 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53589 | LOW3.37 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils 2.40-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2016-2781 | LOW3.31 | coreutils 9.1-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | curl 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | curl 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | curl 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | curl 7.88.1-10+deb12u14 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-50495 | LOW3.31 | ncurses-bin 6.4-4 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl 5.36.0-7+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-common 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils-common 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils-common 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2379 | LOW3.24 | curl 7.88.1-10+deb12u14 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2379 | LOW3.24 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2379 | LOW3.24 | libcurl4 7.88.1-10+deb12u14 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-bin 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6-dev 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1152 | LOW3.15 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-41080 | LOW3.15 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.11 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-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+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2018-1000021 | LOW3 | git 1:2.39.5-0+deb12u3 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | LOW2.92 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | LOW2.92 | perl 5.36.0-7+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | LOW2.92 | perl-base 5.36.0-7+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | LOW2.92 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | curl 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | cpp-12 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | g++-12 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | gcc-12 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-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-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-2025-6141 | LOW2.8 | libncurses-dev 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW2.8 | libncurses6 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW2.8 | libncursesw6 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW2.8 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW2.8 | libtinfo-dev 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW2.8 | libtinfo6 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | LOW2.78 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.5% 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-42496 | LOW2.78 | perl 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | LOW2.78 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | LOW2.78 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2018-20796 | LOW2.7 | libc-bin 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20796 | LOW2.7 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20796 | LOW2.7 | libc6 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20796 | LOW2.7 | libc6-dev 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2015-3276 | LOW2.7 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 5.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-17740 | LOW2.7 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 7.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% 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+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | curl 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | curl 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42767 | LOW2.7 | openssl 3.0.20-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.2% 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-3184 | LOW2.7 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34743 | LOW2.7 | xz-utils 5.4.1-1 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.5% 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.6% 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.5% 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.6% 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.5% 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.6% 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.5% 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.6% Theoretical Threat | Directly Exposed |
| 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.6% 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.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% 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.5% 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-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-10148 | LOW2.45 | curl 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | curl 7.88.1-10+deb12u14 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-10148 | LOW2.45 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-10148 | LOW2.45 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl4 7.88.1-10+deb12u14 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-2025-15224 | LOW2.4 | curl 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | dirmngr 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | dirmngr 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gnupg 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gnupg 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gnupg-utils 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gnupg-utils 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg-agent 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg-agent 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg-wks-client 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg-wks-client 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg-wks-server 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg-wks-server 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgconf 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgconf 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgsm 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgsm 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl4 7.88.1-10+deb12u14 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+deb12u14 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0725 | LOW2.4 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0725 | LOW2.4 | libcurl4 7.88.1-10+deb12u14 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-2025-5278 | LOW2.24 | coreutils 9.1-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-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-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | dirmngr 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gnupg 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gnupg-utils 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg-agent 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg-wks-client 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg-wks-server 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgconf 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgsm 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-6141 | LOW1.68 | ncurses-bin 6.4-4 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-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.5% 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.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-common 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-common 2.40-2 No fix yet | 0.6% 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.5% 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.6% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-52005 | NONE0 | git-man 1:2.39.5-0+deb12u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-39191 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2013-7445 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-19449 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-19814 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-3847 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-52452 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52624 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52751 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53218 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-21803 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-26836 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26913 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26914 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26944 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35887 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38570 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38630 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41045 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42118 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44941 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44942 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44951 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46729 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46811 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46813 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47691 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50029 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50217 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50226 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50282 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53068 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53168 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53179 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53218 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56538 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56775 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57900 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-58093 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21863 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21927 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21967 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21969 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23133 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37750 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37777 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37861 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37952 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37957 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38069 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38117 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38182 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38206 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38248 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38349 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38369 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38582 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38584 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38585 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38595 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38627 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38722 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38734 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39797 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39810 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39859 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39952 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71068 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71073 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71152 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23171 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23208 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23226 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23361 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23447 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23448 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31488 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31489 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31493 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31500 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31527 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31532 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31576 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31578 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31580 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31581 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31583 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31686 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31696 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31702 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31709 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31715 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31729 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43049 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43250 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45996 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46004 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46047 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46163 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46180 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46189 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46219 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46234 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46241 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46323 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46331 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46274 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-12456 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19378 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-11725 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-26934 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-25265 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-3238 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-26242 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-3640 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.4-4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-24975 | NONE0 | git-man 1:2.39.5-0+deb12u3 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-43501 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46195 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43110 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-19070 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-0400 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-40170 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31607 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-53781 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39981 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43248 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-26669 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41935 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53147 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57982 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21985 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22039 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22104 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38081 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38204 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38616 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38636 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39744 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39901 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23327 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31568 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43052 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45957 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45994 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46022 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46033 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46191 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-25742 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-25743 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36013 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-53216 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40064 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68183 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68324 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31613 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31685 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43126 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43414 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46053 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46056 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46120 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46135 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46150 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46209 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2008-4609 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 32.1% High Exploitation Risk | Not Applicable |
| CVE-2021-3864 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-52586 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42162 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37776 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23191 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31419 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31663 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43125 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43198 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43494 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45852 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45858 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46054 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46090 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46099 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46116 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46125 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46181 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46227 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46319 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46330 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53762 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57984 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40158 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40168 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40328 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23050 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31586 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31694 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43116 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43303 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43491 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43493 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45840 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45859 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-45892 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45894 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45899 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45934 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45942 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46015 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46043 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46052 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46069 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46119 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46123 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46132 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46133 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46149 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46173 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46185 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46242 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46266 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46275 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46294 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46306 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-1247 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2961 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45884 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45885 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-36694 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-21264 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53095 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57795 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21714 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21739 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21759 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 7.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-45991 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-6240 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-36968 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31588 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43239 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-0564 | NONE0 | linux-libc-dev 6.1.174-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-2025-40074 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23383 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31502 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31516 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2022-44032 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44033 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44034 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-3397 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40307 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40918 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40146 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40071 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40355 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68342 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68736 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31449 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31505 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31700 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31708 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2018-1121 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-3714 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-53706 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54107 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54141 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23239 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23240 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46065 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46113 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-49569 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46024 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-23039 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40347 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-0597 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-23005 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31082 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-37454 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-4133 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52485 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52590 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52591 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52625 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52629 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52648 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52671 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52676 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52761 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52770 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52797 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52888 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52920 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53149 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53231 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53261 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53292 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53336 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53353 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53367 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53394 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53429 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53460 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53491 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53523 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53529 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53538 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53574 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53627 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53846 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53989 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53999 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54013 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54271 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54280 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-6039 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-2193 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-25740 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26670 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26677 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26691 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26740 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26756 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26799 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26841 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26866 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26876 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26902 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26947 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26948 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26953 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26962 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27010 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27011 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27012 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27041 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27057 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27062 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27079 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35784 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35794 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35799 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35808 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35860 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35904 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35924 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35931 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35942 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35945 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35946 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35951 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35961 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36911 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36922 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36951 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38557 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38564 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38594 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38608 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38620 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38622 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38625 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40965 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40969 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40975 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40998 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40999 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41008 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41023 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41031 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41082 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42128 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42139 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42239 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42241 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42243 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42279 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42317 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43819 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43824 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43850 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43872 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-43899 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43901 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43913 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44963 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45015 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46678 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46681 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46698 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46727 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46728 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46730 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46754 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46760 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46765 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46775 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46776 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46806 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46808 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46834 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46860 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47141 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47658 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47661 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47662 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47664 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47703 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47752 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47794 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49568 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49893 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49901 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49906 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49908 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49910 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49914 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49916 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49918 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49919 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49920 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49921 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49922 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49923 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49926 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49940 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49945 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49970 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49988 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50009 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50017 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50028 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50111 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50166 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50285 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50289 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-52559 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-52560 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53051 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53056 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53079 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53085 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53089 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53090 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53091 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53094 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53114 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53134 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53187 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53195 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53219 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53221 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53224 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53687 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-54683 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56544 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56565 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56566 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56583 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56588 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56591 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56592 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56611 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56641 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56657 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56692 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56712 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56742 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57804 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57809 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57872 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57888 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57975 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57976 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57999 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58006 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58012 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58053 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58089 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58094 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58095 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58096 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58097 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58098 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58100 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58237 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58241 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21634 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21635 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21649 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21656 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21658 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21673 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21693 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21696 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21723 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21729 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21768 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21801 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21831 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21836 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21870 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21872 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21885 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21888 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21894 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21907 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21949 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21955 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21961 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21972 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21976 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22028 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22037 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 23.3% High Exploitation Risk | Not Applicable |
| CVE-2025-22043 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22048 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22053 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22057 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22070 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22103 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22105 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22109 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22113 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22125 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22127 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23129 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23130 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23131 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23132 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37747 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37800 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37802 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37806 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37807 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37833 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37834 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37842 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37853 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37856 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37860 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37864 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37880 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37893 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37956 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37977 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38006 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38014 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38029 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38038 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38039 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38041 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38042 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38045 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38059 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38064 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38080 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38096 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38127 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38132 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38140 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38195 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38203 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38207 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38237 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38244 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38246 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38261 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38264 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38272 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38283 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38311 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38333 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38359 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38426 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38429 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38438 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38449 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38507 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38531 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38544 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38590 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38597 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38615 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38692 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38705 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38709 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38710 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38716 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39677 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39705 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39707 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39720 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39732 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39746 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39747 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39762 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39767 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39779 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39789 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39829 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39833 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39850 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39851 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39886 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39910 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39925 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39932 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39933 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39940 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39947 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39989 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40075 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40102 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40160 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40325 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40339 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68188 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68209 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68236 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68304 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68379 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68823 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71109 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71129 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71138 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71160 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71184 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71188 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71202 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71227 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71272 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71273 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71285 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71289 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71313 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22996 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23000 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23066 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23088 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23137 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23138 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23213 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23214 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23247 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23255 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23265 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23272 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23276 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23278 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23310 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23330 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23346 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23371 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23374 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23389 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23399 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23419 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23442 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23444 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23465 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23468 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23472 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31407 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31410 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31420 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31451 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31458 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31462 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31487 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31531 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31537 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31557 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31560 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31577 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31579 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31585 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31590 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31592 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31594 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31595 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31596 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31599 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31603 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31605 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31606 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31610 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31615 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31616 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31617 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31618 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31619 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31623 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31624 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31625 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31630 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31637 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31642 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31648 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31655 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31673 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31675 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31676 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31677 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31681 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31684 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31692 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31698 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31699 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31701 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31704 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31722 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31723 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31724 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31725 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31767 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31771 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31777 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43009 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43010 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43016 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43022 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43036 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43042 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43048 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43058 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43064 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43071 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43072 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43073 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43079 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43080 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43083 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43085 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43088 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43089 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43091 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43093 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43094 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43098 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43099 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43101 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43103 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43104 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43105 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43107 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43111 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43112 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43113 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43114 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43115 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43118 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43119 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43129 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43137 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43153 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43161 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43167 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43170 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43172 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43173 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43204 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43213 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43215 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43216 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43219 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43234 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43244 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43271 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43288 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43299 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43308 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43309 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43310 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43317 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43318 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43338 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43344 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43350 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43352 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43353 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43362 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43409 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43413 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43416 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43421 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43443 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43456 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43492 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43502 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45834 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45835 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45836 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45838 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45841 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45842 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45843 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45844 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45846 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45855 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45943 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45944 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45961 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45963 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45981 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45985 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45986 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45987 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45988 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45993 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45997 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45999 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46000 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46002 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46003 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46005 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46009 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46012 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46014 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46018 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46019 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46021 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46023 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46026 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46027 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46032 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46037 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46038 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46040 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46044 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46046 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46049 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46050 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46051 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46059 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46064 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46070 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46078 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46079 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46082 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46086 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46102 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46107 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46111 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46127 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46130 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46137 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46146 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46148 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46151 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46153 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46156 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46157 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46158 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46160 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46161 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46165 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46167 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46168 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46169 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46170 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46172 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46179 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46184 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46186 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46190 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46193 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46196 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46200 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46214 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46220 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46225 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46226 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46229 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46231 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46233 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46235 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46236 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46245 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46252 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46254 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46273 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46280 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46291 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46304 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46307 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46312 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46320 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46321 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46322 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2008-2544 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2011-4915 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2011-4916 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2011-4917 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9892 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9900 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-10723 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-8660 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2017-13693 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-13694 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12928 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12378 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12379 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12380 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12381 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12382 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12455 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-4543 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-31081 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31085 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-4134 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52653 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-53823 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53857 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54030 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54088 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35843 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39990 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40057 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40196 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68219 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68334 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68378 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68794 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68822 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71315 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31486 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43253 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43419 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43496 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45877 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45897 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45901 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45917 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46068 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46071 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46083 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46088 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46092 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46101 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46103 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46136 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46178 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46292 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46299 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46302 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-36881 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71225 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40338 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71193 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23035 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-1000021 | NONE0 | git-man 1:2.39.5-0+deb12u3 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2004-0230 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 80.9% Actively Exploited | Not Applicable |
| CVE-2010-4563 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2005-3660 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-30258 | NONE0 | gnupg-l10n 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68972 | NONE0 | gnupg-l10n 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-20794 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-52771 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53447 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-24864 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26869 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27408 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36024 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36949 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39508 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42107 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46787 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46870 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-50135 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53176 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53178 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56729 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57857 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57974 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21651 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21732 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21825 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21892 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22115 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38234 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38524 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38717 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39726 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39754 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39927 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39961 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40139 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68296 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68745 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71074 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23004 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23118 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23207 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23302 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23348 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23394 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31697 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43053 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45949 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46017 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46159 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46187 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2017-0630 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-16230 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16234 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-15213 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-4010 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2012-4542 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-14304 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-54263 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42123 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40206 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68768 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-17977 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-26661 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26662 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26672 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26757 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26758 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26768 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2010-5321 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-41848 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-16089 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-42156 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42158 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-16229 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16231 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16232 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-16233 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-35501 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-3219 | NONE0 | gnupg-l10n 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2015-2877 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-54227 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54233 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54322 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50057 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50211 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40268 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40303 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-11191 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2007-3719 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42155 | NONE0 | linux-libc-dev 6.1.174-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-53613 | NONE0 | bsdutils 1:2.38.1-5+deb12u3 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 | libblkid1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-56131 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | — | Not Applicable |
| CVE-2026-56132 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libmount1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53613 | NONE0 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | — | 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-2025-7709 | NONE0 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-15661 | NONE0 | libssh2-1 1.10.0-3+b1 No fix yet | — | Not Applicable |
| CVE-2026-55199 | NONE0 | libssh2-1 1.10.0-3+b1 No fix yet | — | Not Applicable |
| CVE-2026-55200 | NONE0 | libssh2-1 1.10.0-3+b1 No fix yet | — | Not Applicable |
| CVE-2025-27587 | NONE0 | libssl3 3.0.20-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53613 | NONE0 | libuuid1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libuuid1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31705 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43258 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54125 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40003 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40077 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40097 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40137 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40180 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40266 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40289 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40311 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40333 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40337 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40354 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68190 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68201 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68315 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68320 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68322 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68809 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71065 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71198 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23393 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31432 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31587 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31597 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31598 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31602 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31611 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31612 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31622 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31626 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31627 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31629 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31706 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31707 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31711 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31712 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31716 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43075 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43076 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43117 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43249 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43490 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43495 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43497 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43499 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45839 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45850 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45893 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45930 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46006 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46031 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46058 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46062 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46072 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46075 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46077 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46080 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46091 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46098 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46108 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46109 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46110 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46112 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46122 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46124 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46128 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46129 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46143 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46164 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46177 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46197 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46198 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46199 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46204 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46205 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46206 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46208 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46212 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46218 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46230 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46238 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46303 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46314 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46276 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46282 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46285 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46293 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46296 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46301 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | — | Not Applicable |
| CVE-2023-53851 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52909 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | — | Not Applicable |
| CVE-2026-52910 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | mount 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | mount 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2025-27587 | NONE0 | openssl 3.0.20-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.2% 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 |
| 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-53613 | NONE0 | util-linux 2.38.1-5+deb12u3 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-extra 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 |