Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. The image has 962 exposed vulnerabilities, with 59 rated at severity 7.0 or higher, including critical issues in glibc (CVE-2019-1010023) and HDF5 (CVE-2019-9151) that could lead to arbitrary code execution or out-of-bounds reads. However, these require user interaction, such as running ldd on a malicious ELF or processing a malicious HDF5 file, which may not be common in typical Ansible usage. Post-exploit-only findings are all low severity (max 4.69), so the primary risk is from the exposed surface. Keeping the image updated and avoiding untrusted input files would reduce the practical risk, but the high number of vulnerabilities makes strict controls necessary.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2019-1010023 | HIGH8.8 | libc6 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc6-dev 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9151 | HIGH8.8 | libhdf5-310 1.14.5+repack-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9152 | HIGH8.8 | libhdf5-310 1.14.5+repack-3 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9151 | HIGH8.8 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9152 | HIGH8.8 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9151 | HIGH8.8 | libhdf5-dev 1.14.5+repack-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9152 | HIGH8.8 | libhdf5-dev 1.14.5+repack-3 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9151 | HIGH8.8 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9152 | HIGH8.8 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9151 | HIGH8.8 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9152 | HIGH8.8 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9151 | HIGH8.8 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9152 | HIGH8.8 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9151 | HIGH8.8 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9152 | HIGH8.8 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-8376 | HIGH8.33 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-50252 | HIGH7.91 | libunbound8 1.22.0-2+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13221 | HIGH7.73 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | HIGH7.73 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-bin 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-bin 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6-dev 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6-dev 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libgssrpc4t64 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkadm5clnt-mit12 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkadm5srv-mit12 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkdb5-10t64 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5-dev 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2015-3276 | HIGH7.5 | libldap-common 2.6.10+dfsg-1 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | HIGH7.5 | libldap-common 2.6.10+dfsg-1 No fix yet | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2015-3276 | HIGH7.5 | libldap-dev 2.6.10+dfsg-1 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | HIGH7.5 | libldap-dev 2.6.10+dfsg-1 No fix yet | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2015-3276 | HIGH7.5 | libldap2 2.6.10+dfsg-1 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | HIGH7.5 | libldap2 2.6.10+dfsg-1 No fix yet | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-18232 | HIGH7.48 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-18494 | HIGH7.48 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2020-18232 | HIGH7.48 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-18494 | HIGH7.48 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2020-18232 | HIGH7.48 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-18494 | HIGH7.48 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2020-18232 | HIGH7.48 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-18494 | HIGH7.48 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2020-18232 | HIGH7.48 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-18494 | HIGH7.48 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2020-18232 | HIGH7.48 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-18494 | HIGH7.48 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2020-18232 | HIGH7.48 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-18494 | HIGH7.48 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-44690 | HIGH7.31 | libunbound8 1.22.0-2+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-57432 | HIGH7.14 | libperl5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2153 | MEDIUM6.88 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-2153 | MEDIUM6.88 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-2153 | MEDIUM6.88 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-2153 | MEDIUM6.88 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-2153 | MEDIUM6.88 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-2153 | MEDIUM6.88 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-2153 | MEDIUM6.88 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25210 | MEDIUM6.63 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25210 | MEDIUM6.63 | libexpat1-dev 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2308 | MEDIUM6.63 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-2309 | MEDIUM6.63 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2310 | MEDIUM6.63 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6516 | MEDIUM6.63 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6818 | MEDIUM6.63 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6856 | MEDIUM6.63 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6857 | MEDIUM6.63 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-26200 | MEDIUM6.63 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34734 | MEDIUM6.63 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2308 | MEDIUM6.63 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-2309 | MEDIUM6.63 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2310 | MEDIUM6.63 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6516 | MEDIUM6.63 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6818 | MEDIUM6.63 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6856 | MEDIUM6.63 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6857 | MEDIUM6.63 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-26200 | MEDIUM6.63 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34734 | MEDIUM6.63 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2308 | MEDIUM6.63 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-2309 | MEDIUM6.63 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2310 | MEDIUM6.63 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6516 | MEDIUM6.63 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6818 | MEDIUM6.63 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6856 | MEDIUM6.63 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6857 | MEDIUM6.63 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-26200 | MEDIUM6.63 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34734 | MEDIUM6.63 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2308 | MEDIUM6.63 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-2309 | MEDIUM6.63 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2310 | MEDIUM6.63 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6516 | MEDIUM6.63 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6818 | MEDIUM6.63 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6856 | MEDIUM6.63 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6857 | MEDIUM6.63 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-26200 | MEDIUM6.63 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34734 | MEDIUM6.63 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2308 | MEDIUM6.63 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-2309 | MEDIUM6.63 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2310 | MEDIUM6.63 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6516 | MEDIUM6.63 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6818 | MEDIUM6.63 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6856 | MEDIUM6.63 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6857 | MEDIUM6.63 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-26200 | MEDIUM6.63 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34734 | MEDIUM6.63 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2308 | MEDIUM6.63 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-2309 | MEDIUM6.63 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2310 | MEDIUM6.63 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6516 | MEDIUM6.63 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6818 | MEDIUM6.63 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6856 | MEDIUM6.63 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6857 | MEDIUM6.63 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-26200 | MEDIUM6.63 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34734 | MEDIUM6.63 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2308 | MEDIUM6.63 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-2309 | MEDIUM6.63 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2310 | MEDIUM6.63 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6516 | MEDIUM6.63 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6818 | MEDIUM6.63 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6856 | MEDIUM6.63 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6857 | MEDIUM6.63 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-26200 | MEDIUM6.63 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34734 | MEDIUM6.63 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48962 | MEDIUM6.63 | libperl5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11332 | MEDIUM6.63 | ansible-core 2.21.0 fixed in 2.16.19rc1, 2.18.18rc1, 2.19.11rc1, 2.20.7rc1, 2.21.1rc1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libbinutils 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libctf-nobfd0 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libctf0 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libgprofng0 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15671 | MEDIUM6.5 | libhdf5-310 1.14.5+repack-3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-17433 | MEDIUM6.5 | libhdf5-310 1.14.5+repack-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-17436 | MEDIUM6.5 | libhdf5-310 1.14.5+repack-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-8397 | MEDIUM6.5 | libhdf5-310 1.14.5+repack-3 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15671 | MEDIUM6.5 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-17433 | MEDIUM6.5 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-17436 | MEDIUM6.5 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-8397 | MEDIUM6.5 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15671 | MEDIUM6.5 | libhdf5-dev 1.14.5+repack-3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-17433 | MEDIUM6.5 | libhdf5-dev 1.14.5+repack-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-17436 | MEDIUM6.5 | libhdf5-dev 1.14.5+repack-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-8397 | MEDIUM6.5 | libhdf5-dev 1.14.5+repack-3 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15671 | MEDIUM6.5 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-17433 | MEDIUM6.5 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-17436 | MEDIUM6.5 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-8397 | MEDIUM6.5 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15671 | MEDIUM6.5 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-17433 | MEDIUM6.5 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-17436 | MEDIUM6.5 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-8397 | MEDIUM6.5 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15671 | MEDIUM6.5 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-17433 | MEDIUM6.5 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-17436 | MEDIUM6.5 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-8397 | MEDIUM6.5 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15671 | MEDIUM6.5 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-17433 | MEDIUM6.5 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-17436 | MEDIUM6.5 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-8397 | MEDIUM6.5 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libsframe1 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libbinutils 2.44-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libctf-nobfd0 2.44-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libctf0 2.44-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45186 | MEDIUM6.38 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45186 | MEDIUM6.38 | libexpat1-dev 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libgprofng0 2.44-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-26197 | MEDIUM6.38 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-26197 | MEDIUM6.38 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-26197 | MEDIUM6.38 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-26197 | MEDIUM6.38 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-26197 | MEDIUM6.38 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-26197 | MEDIUM6.38 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-26197 | MEDIUM6.38 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42497 | MEDIUM6.38 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM6.38 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM6.38 | libpython3.13 3.13.5-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | libpython3.13 3.13.5-2+deb13u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM6.38 | libpython3.13-dev 3.13.5-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | libpython3.13-dev 3.13.5-2+deb13u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM6.38 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM6.38 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libsframe1 2.44-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-32665 | MEDIUM6.38 | libunbound8 1.22.0-2+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-40691 | MEDIUM6.38 | libunbound8 1.22.0-2+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-55973 | MEDIUM6.38 | libunbound8 1.22.0-2+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM6.38 | python3.13 3.13.5-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | python3.13 3.13.5-2+deb13u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM6.38 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-54369 | MEDIUM6.03 | libacl1 2.3.2-2+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.13 3.13.5-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.13 3.13.5-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.13-dev 3.13.5-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.13-dev 3.13.5-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | python3.13 3.13.5-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | python3.13 3.13.5-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libbinutils 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libctf-nobfd0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libctf0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libgprofng0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libgssrpc4t64 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkadm5clnt-mit12 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkadm5srv-mit12 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkdb5-10t64 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5-dev 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libsframe1 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1-6 4.20.0-2 fixed in 4.20.0-2+deb13u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1-6-dev 4.20.0-2 fixed in 4.20.0-2+deb13u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56132 | MEDIUM5.87 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM5.87 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56404 | MEDIUM5.87 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56405 | MEDIUM5.87 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM5.87 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56407 | MEDIUM5.87 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56410 | MEDIUM5.87 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56411 | MEDIUM5.87 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56132 | MEDIUM5.87 | libexpat1-dev 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM5.87 | libexpat1-dev 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56404 | MEDIUM5.87 | libexpat1-dev 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56405 | MEDIUM5.87 | libexpat1-dev 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM5.87 | libexpat1-dev 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56407 | MEDIUM5.87 | libexpat1-dev 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56410 | MEDIUM5.87 | libexpat1-dev 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56411 | MEDIUM5.87 | libexpat1-dev 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | libldap-common 2.6.10+dfsg-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | libldap-dev 2.6.10+dfsg-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | libldap2 2.6.10+dfsg-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls-dane0t64 3.8.9-3+deb13u4 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls-openssl27t64 3.8.9-3+deb13u4 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls28-dev 3.8.9-3+deb13u4 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libbinutils 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf-nobfd0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libgprofng0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-26199 | MEDIUM5.52 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-46243 | MEDIUM5.52 | libhdf5-310 1.14.5+repack-3 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-26199 | MEDIUM5.52 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-46243 | MEDIUM5.52 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-26199 | MEDIUM5.52 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-46243 | MEDIUM5.52 | libhdf5-dev 1.14.5+repack-3 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-26199 | MEDIUM5.52 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-46243 | MEDIUM5.52 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-26199 | MEDIUM5.52 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-46243 | MEDIUM5.52 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-26199 | MEDIUM5.52 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-46243 | MEDIUM5.52 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-26199 | MEDIUM5.52 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-46243 | MEDIUM5.52 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-15649 | MEDIUM5.52 | libperl5.40 5.40.1-6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | libpython3.13 3.13.5-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-7774 | MEDIUM5.52 | libpython3.13 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | libpython3.13-dev 3.13.5-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-7774 | MEDIUM5.52 | libpython3.13-dev 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-7774 | MEDIUM5.52 | libpython3.13-minimal 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-7774 | MEDIUM5.52 | libpython3.13-stdlib 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libsframe1 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | python3.13 3.13.5-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-7774 | MEDIUM5.52 | python3.13 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-7774 | MEDIUM5.52 | python3.13-minimal 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libbinutils 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libbinutils 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libbinutils 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf-nobfd0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libctf-nobfd0 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libctf-nobfd0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libctf0 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libctf0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libgprofng0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libgprofng0 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libgprofng0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10809 | MEDIUM5.5 | libhdf5-310 1.14.5+repack-3 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10812 | MEDIUM5.5 | libhdf5-310 1.14.5+repack-3 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10809 | MEDIUM5.5 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10812 | MEDIUM5.5 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10809 | MEDIUM5.5 | libhdf5-dev 1.14.5+repack-3 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10812 | MEDIUM5.5 | libhdf5-dev 1.14.5+repack-3 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10809 | MEDIUM5.5 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10812 | MEDIUM5.5 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10809 | MEDIUM5.5 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10812 | MEDIUM5.5 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10809 | MEDIUM5.5 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10812 | MEDIUM5.5 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10809 | MEDIUM5.5 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10812 | MEDIUM5.5 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libsframe1 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libsframe1 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libsframe1 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54370 | MEDIUM5.35 | libacl1 2.3.2-2+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | MEDIUM5.35 | libattr1 1:2.5.2-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-bin 2.41-12+deb13u3 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6 2.41-12+deb13u3 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6-dev 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6-dev 2.41-12+deb13u3 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-59375 | MEDIUM5.3 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-59375 | MEDIUM5.3 | libexpat1-dev 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | libp11-kit-dev 0.25.5-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | libp11-kit0 0.25.5-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libsmartcols1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | MEDIUM5.02 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56412 | MEDIUM5.02 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | MEDIUM5.02 | libexpat1-dev 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56412 | MEDIUM5.02 | libexpat1-dev 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssrpc4t64 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-44904 | MEDIUM5.02 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-44905 | MEDIUM5.02 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-44904 | MEDIUM5.02 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-44905 | MEDIUM5.02 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-44904 | MEDIUM5.02 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-44905 | MEDIUM5.02 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-44904 | MEDIUM5.02 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-44905 | MEDIUM5.02 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-44904 | MEDIUM5.02 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-44905 | MEDIUM5.02 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-44904 | MEDIUM5.02 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-44905 | MEDIUM5.02 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-44904 | MEDIUM5.02 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-44905 | MEDIUM5.02 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27601 | MEDIUM5.02 | libjs-underscore 1.13.4~dfsg+~1.11.4-3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkadm5clnt-mit12 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkadm5srv-mit12 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkdb5-10t64 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-dev 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | libpython3.13 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | libpython3.13-dev 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | libpython3.13-minimal 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | libpython3.13-stdlib 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-14586 | MEDIUM5.02 | libunbound8 1.22.0-2+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52863 | MEDIUM5.02 | libunbound8 1.22.0-2+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55990 | MEDIUM5.02 | libunbound8 1.22.0-2+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-55991 | MEDIUM5.02 | libunbound8 1.22.0-2+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | python3.13 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | python3.13-minimal 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libbinutils 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | MEDIUM4.76 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf-nobfd0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | MEDIUM4.76 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | MEDIUM4.76 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libgprofng0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | MEDIUM4.76 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libsframe1 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | MEDIUM4.76 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-6110 | MEDIUM4.69 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 20.9% High Exploitation Risk | Post-Exploit |
| CVE-2025-11081 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libblkid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1 2.7.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32776 | MEDIUM4.67 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | MEDIUM4.67 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | MEDIUM4.67 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1-dev 2.7.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32776 | MEDIUM4.67 | libexpat1-dev 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | MEDIUM4.67 | libexpat1-dev 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | MEDIUM4.67 | libexpat1-dev 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-17572 | MEDIUM4.67 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-45829 | MEDIUM4.67 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-45832 | MEDIUM4.67 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-2915 | MEDIUM4.67 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2924 | MEDIUM4.67 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2925 | MEDIUM4.67 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2926 | MEDIUM4.67 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6858 | MEDIUM4.67 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7067 | MEDIUM4.67 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7068 | MEDIUM4.67 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7069 | MEDIUM4.67 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-29043 | MEDIUM4.67 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-17572 | MEDIUM4.67 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-45829 | MEDIUM4.67 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-45832 | MEDIUM4.67 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-2915 | MEDIUM4.67 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2924 | MEDIUM4.67 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2925 | MEDIUM4.67 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2926 | MEDIUM4.67 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6858 | MEDIUM4.67 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7067 | MEDIUM4.67 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7068 | MEDIUM4.67 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7069 | MEDIUM4.67 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-29043 | MEDIUM4.67 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-17572 | MEDIUM4.67 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-45829 | MEDIUM4.67 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-45832 | MEDIUM4.67 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-2915 | MEDIUM4.67 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2924 | MEDIUM4.67 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2925 | MEDIUM4.67 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2926 | MEDIUM4.67 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6858 | MEDIUM4.67 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7067 | MEDIUM4.67 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7068 | MEDIUM4.67 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7069 | MEDIUM4.67 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-29043 | MEDIUM4.67 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-17572 | MEDIUM4.67 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-45829 | MEDIUM4.67 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-45832 | MEDIUM4.67 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-2915 | MEDIUM4.67 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2924 | MEDIUM4.67 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2925 | MEDIUM4.67 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2926 | MEDIUM4.67 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6858 | MEDIUM4.67 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7067 | MEDIUM4.67 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7068 | MEDIUM4.67 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7069 | MEDIUM4.67 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-29043 | MEDIUM4.67 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-17572 | MEDIUM4.67 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-45829 | MEDIUM4.67 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-45832 | MEDIUM4.67 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-2915 | MEDIUM4.67 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2924 | MEDIUM4.67 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2925 | MEDIUM4.67 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2926 | MEDIUM4.67 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6858 | MEDIUM4.67 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7067 | MEDIUM4.67 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7068 | MEDIUM4.67 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7069 | MEDIUM4.67 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-29043 | MEDIUM4.67 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-17572 | MEDIUM4.67 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-45829 | MEDIUM4.67 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-45832 | MEDIUM4.67 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-2915 | MEDIUM4.67 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2924 | MEDIUM4.67 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2925 | MEDIUM4.67 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2926 | MEDIUM4.67 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6858 | MEDIUM4.67 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7067 | MEDIUM4.67 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7068 | MEDIUM4.67 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7069 | MEDIUM4.67 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-29043 | MEDIUM4.67 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-17572 | MEDIUM4.67 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-45829 | MEDIUM4.67 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-45832 | MEDIUM4.67 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-2915 | MEDIUM4.67 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2924 | MEDIUM4.67 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2925 | MEDIUM4.67 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2926 | MEDIUM4.67 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6858 | MEDIUM4.67 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7067 | MEDIUM4.67 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7068 | MEDIUM4.67 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7069 | MEDIUM4.67 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-29043 | MEDIUM4.67 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | libpython3.13 3.13.5-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | libpython3.13-dev 3.13.5-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libsmartcols1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | python3.13 3.13.5-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g-dev 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7598 | MEDIUM4.64 | libssh2-1-dev 1.11.1-1 fixed in 1.11.1-1+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-7598 | MEDIUM4.64 | libssh2-1t64 1.11.1-1 fixed in 1.11.1-1+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58055 | MEDIUM4.59 | libnghttp2-14 1.64.0-1.1+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58055 | MEDIUM4.59 | libnghttp2-dev 1.64.0-1.1+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-24975 | MEDIUM4.5 | git 1:2.47.3-0+deb13u1 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6951 | MEDIUM4.5 | patch 2.8-2 No fix yet | 8.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6952 | MEDIUM4.5 | patch 2.8-2 No fix yet | 8.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1147 | MEDIUM4.5 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libblkid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-2912 | MEDIUM4.5 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2913 | MEDIUM4.5 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6269 | MEDIUM4.5 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6270 | MEDIUM4.5 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2912 | MEDIUM4.5 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2913 | MEDIUM4.5 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6269 | MEDIUM4.5 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6270 | MEDIUM4.5 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2912 | MEDIUM4.5 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2913 | MEDIUM4.5 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6269 | MEDIUM4.5 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6270 | MEDIUM4.5 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2912 | MEDIUM4.5 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2913 | MEDIUM4.5 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6269 | MEDIUM4.5 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6270 | MEDIUM4.5 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2912 | MEDIUM4.5 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2913 | MEDIUM4.5 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6269 | MEDIUM4.5 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6270 | MEDIUM4.5 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2912 | MEDIUM4.5 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2913 | MEDIUM4.5 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6269 | MEDIUM4.5 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6270 | MEDIUM4.5 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2912 | MEDIUM4.5 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2913 | MEDIUM4.5 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6269 | MEDIUM4.5 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6270 | MEDIUM4.5 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | liblzma5 5.8.1-1 fixed in 5.8.1-1+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libmount1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-12087 | MEDIUM4.5 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.13 3.13.5-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | libpython3.13 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4360 | MEDIUM4.5 | libpython3.13 3.13.5-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.13-dev 3.13.5-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | libpython3.13-dev 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4360 | MEDIUM4.5 | libpython3.13-dev 3.13.5-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | libpython3.13-minimal 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4360 | MEDIUM4.5 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | libpython3.13-stdlib 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4360 | MEDIUM4.5 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libsmartcols1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libsmartcols1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libudev1 257.13-1~deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-50251 | MEDIUM4.5 | libunbound8 1.22.0-2+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libuuid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | python3.13 3.13.5-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | python3.13 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4360 | MEDIUM4.5 | python3.13 3.13.5-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | python3.13-minimal 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4360 | MEDIUM4.5 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-52005 | MEDIUM4.49 | git 1:2.47.3-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2021-45346 | MEDIUM4.3 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-57432 | MEDIUM4.28 | perl 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | MEDIUM4.28 | perl-base 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | MEDIUM4.25 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM4.25 | libbz2-1.0 1.0.8-6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libgssrpc4t64 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-17573 | MEDIUM4.25 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-17574 | MEDIUM4.25 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-17573 | MEDIUM4.25 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-17574 | MEDIUM4.25 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-17573 | MEDIUM4.25 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-17574 | MEDIUM4.25 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-17573 | MEDIUM4.25 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-17574 | MEDIUM4.25 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-17573 | MEDIUM4.25 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-17574 | MEDIUM4.25 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-17573 | MEDIUM4.25 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-17574 | MEDIUM4.25 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-17573 | MEDIUM4.25 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-17574 | MEDIUM4.25 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkadm5clnt-mit12 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkadm5srv-mit12 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkdb5-10t64 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5-dev 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48959 | MEDIUM4.25 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48961 | MEDIUM4.25 | libperl5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2020-15719 | MEDIUM4.2 | libldap-common 2.6.10+dfsg-1 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-15719 | MEDIUM4.2 | libldap-dev 2.6.10+dfsg-1 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-15719 | MEDIUM4.2 | libldap2 2.6.10+dfsg-1 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-8286 | MEDIUM4.13 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-56416 | MEDIUM4.08 | libunbound8 1.22.0-2+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | MEDIUM4 | libldap-common 2.6.10+dfsg-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | MEDIUM4 | libldap-dev 2.6.10+dfsg-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | MEDIUM4 | libldap2 2.6.10+dfsg-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-bin 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6-dev 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-11082 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18220 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18220 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2018-20712 | LOW3.9 | binutils 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20712 | LOW3.9 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2025-15661 | LOW3.9 | libssh2-1-dev 1.11.1-1 fixed in 1.11.1-1+deb13u1 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-15661 | LOW3.9 | libssh2-1t64 1.11.1-1 fixed in 1.11.1-1+deb13u1 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2008-3234 | LOW3.9 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils 2.44-3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW3.82 | gzip 1.13-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl3t64-gnutls 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl3t64-gnutls 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9079 | LOW3.82 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl4-openssl-dev 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl4-openssl-dev 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9079 | LOW3.82 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9079 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-55199 | LOW3.82 | libssh2-1-dev 1.11.1-1 fixed in 1.11.1-1+deb13u1 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-55199 | LOW3.82 | libssh2-1t64 1.11.1-1 fixed in 1.11.1-1+deb13u1 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-59999 | LOW3.82 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-60000 | LOW3.82 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-56131 | LOW3.82 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56131 | LOW3.82 | libexpat1-dev 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | libpython3.13 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | libpython3.13-dev 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | libpython3.13-minimal 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | libpython3.13-stdlib 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | python3.13 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | python3.13-minimal 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | LOW3.77 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW3.72 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW3.72 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW3.72 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW3.7 | libapt-pkg7.0 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-3441 | LOW3.62 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2005-2541 | LOW3.6 | tar 1.35+dfsg-3.1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2020-14145 | LOW3.54 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6-dev 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2010-4651 | LOW3.48 | patch 2.8-2 No fix yet | 4.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl3t64-gnutls 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | libcurl3t64-gnutls 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl4-openssl-dev 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | libcurl4-openssl-dev 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils 2.44-3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl3t64-gnutls 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl3t64-gnutls 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl3t64-gnutls 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl3t64-gnutls 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl4-openssl-dev 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl4-openssl-dev 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl4-openssl-dev 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl4-openssl-dev 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-66032 | LOW3.31 | libssh2-1-dev 1.11.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-66033 | LOW3.31 | libssh2-1-dev 1.11.1-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-66032 | LOW3.31 | libssh2-1t64 1.11.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-66033 | LOW3.31 | libssh2-1t64 1.11.1-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-59998 | LOW3.31 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-60001 | LOW3.31 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl 5.40.1-6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl-base 5.40.1-6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3805 | LOW3.21 | libcurl3t64-gnutls 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3805 | LOW3.21 | libcurl4-openssl-dev 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3805 | LOW3.21 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2016-20012 | LOW3.18 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 5.3% Low-Moderate Risk | Post-Exploit |
| CVE-2018-15919 | LOW3.18 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 3.6% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-bin 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2018-14034 | LOW3.17 | libhdf5-310 1.14.5+repack-3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2018-14035 | LOW3.17 | libhdf5-310 1.14.5+repack-3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2018-14034 | LOW3.17 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2018-14035 | LOW3.17 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2018-14034 | LOW3.17 | libhdf5-dev 1.14.5+repack-3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2018-14035 | LOW3.17 | libhdf5-dev 1.14.5+repack-3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2018-14034 | LOW3.17 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2018-14035 | LOW3.17 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2018-14034 | LOW3.17 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2018-14035 | LOW3.17 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2018-14034 | LOW3.17 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2018-14035 | LOW3.17 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2018-14034 | LOW3.17 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2018-14035 | LOW3.17 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1152 | LOW3.15 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-41080 | LOW3.15 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41080 | LOW3.15 | libexpat1-dev 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-41637 | LOW3.15 | libunbound8 1.22.0-2+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42955 | LOW3.15 | libunbound8 1.22.0-2+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46582 | LOW3.15 | libunbound8 1.22.0-2+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50046 | LOW3.15 | libunbound8 1.22.0-2+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50243 | LOW3.15 | libunbound8 1.22.0-2+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54478 | LOW3.15 | libunbound8 1.22.0-2+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56444 | LOW3.15 | libunbound8 1.22.0-2+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.11 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56391 | LOW3.11 | coreutils 9.7-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2020-15778 | LOW3.07 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 13.0% High Exploitation Risk | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-66034 | LOW3.01 | libssh2-1-dev 1.11.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-66034 | LOW3.01 | libssh2-1t64 1.11.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-13346 | LOW3.01 | python3-pip 25.1.1+dfsg-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2018-1000021 | LOW3 | git 1:2.47.3-0+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2007-2243 | LOW3 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-55200 | LOW2.99 | libssh2-1-dev 1.11.1-1 fixed in 1.11.1-1+deb13u1 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-55200 | LOW2.99 | libssh2-1t64 1.11.1-1 fixed in 1.11.1-1+deb13u1 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-6357 | LOW2.96 | python3-pip 25.1.1+dfsg-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl3t64-gnutls 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl4-openssl-dev 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-60002 | LOW2.87 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils 2.44-3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-15003 | LOW2.86 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-15003 | LOW2.86 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-45261 | LOW2.8 | patch 2.8-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-56288 | LOW2.8 | patch 2.8-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56289 | LOW2.8 | patch 2.8-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-8643 | LOW2.8 | python3-pip 25.1.1+dfsg-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.35+dfsg-3.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2914 | LOW2.8 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6750 | LOW2.8 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6816 | LOW2.8 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6817 | LOW2.8 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2914 | LOW2.8 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6750 | LOW2.8 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6816 | LOW2.8 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6817 | LOW2.8 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2914 | LOW2.8 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6750 | LOW2.8 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6816 | LOW2.8 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6817 | LOW2.8 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2914 | LOW2.8 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6750 | LOW2.8 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6816 | LOW2.8 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6817 | LOW2.8 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2914 | LOW2.8 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6750 | LOW2.8 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6816 | LOW2.8 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6817 | LOW2.8 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2914 | LOW2.8 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6750 | LOW2.8 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6816 | LOW2.8 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6817 | LOW2.8 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2914 | LOW2.8 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6750 | LOW2.8 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6816 | LOW2.8 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6817 | LOW2.8 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW2.8 | libperl5.40 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.13 3.13.5-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.13-dev 3.13.5-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 257.13-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | python3.13 3.13.5-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13221 | LOW2.78 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.78 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-59995 | LOW2.75 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59996 | LOW2.75 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59997 | LOW2.75 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | bsdutils 1:2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl3t64-gnutls 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl3t64-gnutls 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl3t64-gnutls 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl4-openssl-dev 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl4-openssl-dev 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl4-openssl-dev 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-66035 | LOW2.7 | libssh2-1-dev 1.11.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-66035 | LOW2.7 | libssh2-1t64 1.11.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | mount 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-8869 | LOW2.7 | python3-pip 25.1.1+dfsg-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34743 | LOW2.7 | xz-utils 5.8.1-1 fixed in 5.8.1-1+deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW2.63 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2007-2768 | LOW2.58 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 8.7% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-42250 | LOW2.55 | bzip2 1.0.8-6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3219 | LOW2.55 | python3-pip 25.1.1+dfsg-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 9.7-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.13-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW2.38 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5278 | LOW2.24 | coreutils 9.7-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW2.24 | coreutils 9.7-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-24515 | LOW2.12 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-24515 | LOW2.12 | libexpat1-dev 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1703 | LOW1.99 | python3-pip 25.1.1+dfsg-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-base 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13221 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42496 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-52005 | NONE0 | git-man 1:2.47.3-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-14034 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2018-14035 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-9151 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2019-9152 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2020-18232 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2020-18494 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-63797 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-57432 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-2153 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-11082 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18220 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-2308 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-2309 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-2310 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6516 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-6818 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6856 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6857 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-26200 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-34734 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncursesw6 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2013-7445 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-19449 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-19814 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-3847 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-21803 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-38137 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38187 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38206 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38421 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39859 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39862 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39958 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23208 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31493 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46279 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53089 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53109 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53118 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53157 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53359 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-53362 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53366 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63794 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63804 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64530 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64531 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64600 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12456 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19378 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-11725 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-26934 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-25265 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-3238 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-26242 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-3640 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-48962 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66864 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | binutils-common 2.44-3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-24975 | NONE0 | git-man 1:2.47.3-0+deb13u1 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-26197 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2018-5709 | NONE0 | krb5-locales 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-5709 | NONE0 | krb5-multidev 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-19070 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-0400 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-42497 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9538 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-15308 | NONE0 | python3.13-dev 3.13.5-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-7210 | NONE0 | python3.13-dev 3.13.5-2+deb13u2 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-3441 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-58015 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22104 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38204 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38636 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23102 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23327 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31568 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46130 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53179 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53330 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40064 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43414 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2008-4609 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 32.1% High Exploitation Risk | Not Applicable |
| CVE-2025-15366 | NONE0 | python3.13-dev 3.13.5-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15367 | NONE0 | python3.13-dev 3.13.5-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-3864 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-31419 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43198 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46054 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46181 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46242 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-52991 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53000 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53091 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53277 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53398 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53399 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63795 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63824 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63829 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63830 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63831 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63879 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63970 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64017 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64191 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64265 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64268 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64271 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64276 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64277 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64287 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64296 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64303 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64304 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64364 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64375 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64378 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64382 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64383 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64385 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64387 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64434 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64483 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64490 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64534 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64552 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64556 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64558 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40158 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40168 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46317 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46325 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46330 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52953 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52956 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53005 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53009 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53078 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53224 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53246 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53250 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53260 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53341 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53361 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53381 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53384 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53388 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53391 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53392 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53397 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63800 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63801 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63802 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63807 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63808 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63809 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63823 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63826 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63940 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63941 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63979 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64024 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64068 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64117 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64160 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64189 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64192 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64216 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64247 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64251 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64255 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64266 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64280 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64283 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64286 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64298 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64305 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64306 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64312 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64317 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64319 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64320 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64321 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64322 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64323 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64324 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64340 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64341 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64342 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64354 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64355 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64372 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64377 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64379 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64380 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64384 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64401 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64402 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64414 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64418 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64422 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64448 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64456 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64470 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64471 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64473 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64475 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64481 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64508 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64520 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64539 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64543 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64548 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64551 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64554 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64557 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64559 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64560 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-1247 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2961 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45884 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45885 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40130 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-36694 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6238 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2018-20712 | NONE0 | binutils-common 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-32256 | NONE0 | binutils-common 2.44-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-26199 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2018-15671 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-17433 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2018-17436 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2019-8397 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-46243 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-6240 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2025-68729 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64535 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-0564 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-15649 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-11972 | NONE0 | python3.13-dev 3.13.5-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7774 | NONE0 | python3.13-dev 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-40074 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45932 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53090 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53092 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-44032 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44033 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-3397 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40146 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | liblastlog2-2 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40355 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68319 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43197 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1153 | NONE0 | binutils-common 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-44904 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-44905 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-26458 | NONE0 | krb5-locales 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | krb5-locales 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-26458 | NONE0 | krb5-multidev 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | krb5-multidev 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-13151 | NONE0 | libtasn1-doc 4.20.0-2 fixed in 4.20.0-2+deb13u1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-1121 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-3714 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-9669 | NONE0 | python3.13-dev 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-23039 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1178 | NONE0 | binutils-common 2.44-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-15003 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | binutils-common 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20673 | NONE0 | binutils-common 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-9996 | NONE0 | binutils-common 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-11081 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6844 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-17572 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2020-10809 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2020-10812 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2021-45829 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-45832 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-2915 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-2924 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-2925 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-2926 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6858 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-7067 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-7068 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-7069 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-29043 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | liblastlog2-2 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31082 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-37454 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-2193 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-25740 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-52560 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56709 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58074 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58094 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58095 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21752 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21807 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21949 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22108 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22109 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22127 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23131 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23132 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23135 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37743 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37746 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37880 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38029 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38036 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38041 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38042 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38064 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38132 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38140 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38199 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38203 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38205 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38207 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38237 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38261 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38284 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38311 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38359 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38597 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38605 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38621 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39677 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39762 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39775 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39789 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39822 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39830 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39833 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39834 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39910 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39925 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39933 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40102 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68209 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68236 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68304 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68353 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68368 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68730 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71117 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71141 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71188 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71202 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71227 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71285 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71302 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71313 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71315 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23007 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23017 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23137 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23152 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23217 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23259 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23265 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23371 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23377 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23385 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23472 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31435 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31526 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31537 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31562 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31579 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31591 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31592 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31630 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31692 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31732 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31771 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31777 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43009 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43010 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43022 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43029 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43034 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43042 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43048 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43083 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43101 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43115 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43118 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43127 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43172 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43191 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43204 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43213 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43216 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43234 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43272 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43294 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43298 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43299 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43301 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43308 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43309 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43310 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43311 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43325 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43326 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43337 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43344 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43346 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43352 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43353 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43355 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43416 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43443 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43463 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43464 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43465 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43485 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45897 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45901 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45934 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45944 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45961 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45963 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46014 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46032 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46044 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46059 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46066 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46071 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46093 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46096 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46148 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46153 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46171 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46228 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46245 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46252 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46256 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46302 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46314 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52937 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52944 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52975 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52988 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52994 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53017 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53018 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53027 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53070 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53101 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53102 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53103 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53104 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53106 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53107 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53113 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53139 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53142 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53151 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53163 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53167 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53226 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53258 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53281 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53285 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53292 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53297 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53313 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53321 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53325 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53327 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53365 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53377 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53382 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53385 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53393 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53394 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53400 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53402 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53403 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63798 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63803 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63822 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63832 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63858 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64006 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64036 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64038 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64058 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64067 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64076 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64077 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64079 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64159 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64190 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64205 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64206 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64210 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64212 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64245 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64253 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64279 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64284 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64289 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64290 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64299 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64307 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64308 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64309 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64310 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64313 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64315 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64316 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64326 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64327 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64328 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64329 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64330 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64333 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64336 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64338 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64343 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64344 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64346 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64347 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64351 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64357 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64360 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64362 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64363 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64365 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64368 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64369 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64373 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64374 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64381 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64403 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64404 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64405 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64406 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64407 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64408 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64409 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64411 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64412 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64413 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64416 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64423 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64424 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64433 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64436 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64452 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64454 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64455 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64458 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64463 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64472 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64477 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64478 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64479 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64487 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64496 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64507 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64510 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64529 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64540 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64541 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64542 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64545 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64546 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64547 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64553 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64555 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2008-2544 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2011-4915 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2011-4916 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2011-4917 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9892 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9900 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-10723 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-8660 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2017-13693 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-13694 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12928 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12378 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12379 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12380 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12381 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12382 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12455 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-4543 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-31081 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31085 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40086 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68193 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68359 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53284 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63810 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63821 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63853 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63872 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63998 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63999 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64060 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64066 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64070 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64078 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64146 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64187 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64213 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64227 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64244 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64254 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64256 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64275 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64294 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64297 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64301 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64332 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64334 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64335 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64352 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64370 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64376 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64388 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64415 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64417 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64419 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64428 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64430 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64435 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64465 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64474 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64476 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64480 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64482 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64486 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64488 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64489 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64511 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64512 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64513 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64514 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64537 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64544 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-24049 | NONE0 | python3-wheel 0.46.1-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-0864 | NONE0 | python3.13-dev 3.13.5-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1147 | NONE0 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-2912 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-2913 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6269 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6270 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | liblastlog2-2 2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | liblastlog2-2 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64538 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12087 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-12781 | NONE0 | python3.13-dev 3.13.5-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-3276 | NONE0 | python3.13-dev 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-4360 | NONE0 | python3.13-dev 3.13.5-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40217 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40338 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1176 | NONE0 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2018-1000021 | NONE0 | git-man 1:2.47.3-0+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-17573 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-17574 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-11850 | NONE0 | krb5-locales 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11850 | NONE0 | krb5-multidev 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2004-0230 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 80.3% Actively Exploited | Not Applicable |
| CVE-2010-4563 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-48959 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-48961 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2005-3660 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2007-5686 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules-bin 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-runtime 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam0g 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | liblastlog2-2 2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-20794 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-24864 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37906 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40139 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68745 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71074 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23348 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43053 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46017 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46272 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53108 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2017-0630 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-16230 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16234 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-15213 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-4010 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2012-4542 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68360 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-1502 | NONE0 | python3.13-dev 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2020-14304 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-17977 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2010-5321 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-41848 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-16089 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16229 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16231 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16232 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-16233 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-56433 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-35501 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66861 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66862 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-2914 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-6750 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6816 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6817 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncursesw6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2015-2877 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-68751 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-bin 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2011-4116 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-3479 | NONE0 | python3.13-dev 3.13.5-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-69644 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40113 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-11191 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2007-3719 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.2.37-2+b9 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53910 | NONE0 | diffutils 1:3.10-4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-2923 | NONE0 | hdf5-helpers 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56408 | NONE0 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56409 | NONE0 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56408 | NONE0 | libexpat1-dev 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56409 | NONE0 | libexpat1-dev 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-2923 | NONE0 | libhdf5-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-2923 | NONE0 | libhdf5-cpp-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-2923 | NONE0 | libhdf5-dev 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-2923 | NONE0 | libhdf5-fortran-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-2923 | NONE0 | libhdf5-hl-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-2923 | NONE0 | libhdf5-hl-cpp-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-2923 | NONE0 | libhdf5-hl-fortran-310 1.14.5+repack-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-57433 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | libpython3.13 3.13.5-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.13 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | libpython3.13 3.13.5-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6879 | NONE0 | libpython3.13 3.13.5-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | libpython3.13-dev 3.13.5-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.13-dev 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | libpython3.13-dev 3.13.5-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6879 | NONE0 | libpython3.13-dev 3.13.5-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6879 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6879 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-11822 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50812 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50813 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-44621 | NONE0 | libunbound8 1.22.0-2+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50045 | NONE0 | libunbound8 1.22.0-2+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-50248 | NONE0 | libunbound8 1.22.0-2+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55717 | NONE0 | libunbound8 1.22.0-2+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-44687 | NONE0 | libunbound8 1.22.0-2+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55708 | NONE0 | libunbound8 1.22.0-2+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43263 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53010 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64437 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40098 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68174 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68318 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68376 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68735 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52983 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53368 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53383 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-53386 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53387 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53389 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53390 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53401 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63796 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63805 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63806 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63811 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63812 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63814 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63815 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63816 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63817 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63818 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63819 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63825 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63827 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63828 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63833 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63834 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63835 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63836 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63857 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63859 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64082 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64154 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64188 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64241 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64246 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64248 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64249 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64250 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64252 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64269 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64270 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64272 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64273 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64274 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64318 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64331 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64337 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64345 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64348 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64350 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64358 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64359 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64361 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64367 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64371 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64386 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64389 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64390 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64391 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64392 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64393 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64394 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64395 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64396 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64397 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64398 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64399 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64400 | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64420 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64421 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64425 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64429 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64432 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64438 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64440 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64441 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64442 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64443 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64444 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64445 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64446 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64449 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64450 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64457 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64461 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64462 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64468 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64469 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64484 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64493 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64494 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64495 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64497 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64499 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64500 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64503 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64504 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64505 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64509 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64532 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64533 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64536 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64549 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64550 | NONE0 | linux-libc-dev 6.12.94-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.12.94-1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login.defs 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-57433 | NONE0 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | python3.13 3.13.5-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.13 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | python3.13 3.13.5-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6879 | NONE0 | python3.13 3.13.5-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | python3.13-dev 3.13.5-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.13-dev 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | python3.13-dev 3.13.5-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6879 | NONE0 | python3.13-dev 3.13.5-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.13-minimal 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6879 | NONE0 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| TEMP-0517018-A83CE6 | NONE0 | sysvinit-utils 3.14-4 No fix yet | — | Not Applicable |
| TEMP-0290435-0B57B5 | NONE0 | tar 1.35+dfsg-3.1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.