Last scanned:
This base/runtime image carries significant vulnerabilities that any image built on it would inherit; remediate them in the final image before production. The inherited packages include serious image-parsing and glibc issues, such as CVE-2023-5841 and CVE-2019-1010023, which could let an attacker trigger heap overflows or code execution if the final image processes untrusted files or runs ldd on malicious ELF files. The glibc ldd issue is fully mitigated by never running ldd on untrusted ELF files, and the OpenEXR issue is avoided by not parsing untrusted OpenEXR files. These findings matter only when the built image actually invokes those libraries on attacker-controlled inputs; otherwise, they remain inherited but lower-risk. Note: this is a general-purpose base/runtime image — many findings live in components that an application built on top may never load, so actual exploitability depends on the final image. For an accurate risk picture, re-scan the final application image with context.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2023-5841 | CRITICAL9.1 | libopenexr-dev 3.1.5-5 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc-bin 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc6 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc6-dev 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9580 | HIGH8.8 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9581 | HIGH8.8 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2018-16376 | HIGH8.8 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9580 | HIGH8.8 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9581 | HIGH8.8 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2018-16376 | HIGH8.8 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42217 | HIGH8.33 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42217 | HIGH8.33 | libopenexr-dev 3.1.5-5 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-6653 | HIGH8.33 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6653 | HIGH8.33 | libxml2-dev 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31486 | HIGH8.1 | libperl5.36 5.36.0-7+deb12u4 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42216 | HIGH7.73 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42216 | HIGH7.73 | libopenexr-dev 3.1.5-5 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-7458 | HIGH7.73 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7458 | HIGH7.73 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-bin 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-bin 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6-dev 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6-dev 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-6829 | HIGH7.5 | libgcrypt20 1.10.1-3+deb12u1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libgssrpc4 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-25193 | HIGH7.5 | libharfbuzz0b 6.0.0+dfsg-3 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkadm5clnt-mit12 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkadm5srv-mit12 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkdb5-10 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5-dev 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2953 | HIGH7.5 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2015-3276 | HIGH7.5 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | HIGH7.5 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9113 | HIGH7.5 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9114 | HIGH7.5 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9113 | HIGH7.5 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9114 | HIGH7.5 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-52355 | HIGH7.5 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-16232 | HIGH7.5 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-52355 | HIGH7.5 | libtiff6 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-16232 | HIGH7.5 | libtiff6 4.5.0-6+deb12u4 No fix yet | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-52355 | HIGH7.5 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-16232 | HIGH7.5 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-32740 | HIGH7.48 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-49463 | HIGH7.48 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-97380 | HIGH7.48 | libmariadb-dev 1:10.11.18-0+deb12u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-97380 | HIGH7.48 | libmariadb-dev-compat 1:10.11.18-0+deb12u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-97380 | HIGH7.48 | libmariadb3 1:10.11.18-0+deb12u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-41142 | HIGH7.48 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-41142 | HIGH7.48 | libopenexr-dev 3.1.5-5 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-16742 | HIGH7.48 | libsystemd0 252.39-1~deb12u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-16742 | HIGH7.48 | libudev1 252.39-1~deb12u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-74860 | HIGH7.22 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-74860 | HIGH7.22 | libxml2-dev 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107818 | HIGH7.14 | libmariadb-dev 1:10.11.18-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-107818 | HIGH7.14 | libmariadb-dev-compat 1:10.11.18-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-107818 | HIGH7.14 | libmariadb3 1:10.11.18-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-88807 | HIGH7.06 | libxrender-dev 1:0.9.10-1.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-88807 | HIGH7.06 | libxrender1 1:0.9.10-1.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-77214 | MEDIUM6.97 | libexpat1 2.5.0-1+deb12u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-77214 | MEDIUM6.97 | libexpat1-dev 2.5.0-1+deb12u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-41071 | MEDIUM6.88 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-19445 | MEDIUM6.88 | libpython3.11-minimal 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-19445 | MEDIUM6.88 | libpython3.11-stdlib 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM6.8 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM6.8 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM6.8 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM6.8 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM6.8 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM6.8 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2007-3996 | MEDIUM6.8 | libwmf-0.2-7 0.2.12-5.1 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3996 | MEDIUM6.8 | libwmf-dev 0.2.12-5.1 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3996 | MEDIUM6.8 | libwmflite-0.2-7 0.2.12-5.1 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-78408 | MEDIUM6.71 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM6.71 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM6.71 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM6.71 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM6.71 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM6.71 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM6.63 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM6.63 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM6.63 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM6.63 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1365 | MEDIUM6.63 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1372 | MEDIUM6.63 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-47178 | MEDIUM6.63 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM6.63 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM6.63 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM6.63 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM6.63 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | MEDIUM6.63 | libncurses-dev 6.4-4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | MEDIUM6.63 | libncurses5-dev 6.4-4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | MEDIUM6.63 | libncurses6 6.4-4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | MEDIUM6.63 | libncursesw5-dev 6.4-4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | MEDIUM6.63 | libncursesw6 6.4-4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-12495 | MEDIUM6.63 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-12839 | MEDIUM6.63 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-12840 | MEDIUM6.63 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27622 | MEDIUM6.63 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34588 | MEDIUM6.63 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-12495 | MEDIUM6.63 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-12839 | MEDIUM6.63 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-12840 | MEDIUM6.63 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27622 | MEDIUM6.63 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34588 | MEDIUM6.63 | libopenexr-dev 3.1.5-5 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-12003 | MEDIUM6.63 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-12003 | MEDIUM6.63 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-96889 | MEDIUM6.63 | librsvg2-2 2.54.7+dfsg-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-96889 | MEDIUM6.63 | librsvg2-common 2.54.7+dfsg-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-96889 | MEDIUM6.63 | librsvg2-dev 2.54.7+dfsg-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM6.63 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM6.63 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11822 | MEDIUM6.63 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11824 | MEDIUM6.63 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11822 | MEDIUM6.63 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11824 | MEDIUM6.63 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8176 | MEDIUM6.63 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8177 | MEDIUM6.63 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8176 | MEDIUM6.63 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8177 | MEDIUM6.63 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8176 | MEDIUM6.63 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8177 | MEDIUM6.63 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | MEDIUM6.63 | libtinfo6 6.4-4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM6.63 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM6.63 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86138 | MEDIUM6.63 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86140 | MEDIUM6.63 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86142 | MEDIUM6.63 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86144 | MEDIUM6.63 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11979 | MEDIUM6.63 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86138 | MEDIUM6.63 | libxml2-dev 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86140 | MEDIUM6.63 | libxml2-dev 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86142 | MEDIUM6.63 | libxml2-dev 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86144 | MEDIUM6.63 | libxml2-dev 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11979 | MEDIUM6.63 | libxml2-dev 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | libasan8 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | libatomic1 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | libcc1-0 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | libgcc-12-dev 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | libgomp1 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | libitm1 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | liblsan0 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86047 | MEDIUM6.54 | libmariadb-dev 1:10.11.18-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86047 | MEDIUM6.54 | libmariadb-dev-compat 1:10.11.18-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86047 | MEDIUM6.54 | libmariadb3 1:10.11.18-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | libquadmath0 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | libstdc++-12-dev 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | libtsan2 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | libubsan1 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libbinutils 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | MEDIUM6.5 | libcairo-gobject2 1.16.0-7 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6461 | MEDIUM6.5 | libcairo-gobject2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6462 | MEDIUM6.5 | libcairo-gobject2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | MEDIUM6.5 | libcairo-script-interpreter2 1.16.0-7 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6461 | MEDIUM6.5 | libcairo-script-interpreter2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6462 | MEDIUM6.5 | libcairo-script-interpreter2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | MEDIUM6.5 | libcairo2 1.16.0-7 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6461 | MEDIUM6.5 | libcairo2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6462 | MEDIUM6.5 | libcairo2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | MEDIUM6.5 | libcairo2-dev 1.16.0-7 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6461 | MEDIUM6.5 | libcairo2-dev 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6462 | MEDIUM6.5 | libcairo2-dev 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libctf-nobfd0 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libctf0 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libgprofng0 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2017-9937 | MEDIUM6.5 | libjbig-dev 2.1-6.1 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2017-9937 | MEDIUM6.5 | libjbig0 2.1-6.1 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-50495 | MEDIUM6.5 | libncurses-dev 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-50495 | MEDIUM6.5 | libncurses5-dev 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-50495 | MEDIUM6.5 | libncurses6 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-50495 | MEDIUM6.5 | libncursesw5-dev 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-50495 | MEDIUM6.5 | libncursesw6 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-10505 | MEDIUM6.5 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9115 | MEDIUM6.5 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9116 | MEDIUM6.5 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9117 | MEDIUM6.5 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6988 | MEDIUM6.5 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2016-10505 | MEDIUM6.5 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9115 | MEDIUM6.5 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9116 | MEDIUM6.5 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9117 | MEDIUM6.5 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6988 | MEDIUM6.5 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6277 | MEDIUM6.5 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-10126 | MEDIUM6.5 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1210 | MEDIUM6.5 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6277 | MEDIUM6.5 | libtiff6 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-10126 | MEDIUM6.5 | libtiff6 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1210 | MEDIUM6.5 | libtiff6 4.5.0-6+deb12u4 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6277 | MEDIUM6.5 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-10126 | MEDIUM6.5 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1210 | MEDIUM6.5 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-50495 | MEDIUM6.5 | libtinfo6 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-39616 | MEDIUM6.38 | libaom3 3.6.0-1+deb12u3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1352 | MEDIUM6.38 | libelf1 0.188-2.1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86420 | MEDIUM6.38 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86421 | MEDIUM6.38 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-93589 | MEDIUM6.38 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93590 | MEDIUM6.38 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86420 | MEDIUM6.38 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86421 | MEDIUM6.38 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-93589 | MEDIUM6.38 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93590 | MEDIUM6.38 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86420 | MEDIUM6.38 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86421 | MEDIUM6.38 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-93589 | MEDIUM6.38 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93590 | MEDIUM6.38 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86420 | MEDIUM6.38 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86421 | MEDIUM6.38 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-93589 | MEDIUM6.38 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93590 | MEDIUM6.38 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86420 | MEDIUM6.38 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86421 | MEDIUM6.38 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-93589 | MEDIUM6.38 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93590 | MEDIUM6.38 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86420 | MEDIUM6.38 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86421 | MEDIUM6.38 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-93589 | MEDIUM6.38 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93590 | MEDIUM6.38 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86420 | MEDIUM6.38 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86421 | MEDIUM6.38 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-93589 | MEDIUM6.38 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93590 | MEDIUM6.38 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86420 | MEDIUM6.38 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86421 | MEDIUM6.38 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-93589 | MEDIUM6.38 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93590 | MEDIUM6.38 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86420 | MEDIUM6.38 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86421 | MEDIUM6.38 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-93589 | MEDIUM6.38 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93590 | MEDIUM6.38 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86420 | MEDIUM6.38 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86421 | MEDIUM6.38 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-93589 | MEDIUM6.38 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93590 | MEDIUM6.38 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107815 | MEDIUM6.38 | libmariadb-dev 1:10.11.18-0+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-107815 | MEDIUM6.38 | libmariadb-dev-compat 1:10.11.18-0+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-107815 | MEDIUM6.38 | libmariadb3 1:10.11.18-0+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-64181 | MEDIUM6.38 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34543 | MEDIUM6.38 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-64181 | MEDIUM6.38 | libopenexr-dev 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34543 | MEDIUM6.38 | libopenexr-dev 3.1.5-5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM6.38 | libperl5.36 5.36.0-7+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69534 | MEDIUM6.38 | libpython3.11-minimal 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM6.38 | libpython3.11-minimal 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-69534 | MEDIUM6.38 | libpython3.11-stdlib 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM6.38 | libpython3.11-stdlib 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-88806 | MEDIUM6.38 | libx11-6 2:1.8.4-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88806 | MEDIUM6.38 | libx11-data 2:1.8.4-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88806 | MEDIUM6.38 | libx11-dev 2:1.8.4-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19553 | MEDIUM6.29 | libpython3.11-minimal 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-19553 | MEDIUM6.29 | libpython3.11-stdlib 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-84782 | MEDIUM6.29 | libssl-dev 3.0.22-1~deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-84782 | MEDIUM6.29 | libssl3 3.0.22-1~deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34544 | MEDIUM6.21 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34545 | MEDIUM6.21 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-34544 | MEDIUM6.21 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34545 | MEDIUM6.21 | libopenexr-dev 3.1.5-5 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-11940 | MEDIUM6.21 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-11940 | MEDIUM6.21 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-12912 | MEDIUM6.21 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52490 | MEDIUM6.21 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61144 | MEDIUM6.21 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52491 | MEDIUM6.21 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52492 | MEDIUM6.21 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-12912 | MEDIUM6.21 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52490 | MEDIUM6.21 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61144 | MEDIUM6.21 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52491 | MEDIUM6.21 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52492 | MEDIUM6.21 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-12912 | MEDIUM6.21 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52490 | MEDIUM6.21 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61144 | MEDIUM6.21 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52491 | MEDIUM6.21 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52492 | MEDIUM6.21 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86143 | MEDIUM6.21 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86143 | MEDIUM6.21 | libxml2-dev 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107823 | MEDIUM6.12 | libmariadb-dev 1:10.11.18-0+deb12u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-107823 | MEDIUM6.12 | libmariadb-dev-compat 1:10.11.18-0+deb12u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-107823 | MEDIUM6.12 | libmariadb3 1:10.11.18-0+deb12u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-54369 | MEDIUM6.03 | libacl1 2.3.1-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-16118 | MEDIUM6.03 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-16118 | MEDIUM6.03 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-16118 | MEDIUM6.03 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-16118 | MEDIUM6.03 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-16118 | MEDIUM6.03 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68431 | MEDIUM6.03 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32741 | MEDIUM6.03 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32882 | MEDIUM6.03 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-34379 | MEDIUM6.03 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40244 | MEDIUM6.03 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40250 | MEDIUM6.03 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59184 | MEDIUM6.03 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59186 | MEDIUM6.03 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59187 | MEDIUM6.03 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59189 | MEDIUM6.03 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59981 | MEDIUM6.03 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59982 | MEDIUM6.03 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-68515 | MEDIUM6.03 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34379 | MEDIUM6.03 | libopenexr-dev 3.1.5-5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40244 | MEDIUM6.03 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40250 | MEDIUM6.03 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59184 | MEDIUM6.03 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59186 | MEDIUM6.03 | libopenexr-dev 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59187 | MEDIUM6.03 | libopenexr-dev 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59189 | MEDIUM6.03 | libopenexr-dev 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59981 | MEDIUM6.03 | libopenexr-dev 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59982 | MEDIUM6.03 | libopenexr-dev 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-68515 | MEDIUM6.03 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libasan8 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libatomic1 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM5.95 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM5.95 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM5.95 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM5.95 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM5.95 | libc-bin 2.36-9+deb12u14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM5.95 | libc-bin 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM5.95 | libc-dev-bin 2.36-9+deb12u14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM5.95 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM5.95 | libc6 2.36-9+deb12u14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM5.95 | libc6 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM5.95 | libc6-dev 2.36-9+deb12u14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM5.95 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libcc1-0 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libgcc-12-dev 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libgomp1 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libitm1 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | liblsan0 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109964 | MEDIUM5.95 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109964 | MEDIUM5.95 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109964 | MEDIUM5.95 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109964 | MEDIUM5.95 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109964 | MEDIUM5.95 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109964 | MEDIUM5.95 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109964 | MEDIUM5.95 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109964 | MEDIUM5.95 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109964 | MEDIUM5.95 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109964 | MEDIUM5.95 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM5.95 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM5.95 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM5.95 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM5.95 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libquadmath0 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM5.95 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM5.95 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libstdc++-12-dev 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libtsan2 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libubsan1 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM5.95 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM5.95 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libbinutils 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libctf-nobfd0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libctf0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt20 1.10.1-3+deb12u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libgprofng0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libgssrpc4 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkadm5clnt-mit12 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkadm5srv-mit12 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkdb5-10 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5-dev 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1-6 4.19.0-2+deb12u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56132 | MEDIUM5.87 | libexpat1 2.5.0-1+deb12u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56132 | MEDIUM5.87 | libexpat1-dev 2.5.0-1+deb12u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-90803 | MEDIUM5.78 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM5.78 | libc-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM5.78 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM5.78 | libc6 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM5.78 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-90803 | MEDIUM5.78 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90803 | MEDIUM5.78 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90803 | MEDIUM5.78 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107821 | MEDIUM5.7 | libmariadb-dev 1:10.11.18-0+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-107821 | MEDIUM5.7 | libmariadb-dev-compat 1:10.11.18-0+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-107821 | MEDIUM5.7 | libmariadb3 1:10.11.18-0+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-90801 | MEDIUM5.61 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90828 | MEDIUM5.61 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90829 | MEDIUM5.61 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90831 | MEDIUM5.61 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-90801 | MEDIUM5.61 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90828 | MEDIUM5.61 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90829 | MEDIUM5.61 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90831 | MEDIUM5.61 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-90801 | MEDIUM5.61 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90828 | MEDIUM5.61 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90829 | MEDIUM5.61 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90831 | MEDIUM5.61 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-90801 | MEDIUM5.61 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90828 | MEDIUM5.61 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90829 | MEDIUM5.61 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90831 | MEDIUM5.61 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libbinutils 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libctf-nobfd0 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libctf0 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libgprofng0 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM5.52 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM5.52 | libgssrpc4 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32738 | MEDIUM5.52 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32739 | MEDIUM5.52 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32814 | MEDIUM5.52 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-49271 | MEDIUM5.52 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM5.52 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM5.52 | libkadm5clnt-mit12 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM5.52 | libkadm5srv-mit12 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM5.52 | libkdb5-10 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM5.52 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM5.52 | libkrb5-dev 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM5.52 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53532 | MEDIUM5.52 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54920 | MEDIUM5.52 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-68516 | MEDIUM5.52 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53532 | MEDIUM5.52 | libopenexr-dev 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54920 | MEDIUM5.52 | libopenexr-dev 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-68516 | MEDIUM5.52 | libopenexr-dev 3.1.5-5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-39329 | MEDIUM5.52 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-39329 | MEDIUM5.52 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-37769 | MEDIUM5.52 | libpixman-1-0 0.42.2-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-37769 | MEDIUM5.52 | libpixman-1-dev 0.42.2-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-15310 | MEDIUM5.52 | libpython3.11-minimal 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-17084 | MEDIUM5.52 | libpython3.11-minimal 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-15310 | MEDIUM5.52 | libpython3.11-stdlib 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-17084 | MEDIUM5.52 | libpython3.11-stdlib 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-85231 | MEDIUM5.52 | libtirpc-common 1.3.3+ds-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85231 | MEDIUM5.52 | libtirpc-dev 1.3.3+ds-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85231 | MEDIUM5.52 | libtirpc3 1.3.3+ds-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-94283 | MEDIUM5.52 | libx11-6 2:1.8.4-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94283 | MEDIUM5.52 | libx11-data 2:1.8.4-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94283 | MEDIUM5.52 | libx11-dev 2:1.8.4-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libbinutils 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libbinutils 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libbinutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | MEDIUM5.5 | libcairo-gobject2 1.16.0-7 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | MEDIUM5.5 | libcairo-script-interpreter2 1.16.0-7 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | MEDIUM5.5 | libcairo2 1.16.0-7 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | MEDIUM5.5 | libcairo2-dev 1.16.0-7 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf-nobfd0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libctf-nobfd0 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libctf-nobfd0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libctf0 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libctf0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libgprofng0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libgprofng0 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libgprofng0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107822 | MEDIUM5.44 | libmariadb-dev 1:10.11.18-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107822 | MEDIUM5.44 | libmariadb-dev-compat 1:10.11.18-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107822 | MEDIUM5.44 | libmariadb3 1:10.11.18-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54370 | MEDIUM5.35 | libacl1 2.3.1-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | MEDIUM5.35 | libattr1 1:2.5.1-4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-12345 | MEDIUM5.35 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-12345 | MEDIUM5.35 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-bin 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-bin 2.36-9+deb12u14 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6 2.36-9+deb12u14 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6-dev 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6-dev 2.36-9+deb12u14 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2015-9019 | MEDIUM5.3 | libxslt1-dev 1.1.35-1+deb12u4 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2015-9019 | MEDIUM5.3 | libxslt1.1 1.1.35-1+deb12u4 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-55373 | MEDIUM5.27 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55373 | MEDIUM5.27 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | libp11-kit0 0.24.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18938 | MEDIUM5.27 | libp11-kit0 0.24.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-28162 | MEDIUM5.27 | libpng-dev 1.6.39-2+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-28162 | MEDIUM5.27 | libpng16-16 1.6.39-2+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90804 | MEDIUM5.18 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90804 | MEDIUM5.18 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90804 | MEDIUM5.18 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18090 | MEDIUM5.18 | libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18090 | MEDIUM5.18 | libgdk-pixbuf-2.0-dev 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18090 | MEDIUM5.18 | libgdk-pixbuf2.0-bin 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18090 | MEDIUM5.18 | libgdk-pixbuf2.0-common 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90804 | MEDIUM5.18 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | libpython3.11-minimal 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | libpython3.11-stdlib 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18495 | MEDIUM5.18 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-1916 | MEDIUM5.18 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-18495 | MEDIUM5.18 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-1916 | MEDIUM5.18 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-18495 | MEDIUM5.18 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-1916 | MEDIUM5.18 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | libc-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.02 | libc-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.02 | libc-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.02 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.02 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | libc6 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.02 | libc6 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.02 | libc6 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.02 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.02 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-32570 | MEDIUM5.02 | libdav1d6 1.0.0-2+deb12u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-102633 | MEDIUM5.02 | libexpat1 2.5.0-1+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102633 | MEDIUM5.02 | libexpat1-dev 2.5.0-1+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssrpc4 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkadm5clnt-mit12 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkadm5srv-mit12 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkdb5-10 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-dev 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-106565 | MEDIUM5.02 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106567 | MEDIUM5.02 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106565 | MEDIUM5.02 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106567 | MEDIUM5.02 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106565 | MEDIUM5.02 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106567 | MEDIUM5.02 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106565 | MEDIUM5.02 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106567 | MEDIUM5.02 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106565 | MEDIUM5.02 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106567 | MEDIUM5.02 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106565 | MEDIUM5.02 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106567 | MEDIUM5.02 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106565 | MEDIUM5.02 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106567 | MEDIUM5.02 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106565 | MEDIUM5.02 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106567 | MEDIUM5.02 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106565 | MEDIUM5.02 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106567 | MEDIUM5.02 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106565 | MEDIUM5.02 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106567 | MEDIUM5.02 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | libpython3.11-minimal 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | libpython3.11-stdlib 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54872 | MEDIUM5.02 | libssl-dev 3.0.22-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75805 | MEDIUM5.02 | libssl-dev 3.0.22-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77696 | MEDIUM5.02 | libssl-dev 3.0.22-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54872 | MEDIUM5.02 | libssl3 3.0.22-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75805 | MEDIUM5.02 | libssl3 3.0.22-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77696 | MEDIUM5.02 | libssl3 3.0.22-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3477 | MEDIUM5 | libwmf-0.2-7 0.2.12-5.1 No fix yet | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3477 | MEDIUM5 | libwmf-dev 0.2.12-5.1 No fix yet | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3477 | MEDIUM5 | libwmflite-0.2-7 0.2.12-5.1 No fix yet | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-15534 | MEDIUM4.84 | libperl5.36 5.36.0-7+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libbinutils 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | MEDIUM4.76 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf-nobfd0 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | MEDIUM4.76 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf0 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | MEDIUM4.76 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libgprofng0 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | MEDIUM4.76 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libasan8 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libatomic1 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19548 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-90830 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91779 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91782 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | libc-bin 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | libc6 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libcc1-0 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19548 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-90830 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91779 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91782 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19548 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-90830 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91779 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91782 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1371 | MEDIUM4.67 | libelf1 0.188-2.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1377 | MEDIUM4.67 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1 2.5.0-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52426 | MEDIUM4.67 | libexpat1 2.5.0-1+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1-dev 2.5.0-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52426 | MEDIUM4.67 | libexpat1-dev 2.5.0-1+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95512 | MEDIUM4.67 | libfreetype-dev 2.12.1+dfsg-5+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95512 | MEDIUM4.67 | libfreetype6 2.12.1+dfsg-5+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95512 | MEDIUM4.67 | libfreetype6-dev 2.12.1+dfsg-5+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc-12-dev 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgomp1 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19548 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-90830 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91779 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91782 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-47709 | MEDIUM4.67 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libitm1 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | liblsan0 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-86423 | MEDIUM4.67 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86425 | MEDIUM4.67 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86423 | MEDIUM4.67 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86425 | MEDIUM4.67 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86423 | MEDIUM4.67 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86425 | MEDIUM4.67 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86423 | MEDIUM4.67 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86425 | MEDIUM4.67 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86423 | MEDIUM4.67 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86425 | MEDIUM4.67 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86423 | MEDIUM4.67 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86425 | MEDIUM4.67 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86423 | MEDIUM4.67 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86425 | MEDIUM4.67 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86423 | MEDIUM4.67 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86425 | MEDIUM4.67 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86423 | MEDIUM4.67 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86425 | MEDIUM4.67 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86423 | MEDIUM4.67 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86425 | MEDIUM4.67 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-48074 | MEDIUM4.67 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-55059 | MEDIUM4.67 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55371 | MEDIUM4.67 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59183 | MEDIUM4.67 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59983 | MEDIUM4.67 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59984 | MEDIUM4.67 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59985 | MEDIUM4.67 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-61555 | MEDIUM4.67 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88384 | MEDIUM4.67 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-48074 | MEDIUM4.67 | libopenexr-dev 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-55059 | MEDIUM4.67 | libopenexr-dev 3.1.5-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55371 | MEDIUM4.67 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59183 | MEDIUM4.67 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59983 | MEDIUM4.67 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59984 | MEDIUM4.67 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59985 | MEDIUM4.67 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-61555 | MEDIUM4.67 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88384 | MEDIUM4.67 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-39328 | MEDIUM4.67 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-39328 | MEDIUM4.67 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | MEDIUM4.67 | libpng-dev 1.6.39-2+deb12u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | MEDIUM4.67 | libpng16-16 1.6.39-2+deb12u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libquadmath0 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-50812 | MEDIUM4.67 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50813 | MEDIUM4.67 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-29088 | MEDIUM4.67 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50812 | MEDIUM4.67 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50813 | MEDIUM4.67 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-29088 | MEDIUM4.67 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libstdc++-12-dev 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM4.67 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-3164 | MEDIUM4.67 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6228 | MEDIUM4.67 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61143 | MEDIUM4.67 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-3164 | MEDIUM4.67 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6228 | MEDIUM4.67 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61143 | MEDIUM4.67 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-3164 | MEDIUM4.67 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6228 | MEDIUM4.67 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61143 | MEDIUM4.67 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libtsan2 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libubsan1 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM4.67 | libudev1 252.39-1~deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-94284 | MEDIUM4.67 | libx11-6 2:1.8.4-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94284 | MEDIUM4.67 | libx11-data 2:1.8.4-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94284 | MEDIUM4.67 | libx11-dev 2:1.8.4-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76781 | MEDIUM4.67 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76781 | MEDIUM4.67 | libxml2-dev 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-10911 | MEDIUM4.67 | libxslt1-dev 1.1.35-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-10911 | MEDIUM4.67 | libxslt1.1 1.1.35-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107816 | MEDIUM4.59 | libmariadb-dev 1:10.11.18-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85985 | MEDIUM4.59 | libmariadb-dev 1:10.11.18-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107816 | MEDIUM4.59 | libmariadb-dev-compat 1:10.11.18-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85985 | MEDIUM4.59 | libmariadb-dev-compat 1:10.11.18-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107816 | MEDIUM4.59 | libmariadb3 1:10.11.18-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85985 | MEDIUM4.59 | libmariadb3 1:10.11.18-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58055 | MEDIUM4.59 | libnghttp2-14 1.52.0-1+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-24975 | MEDIUM4.5 | git 1:2.39.5-0+deb12u3 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2008-1688 | MEDIUM4.5 | m4 1.4.19-3 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6951 | MEDIUM4.5 | patch 2.7.6-7 No fix yet | 8.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6952 | MEDIUM4.5 | patch 2.7.6-7 No fix yet | 8.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1147 | MEDIUM4.5 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM4.5 | libc-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM4.5 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM4.5 | libc6 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM4.5 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-16768 | MEDIUM4.5 | libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-16768 | MEDIUM4.5 | libgdk-pixbuf-2.0-dev 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-16768 | MEDIUM4.5 | libgdk-pixbuf2.0-bin 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-16768 | MEDIUM4.5 | libgdk-pixbuf2.0-common 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15588 | MEDIUM4.5 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86469 | MEDIUM4.5 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15588 | MEDIUM4.5 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86469 | MEDIUM4.5 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15588 | MEDIUM4.5 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86469 | MEDIUM4.5 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15588 | MEDIUM4.5 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86469 | MEDIUM4.5 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15588 | MEDIUM4.5 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86469 | MEDIUM4.5 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-22693 | MEDIUM4.5 | libharfbuzz0b 6.0.0+dfsg-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-102635 | MEDIUM4.5 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-106564 | MEDIUM4.5 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106568 | MEDIUM4.5 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106577 | MEDIUM4.5 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109259 | MEDIUM4.5 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109262 | MEDIUM4.5 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109265 | MEDIUM4.5 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109269 | MEDIUM4.5 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109276 | MEDIUM4.5 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64685 | MEDIUM4.5 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102635 | MEDIUM4.5 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-106564 | MEDIUM4.5 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106568 | MEDIUM4.5 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106577 | MEDIUM4.5 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109259 | MEDIUM4.5 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109262 | MEDIUM4.5 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109265 | MEDIUM4.5 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109269 | MEDIUM4.5 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109276 | MEDIUM4.5 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64685 | MEDIUM4.5 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102635 | MEDIUM4.5 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-106564 | MEDIUM4.5 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106568 | MEDIUM4.5 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106577 | MEDIUM4.5 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109259 | MEDIUM4.5 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109262 | MEDIUM4.5 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109265 | MEDIUM4.5 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109269 | MEDIUM4.5 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109276 | MEDIUM4.5 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64685 | MEDIUM4.5 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102635 | MEDIUM4.5 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-106564 | MEDIUM4.5 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106568 | MEDIUM4.5 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106577 | MEDIUM4.5 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109259 | MEDIUM4.5 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109262 | MEDIUM4.5 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109265 | MEDIUM4.5 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109269 | MEDIUM4.5 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109276 | MEDIUM4.5 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64685 | MEDIUM4.5 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102635 | MEDIUM4.5 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-106564 | MEDIUM4.5 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106568 | MEDIUM4.5 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106577 | MEDIUM4.5 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109259 | MEDIUM4.5 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109262 | MEDIUM4.5 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109265 | MEDIUM4.5 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109269 | MEDIUM4.5 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109276 | MEDIUM4.5 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64685 | MEDIUM4.5 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102635 | MEDIUM4.5 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-106564 | MEDIUM4.5 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106568 | MEDIUM4.5 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106577 | MEDIUM4.5 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109259 | MEDIUM4.5 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109262 | MEDIUM4.5 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109265 | MEDIUM4.5 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109269 | MEDIUM4.5 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109276 | MEDIUM4.5 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64685 | MEDIUM4.5 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102635 | MEDIUM4.5 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-106564 | MEDIUM4.5 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106568 | MEDIUM4.5 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106577 | MEDIUM4.5 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109259 | MEDIUM4.5 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109262 | MEDIUM4.5 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109265 | MEDIUM4.5 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109269 | MEDIUM4.5 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109276 | MEDIUM4.5 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64685 | MEDIUM4.5 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102635 | MEDIUM4.5 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-106564 | MEDIUM4.5 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106568 | MEDIUM4.5 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106577 | MEDIUM4.5 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109259 | MEDIUM4.5 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109262 | MEDIUM4.5 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109265 | MEDIUM4.5 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109269 | MEDIUM4.5 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109276 | MEDIUM4.5 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64685 | MEDIUM4.5 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102635 | MEDIUM4.5 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-106564 | MEDIUM4.5 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106568 | MEDIUM4.5 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106577 | MEDIUM4.5 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109259 | MEDIUM4.5 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109262 | MEDIUM4.5 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109265 | MEDIUM4.5 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109269 | MEDIUM4.5 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109276 | MEDIUM4.5 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64685 | MEDIUM4.5 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102635 | MEDIUM4.5 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-106564 | MEDIUM4.5 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106568 | MEDIUM4.5 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106577 | MEDIUM4.5 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109259 | MEDIUM4.5 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109262 | MEDIUM4.5 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109265 | MEDIUM4.5 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109269 | MEDIUM4.5 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109276 | MEDIUM4.5 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64685 | MEDIUM4.5 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34380 | MEDIUM4.5 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34380 | MEDIUM4.5 | libopenexr-dev 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3713 | MEDIUM4.5 | libpng-dev 1.6.39-2+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3713 | MEDIUM4.5 | libpng16-16 1.6.39-2+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-8328 | MEDIUM4.5 | libpython3.11-minimal 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-15806 | MEDIUM4.5 | libpython3.11-minimal 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | libpython3.11-minimal 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3446 | MEDIUM4.5 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-8328 | MEDIUM4.5 | libpython3.11-stdlib 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-15806 | MEDIUM4.5 | libpython3.11-stdlib 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | libpython3.11-stdlib 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3446 | MEDIUM4.5 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM4.5 | libssl-dev 3.0.22-1~deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM4.5 | libssl3 3.0.22-1~deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8851 | MEDIUM4.5 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8851 | MEDIUM4.5 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8851 | MEDIUM4.5 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-85977 | MEDIUM4.5 | libtirpc-common 1.3.3+ds-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85977 | MEDIUM4.5 | libtirpc-dev 1.3.3+ds-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85977 | MEDIUM4.5 | libtirpc3 1.3.3+ds-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libudev1 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libudev1 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libudev1 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-52005 | MEDIUM4.49 | git 1:2.39.5-0+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-94285 | MEDIUM4.33 | libx11-6 2:1.8.4-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94285 | MEDIUM4.33 | libx11-data 2:1.8.4-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94285 | MEDIUM4.33 | libx11-dev 2:1.8.4-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-45346 | MEDIUM4.3 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-45346 | MEDIUM4.3 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3476 | MEDIUM4.3 | libwmf-0.2-7 0.2.12-5.1 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3476 | MEDIUM4.3 | libwmf-dev 0.2.12-5.1 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3476 | MEDIUM4.3 | libwmflite-0.2-7 0.2.12-5.1 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-90802 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91780 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM4.25 | libbz2-1.0 1.0.8-5+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM4.25 | libbz2-dev 1.0.8-5+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.36-9+deb12u14 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.36-9+deb12u14 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-90802 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91780 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-90802 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91780 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-90802 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91780 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libgssrpc4 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkadm5clnt-mit12 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkadm5srv-mit12 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkdb5-10 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5-dev 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-62363 | MEDIUM4.25 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-62363 | MEDIUM4.25 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-62363 | MEDIUM4.25 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-62363 | MEDIUM4.25 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-62363 | MEDIUM4.25 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-62363 | MEDIUM4.25 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-62363 | MEDIUM4.25 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-62363 | MEDIUM4.25 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-62363 | MEDIUM4.25 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-62363 | MEDIUM4.25 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34589 | MEDIUM4.25 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34589 | MEDIUM4.25 | libopenexr-dev 3.1.5-5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-28164 | MEDIUM4.25 | libpng-dev 1.6.39-2+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-28164 | MEDIUM4.25 | libpng16-16 1.6.39-2+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-61145 | MEDIUM4.25 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61145 | MEDIUM4.25 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61145 | MEDIUM4.25 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2020-15719 | MEDIUM4.2 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc-bin 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc6 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.17 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.17 | libgssrpc4 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.17 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.17 | libkadm5clnt-mit12 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.17 | libkadm5srv-mit12 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.17 | libkdb5-10 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.17 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.17 | libkrb5-dev 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.17 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-8286 | MEDIUM4.13 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | MEDIUM4.13 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | MEDIUM4.13 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | MEDIUM4.13 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | MEDIUM4.13 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-19445 | MEDIUM4.13 | python3.11 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19445 | MEDIUM4.13 | python3.11-minimal 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | MEDIUM4.08 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | MEDIUM4.08 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | MEDIUM4.08 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | MEDIUM4.08 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-86410 | MEDIUM4.08 | curl 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-86410 | MEDIUM4.08 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-86410 | MEDIUM4.08 | libcurl4 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-86410 | MEDIUM4.08 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-109275 | MEDIUM4.08 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109275 | MEDIUM4.08 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109275 | MEDIUM4.08 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109275 | MEDIUM4.08 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109275 | MEDIUM4.08 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109275 | MEDIUM4.08 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109275 | MEDIUM4.08 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109275 | MEDIUM4.08 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109275 | MEDIUM4.08 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109275 | MEDIUM4.08 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam-modules 1.5.2-6+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam-modules-bin 1.5.2-6+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam-runtime 1.5.2-6+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam0g 1.5.2-6+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.03 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | MEDIUM4.03 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | MEDIUM4.03 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | MEDIUM4.03 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | MEDIUM4 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | MEDIUM4 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-81893 | MEDIUM4 | libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-81893 | MEDIUM4 | libgdk-pixbuf-2.0-dev 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-81893 | MEDIUM4 | libgdk-pixbuf2.0-bin 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-81893 | MEDIUM4 | libgdk-pixbuf2.0-common 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | MEDIUM4 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-62343 | MEDIUM4 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-62946 | MEDIUM4 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-62343 | MEDIUM4 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-62946 | MEDIUM4 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-62343 | MEDIUM4 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-62946 | MEDIUM4 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-62343 | MEDIUM4 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-62946 | MEDIUM4 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-62343 | MEDIUM4 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-62946 | MEDIUM4 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-62343 | MEDIUM4 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-62946 | MEDIUM4 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-62343 | MEDIUM4 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-62946 | MEDIUM4 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-62343 | MEDIUM4 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-62946 | MEDIUM4 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-62343 | MEDIUM4 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-62946 | MEDIUM4 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-62343 | MEDIUM4 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-62946 | MEDIUM4 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-10041 | MEDIUM4 | libpam-modules 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-10041 | MEDIUM4 | libpam-modules-bin 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-10041 | MEDIUM4 | libpam-runtime 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-10041 | MEDIUM4 | libpam0g 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-bin 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6-dev 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-11082 | LOW3.98 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18220 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18220 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW3.98 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW3.98 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW3.98 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW3.98 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-106583 | LOW3.98 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-12003 | LOW3.98 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-12003 | LOW3.98 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW3.98 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW3.98 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW3.98 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW3.98 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW3.93 | cpp-12 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW3.93 | g++-12 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW3.93 | gcc-12 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2018-20712 | LOW3.9 | binutils 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20712 | LOW3.9 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-92388 | LOW3.9 | curl 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-86414 | LOW3.9 | curl 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-92390 | LOW3.9 | curl 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2017-11754 | LOW3.9 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2017-11755 | LOW3.9 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2018-15607 | LOW3.9 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2017-11754 | LOW3.9 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2017-11755 | LOW3.9 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2018-15607 | LOW3.9 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-92388 | LOW3.9 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-86414 | LOW3.9 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-92390 | LOW3.9 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-92388 | LOW3.9 | libcurl4 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-86414 | LOW3.9 | libcurl4 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-92390 | LOW3.9 | libcurl4 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-92388 | LOW3.9 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-86414 | LOW3.9 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-92390 | LOW3.9 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2008-3234 | LOW3.9 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2024-10524 | LOW3.9 | wget 1.21.3-1+deb12u1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2009-3546 | LOW3.85 | libwmf-0.2-7 0.2.12-5.1 No fix yet | 10.2% High Exploitation Risk | Post-Exploit |
| CVE-2009-3546 | LOW3.85 | libwmf-dev 0.2.12-5.1 No fix yet | 10.2% High Exploitation Risk | Post-Exploit |
| CVE-2009-3546 | LOW3.85 | libwmflite-0.2-7 0.2.12-5.1 No fix yet | 10.2% High Exploitation Risk | Post-Exploit |
| CVE-2025-0840 | LOW3.82 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW3.82 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-0840 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW3.82 | gzip 1.12-1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-86420 | LOW3.82 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-86421 | LOW3.82 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-93589 | LOW3.82 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-93590 | LOW3.82 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-86420 | LOW3.82 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-86421 | LOW3.82 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-93589 | LOW3.82 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-93590 | LOW3.82 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-106553 | LOW3.82 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-106555 | LOW3.82 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-59999 | LOW3.82 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-60000 | LOW3.82 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl 5.36.0-7+deb12u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-base 5.36.0-7+deb12u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-modules-5.36 5.36.0-7+deb12u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69534 | LOW3.82 | python3.11 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-15308 | LOW3.82 | python3.11 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW3.82 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-69534 | LOW3.82 | python3.11-minimal 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-15308 | LOW3.82 | python3.11-minimal 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW3.82 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW3.82 | libpython3.11-minimal 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | libpython3.11-stdlib 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | LOW3.77 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-84782 | LOW3.77 | openssl 3.0.22-1~deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19553 | LOW3.77 | python3.11 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-19553 | LOW3.77 | python3.11-minimal 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-109281 | LOW3.74 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109281 | LOW3.74 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109281 | LOW3.74 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109281 | LOW3.74 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109281 | LOW3.74 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109281 | LOW3.74 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109281 | LOW3.74 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109281 | LOW3.74 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109281 | LOW3.74 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109281 | LOW3.74 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-107817 | LOW3.74 | libmariadb-dev 1:10.11.18-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-107817 | LOW3.74 | libmariadb-dev-compat 1:10.11.18-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-107817 | LOW3.74 | libmariadb3 1:10.11.18-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-11940 | LOW3.72 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-11940 | LOW3.72 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW3.7 | libapt-pkg6.0 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-31879 | LOW3.66 | wget 1.21.3-1+deb12u1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-93588 | LOW3.65 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93588 | LOW3.65 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93588 | LOW3.65 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93588 | LOW3.65 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93588 | LOW3.65 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93588 | LOW3.65 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93588 | LOW3.65 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93588 | LOW3.65 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93588 | LOW3.65 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93588 | LOW3.65 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-44169 | LOW3.65 | libmariadb-dev 1:10.11.18-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85745 | LOW3.65 | libmariadb-dev 1:10.11.18-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-44169 | LOW3.65 | libmariadb-dev-compat 1:10.11.18-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85745 | LOW3.65 | libmariadb-dev-compat 1:10.11.18-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-44169 | LOW3.65 | libmariadb3 1:10.11.18-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85745 | LOW3.65 | libmariadb3 1:10.11.18-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-39327 | LOW3.65 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-39327 | LOW3.65 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | LOW3.62 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW3.62 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW3.62 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW3.62 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW3.62 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58471 | LOW3.62 | wget 1.21.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58472 | LOW3.62 | wget 1.21.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2005-2541 | LOW3.6 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-53613 | LOW3.57 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW3.57 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW3.57 | cpp-12 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW3.57 | g++-12 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW3.57 | gcc-12 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-109964 | LOW3.57 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-109964 | LOW3.57 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW3.57 | mount 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW3.57 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW3.57 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW3.57 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW3.57 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW3.57 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-19542 | LOW3.57 | libc-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | libc-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | LOW3.57 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | LOW3.57 | libc6 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | libc6 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | LOW3.57 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-105083 | LOW3.57 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105083 | LOW3.57 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105083 | LOW3.57 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105083 | LOW3.57 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105083 | LOW3.57 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105083 | LOW3.57 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105083 | LOW3.57 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105083 | LOW3.57 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105083 | LOW3.57 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105083 | LOW3.57 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | LOW3.54 | binutils 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2020-14145 | LOW3.54 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-6879 | LOW3.53 | libaom3 3.6.0-1+deb12u3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-bin 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6-dev 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-45853 | LOW3.53 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 3.4% Low-Moderate Risk | Post-Exploit |
| CVE-2010-4651 | LOW3.48 | patch 2.7.6-7 No fix yet | 4.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-90803 | LOW3.47 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90803 | LOW3.47 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-25260 | LOW3.4 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-106566 | LOW3.4 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-106566 | LOW3.4 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-106566 | LOW3.4 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-106566 | LOW3.4 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-106566 | LOW3.4 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-106566 | LOW3.4 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-106566 | LOW3.4 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-106566 | LOW3.4 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-106566 | LOW3.4 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-106566 | LOW3.4 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | LOW3.37 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-90801 | LOW3.37 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90828 | LOW3.37 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90829 | LOW3.37 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90831 | LOW3.37 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-53589 | LOW3.37 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-90801 | LOW3.37 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90828 | LOW3.37 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90829 | LOW3.37 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90831 | LOW3.37 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils 2.40-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2016-2781 | LOW3.31 | coreutils 9.1-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | curl 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-19931 | LOW3.31 | curl 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-19931 | LOW3.31 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-19931 | LOW3.31 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-19931 | LOW3.31 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-106552 | LOW3.31 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-106585 | LOW3.31 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59998 | LOW3.31 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-60001 | LOW3.31 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW3.31 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-15310 | LOW3.31 | python3.11 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-17084 | LOW3.31 | python3.11 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW3.31 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-15310 | LOW3.31 | python3.11-minimal 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-17084 | LOW3.31 | python3.11-minimal 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-58469 | LOW3.31 | wget 1.21.3-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-16599 | LOW3.31 | wget 1.21.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2016-8678 | LOW3.3 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2017-7275 | LOW3.3 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2016-8678 | LOW3.3 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2017-7275 | LOW3.3 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5841 | LOW3.28 | libopenexr-3-1-30 3.1.5-5 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2379 | LOW3.24 | curl 7.88.1-10+deb12u15 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2379 | LOW3.24 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2379 | LOW3.24 | libcurl4 7.88.1-10+deb12u15 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2379 | LOW3.24 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-12345 | LOW3.21 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-12345 | LOW3.21 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-86409 | LOW3.18 | curl 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-86409 | LOW3.18 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-86409 | LOW3.18 | libcurl4 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-86409 | LOW3.18 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2016-20012 | LOW3.18 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 5.3% Low-Moderate Risk | Post-Exploit |
| CVE-2018-15919 | LOW3.18 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 3.6% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1152 | LOW3.15 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.15 | libc-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.15 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.15 | libc6 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.15 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-41080 | LOW3.15 | libexpat1 2.5.0-1+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41080 | LOW3.15 | libexpat1-dev 2.5.0-1+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-109260 | LOW3.15 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109261 | LOW3.15 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109263 | LOW3.15 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109264 | LOW3.15 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109268 | LOW3.15 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109271 | LOW3.15 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109260 | LOW3.15 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109261 | LOW3.15 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109263 | LOW3.15 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109264 | LOW3.15 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109268 | LOW3.15 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109271 | LOW3.15 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109260 | LOW3.15 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109261 | LOW3.15 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109263 | LOW3.15 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109264 | LOW3.15 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109268 | LOW3.15 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109271 | LOW3.15 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109260 | LOW3.15 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109261 | LOW3.15 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109263 | LOW3.15 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109264 | LOW3.15 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109268 | LOW3.15 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109271 | LOW3.15 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109260 | LOW3.15 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109261 | LOW3.15 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109263 | LOW3.15 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109264 | LOW3.15 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109268 | LOW3.15 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109271 | LOW3.15 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109260 | LOW3.15 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109261 | LOW3.15 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109263 | LOW3.15 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109264 | LOW3.15 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109268 | LOW3.15 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109271 | LOW3.15 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109260 | LOW3.15 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109261 | LOW3.15 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109263 | LOW3.15 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109264 | LOW3.15 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109268 | LOW3.15 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109271 | LOW3.15 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109260 | LOW3.15 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109261 | LOW3.15 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109263 | LOW3.15 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109264 | LOW3.15 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109268 | LOW3.15 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109271 | LOW3.15 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109260 | LOW3.15 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109261 | LOW3.15 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109263 | LOW3.15 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109264 | LOW3.15 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109268 | LOW3.15 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109271 | LOW3.15 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109260 | LOW3.15 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109261 | LOW3.15 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109263 | LOW3.15 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109264 | LOW3.15 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109268 | LOW3.15 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109271 | LOW3.15 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.15 | libssl-dev 3.0.22-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.15 | libssl3 3.0.22-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.11 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90804 | LOW3.11 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90804 | LOW3.11 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56391 | LOW3.11 | coreutils 9.1-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW3.11 | coreutils 9.1-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.11 | python3.11 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.11 | python3.11-minimal 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2020-15778 | LOW3.07 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 13.7% High Exploitation Risk | Post-Exploit |
| CVE-2026-105081 | LOW3.06 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105081 | LOW3.06 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105081 | LOW3.06 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105081 | LOW3.06 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105081 | LOW3.06 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105081 | LOW3.06 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105081 | LOW3.06 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105081 | LOW3.06 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105081 | LOW3.06 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105081 | LOW3.06 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-10966 | LOW3.01 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-106565 | LOW3.01 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-106567 | LOW3.01 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-106565 | LOW3.01 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-106567 | LOW3.01 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-54872 | LOW3.01 | openssl 3.0.22-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-75805 | LOW3.01 | openssl 3.0.22-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-77696 | LOW3.01 | openssl 3.0.22-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-9669 | LOW3.01 | python3.11 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9669 | LOW3.01 | python3.11-minimal 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-15146 | LOW3.01 | wget 1.21.3-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2018-1000021 | LOW3 | git 1:2.39.5-0+deb12u3 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2008-3134 | LOW3 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2008-3134 | LOW3 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2007-2243 | LOW3 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | LOW2.92 | perl 5.36.0-7+deb12u4 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | LOW2.92 | perl-base 5.36.0-7+deb12u4 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | LOW2.92 | perl-modules-5.36 5.36.0-7+deb12u4 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-15534 | LOW2.91 | perl 5.36.0-7+deb12u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.91 | perl-base 5.36.0-7+deb12u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.91 | perl-modules-5.36 5.36.0-7+deb12u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-107928 | LOW2.88 | curl 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-107928 | LOW2.88 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-107928 | LOW2.88 | libcurl4 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-107928 | LOW2.88 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-60002 | LOW2.87 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils 2.40-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-15003 | LOW2.86 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-15003 | LOW2.86 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-73282 | LOW2.86 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2019-6110 | LOW2.81 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 24.9% High Exploitation Risk | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW2.8 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-19548 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-90830 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91779 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91782 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-19548 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-90830 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91779 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91782 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | cpp-12 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-102473 | LOW2.8 | dash 0.5.12-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | g++-12 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | gcc-12 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-86423 | LOW2.8 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-86425 | LOW2.8 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2005-0406 | LOW2.8 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-86423 | LOW2.8 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-86425 | LOW2.8 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2005-0406 | LOW2.8 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-45261 | LOW2.8 | patch 2.7.6-7 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-56288 | LOW2.8 | patch 2.7.6-7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56289 | LOW2.8 | patch 2.7.6-7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0864 | LOW2.8 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0864 | LOW2.8 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-91781 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-50422 | LOW2.8 | libcairo-gobject2 1.16.0-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-50422 | LOW2.8 | libcairo-script-interpreter2 1.16.0-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-50422 | LOW2.8 | libcairo2 1.16.0-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-50422 | LOW2.8 | libcairo2-dev 1.16.0-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-91781 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-91781 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-91781 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3949 | LOW2.8 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-109267 | LOW2.8 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109270 | LOW2.8 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109273 | LOW2.8 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109277 | LOW2.8 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-66011 | LOW2.8 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-93586 | LOW2.8 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-93587 | LOW2.8 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109267 | LOW2.8 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109270 | LOW2.8 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109273 | LOW2.8 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109277 | LOW2.8 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-66011 | LOW2.8 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-93586 | LOW2.8 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-93587 | LOW2.8 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109267 | LOW2.8 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109270 | LOW2.8 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109273 | LOW2.8 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109277 | LOW2.8 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-66011 | LOW2.8 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-93586 | LOW2.8 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-93587 | LOW2.8 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109267 | LOW2.8 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109270 | LOW2.8 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109273 | LOW2.8 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109277 | LOW2.8 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-66011 | LOW2.8 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-93586 | LOW2.8 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-93587 | LOW2.8 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109267 | LOW2.8 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109270 | LOW2.8 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109273 | LOW2.8 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109277 | LOW2.8 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-66011 | LOW2.8 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-93586 | LOW2.8 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-93587 | LOW2.8 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109267 | LOW2.8 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109270 | LOW2.8 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109273 | LOW2.8 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109277 | LOW2.8 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-66011 | LOW2.8 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-93586 | LOW2.8 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-93587 | LOW2.8 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109267 | LOW2.8 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109270 | LOW2.8 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109273 | LOW2.8 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109277 | LOW2.8 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-66011 | LOW2.8 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-93586 | LOW2.8 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-93587 | LOW2.8 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109267 | LOW2.8 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109270 | LOW2.8 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109273 | LOW2.8 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109277 | LOW2.8 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-66011 | LOW2.8 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-93586 | LOW2.8 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-93587 | LOW2.8 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109267 | LOW2.8 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109270 | LOW2.8 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109273 | LOW2.8 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109277 | LOW2.8 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-66011 | LOW2.8 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-93586 | LOW2.8 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-93587 | LOW2.8 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109267 | LOW2.8 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109270 | LOW2.8 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109273 | LOW2.8 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-109277 | LOW2.8 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-66011 | LOW2.8 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-93586 | LOW2.8 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-93587 | LOW2.8 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW2.8 | libncurses-dev 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW2.8 | libncurses5-dev 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW2.8 | libncurses6 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW2.8 | libncursesw5-dev 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW2.8 | libncursesw6 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW2.8 | libperl5.36 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-4016 | LOW2.8 | libproc2-0 2:4.0.2-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8961 | LOW2.8 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9165 | LOW2.8 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8961 | LOW2.8 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9165 | LOW2.8 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8961 | LOW2.8 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9165 | LOW2.8 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW2.8 | libtinfo6 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 252.39-1~deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-59995 | LOW2.75 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59996 | LOW2.75 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59997 | LOW2.75 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-73283 | LOW2.75 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2008-1687 | LOW2.7 | m4 1.4.19-3 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | curl 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-53910 | LOW2.7 | diffutils 1:3.8-4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-102635 | LOW2.7 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-106564 | LOW2.7 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-106568 | LOW2.7 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-106577 | LOW2.7 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-109259 | LOW2.7 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-109262 | LOW2.7 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-109265 | LOW2.7 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-109269 | LOW2.7 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-109276 | LOW2.7 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-64685 | LOW2.7 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-55160 | LOW2.7 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-102635 | LOW2.7 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-106564 | LOW2.7 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-106568 | LOW2.7 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-106577 | LOW2.7 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-109259 | LOW2.7 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-109262 | LOW2.7 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-109265 | LOW2.7 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-109269 | LOW2.7 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-109276 | LOW2.7 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-64685 | LOW2.7 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-55160 | LOW2.7 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-75806 | LOW2.7 | openssl 3.0.22-1~deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8328 | LOW2.7 | python3.11 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW2.7 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-15806 | LOW2.7 | python3.11 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW2.7 | python3.11 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3446 | LOW2.7 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-8328 | LOW2.7 | python3.11-minimal 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW2.7 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-15806 | LOW2.7 | python3.11-minimal 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW2.7 | python3.11-minimal 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3446 | LOW2.7 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58470 | LOW2.7 | wget 1.21.3-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11731 | LOW2.63 | libxslt1-dev 1.1.35-1+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11731 | LOW2.63 | libxslt1.1 1.1.35-1+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2007-2768 | LOW2.58 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 8.6% Low-Moderate Risk | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-90802 | LOW2.55 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91780 | LOW2.55 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-90802 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91780 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42250 | LOW2.55 | bzip2 1.0.8-5+b1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-62363 | LOW2.55 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-62363 | LOW2.55 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-109278 | LOW2.46 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109278 | LOW2.46 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109278 | LOW2.46 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109278 | LOW2.46 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109278 | LOW2.46 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109278 | LOW2.46 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109278 | LOW2.46 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109278 | LOW2.46 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109278 | LOW2.46 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109278 | LOW2.46 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14017 | LOW2.45 | curl 7.88.1-10+deb12u15 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-109275 | LOW2.45 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-109275 | LOW2.45 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 9.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | curl 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | dirmngr 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | dirmngr 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gnupg 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gnupg 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gnupg-utils 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gnupg-utils 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg-agent 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg-agent 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg-wks-client 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg-wks-client 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg-wks-server 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg-wks-server 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgconf 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgconf 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgsm 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgsm 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.12-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-62343 | LOW2.4 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-62946 | LOW2.4 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-62343 | LOW2.4 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-62946 | LOW2.4 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-0725 | LOW2.4 | curl 7.88.1-10+deb12u15 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0725 | LOW2.4 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0725 | LOW2.4 | libcurl4 7.88.1-10+deb12u15 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0725 | LOW2.4 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2025-69644 | LOW2.38 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18503 | LOW2.38 | libpython3.11-minimal 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18503 | LOW2.38 | libpython3.11-stdlib 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW2.29 | python3.11 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW2.29 | python3.11-minimal 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils 9.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-109281 | LOW2.24 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-109281 | LOW2.24 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18477 | LOW2.24 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW2.24 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-87864 | LOW2.22 | curl 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-87865 | LOW2.22 | curl 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-87866 | LOW2.22 | curl 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-92389 | LOW2.22 | curl 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-92391 | LOW2.22 | curl 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-87864 | LOW2.22 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-87865 | LOW2.22 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-87866 | LOW2.22 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-92389 | LOW2.22 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-92391 | LOW2.22 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-87864 | LOW2.22 | libcurl4 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-87865 | LOW2.22 | libcurl4 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-87866 | LOW2.22 | libcurl4 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-92389 | LOW2.22 | libcurl4 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-92391 | LOW2.22 | libcurl4 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-87864 | LOW2.22 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-87865 | LOW2.22 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-87866 | LOW2.22 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-92389 | LOW2.22 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-92391 | LOW2.22 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-93588 | LOW2.19 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-93588 | LOW2.19 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-106586 | LOW2.19 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-105083 | LOW2.14 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-105083 | LOW2.14 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-109258 | LOW2.12 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109272 | LOW2.12 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109274 | LOW2.12 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109279 | LOW2.12 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109280 | LOW2.12 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109282 | LOW2.12 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86424 | LOW2.12 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109258 | LOW2.12 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109272 | LOW2.12 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109274 | LOW2.12 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109279 | LOW2.12 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109280 | LOW2.12 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109282 | LOW2.12 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86424 | LOW2.12 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109258 | LOW2.12 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109272 | LOW2.12 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109274 | LOW2.12 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109279 | LOW2.12 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109280 | LOW2.12 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109282 | LOW2.12 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86424 | LOW2.12 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109258 | LOW2.12 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109272 | LOW2.12 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109274 | LOW2.12 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109279 | LOW2.12 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109280 | LOW2.12 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109282 | LOW2.12 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86424 | LOW2.12 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109258 | LOW2.12 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109272 | LOW2.12 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109274 | LOW2.12 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109279 | LOW2.12 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109280 | LOW2.12 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109282 | LOW2.12 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86424 | LOW2.12 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109258 | LOW2.12 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109272 | LOW2.12 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109274 | LOW2.12 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109279 | LOW2.12 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109280 | LOW2.12 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109282 | LOW2.12 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86424 | LOW2.12 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109258 | LOW2.12 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109272 | LOW2.12 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109274 | LOW2.12 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109279 | LOW2.12 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109280 | LOW2.12 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109282 | LOW2.12 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86424 | LOW2.12 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109258 | LOW2.12 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109272 | LOW2.12 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109274 | LOW2.12 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109279 | LOW2.12 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109280 | LOW2.12 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109282 | LOW2.12 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86424 | LOW2.12 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109258 | LOW2.12 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109272 | LOW2.12 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109274 | LOW2.12 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109279 | LOW2.12 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109280 | LOW2.12 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109282 | LOW2.12 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86424 | LOW2.12 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109258 | LOW2.12 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109272 | LOW2.12 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-109274 | LOW2.12 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109279 | LOW2.12 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109280 | LOW2.12 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-109282 | LOW2.12 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86424 | LOW2.12 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-13978 | LOW2.12 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8534 | LOW2.12 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-13978 | LOW2.12 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8534 | LOW2.12 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-13978 | LOW2.12 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8534 | LOW2.12 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102474 | LOW2.04 | dash 0.5.12-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-106566 | LOW2.04 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-106566 | LOW2.04 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-94266 | LOW1.98 | curl 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-94266 | LOW1.98 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-94266 | LOW1.98 | libcurl4 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2026-94266 | LOW1.98 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | — | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-13608 | LOW1.89 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW1.89 | curl 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.89 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-109260 | LOW1.89 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-109261 | LOW1.89 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-109263 | LOW1.89 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-109264 | LOW1.89 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-109268 | LOW1.89 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-109271 | LOW1.89 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-109260 | LOW1.89 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-109261 | LOW1.89 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-109263 | LOW1.89 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-109264 | LOW1.89 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-109268 | LOW1.89 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-109271 | LOW1.89 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13608 | LOW1.89 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW1.89 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.89 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13608 | LOW1.89 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW1.89 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.89 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13608 | LOW1.89 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW1.89 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.89 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-106582 | LOW1.89 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-35189 | LOW1.89 | openssl 3.0.22-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6879 | LOW1.87 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6879 | LOW1.87 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-105712 | LOW1.84 | dirmngr 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW1.84 | gnupg 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW1.84 | gnupg-utils 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW1.84 | gpg 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW1.84 | gpg-agent 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW1.84 | gpg-wks-client 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW1.84 | gpg-wks-server 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW1.84 | gpgconf 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW1.84 | gpgsm 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW1.84 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-105081 | LOW1.84 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-105081 | LOW1.84 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-73281 | LOW1.78 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils 2.40-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils 2.40-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils 2.40-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-91781 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-91781 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | dirmngr 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gnupg 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gnupg-utils 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg-agent 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg-wks-client 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg-wks-server 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgconf 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgsm 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-109267 | LOW1.68 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-109270 | LOW1.68 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-109273 | LOW1.68 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-109277 | LOW1.68 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-66011 | LOW1.68 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-93586 | LOW1.68 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-93587 | LOW1.68 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-109267 | LOW1.68 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-109270 | LOW1.68 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-109273 | LOW1.68 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-109277 | LOW1.68 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-66011 | LOW1.68 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-93586 | LOW1.68 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-93587 | LOW1.68 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-106584 | LOW1.68 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-106587 | LOW1.68 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-base 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-modules-5.36 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-4016 | LOW1.68 | procps 2:4.0.2-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-4217 | LOW1.68 | unzip 6.0-28+deb12u1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-82209 | LOW1.58 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-82209 | LOW1.58 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-82209 | LOW1.58 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-82209 | LOW1.58 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | dirmngr 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gnupg 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gnupg-utils 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gpg 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gpg-agent 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gpg-wks-client 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gpg-wks-server 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gpgconf 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gpgsm 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-109278 | LOW1.48 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-109278 | LOW1.48 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18503 | LOW1.43 | python3.11 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18503 | LOW1.43 | python3.11-minimal 3.11.2-6+deb12u8 fixed in 3.11.2-6+deb12u9 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-109258 | LOW1.27 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-109272 | LOW1.27 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-109274 | LOW1.27 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-109279 | LOW1.27 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-109280 | LOW1.27 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-109282 | LOW1.27 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-86424 | LOW1.27 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-109258 | LOW1.27 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-109272 | LOW1.27 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-109274 | LOW1.27 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-109279 | LOW1.27 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-109280 | LOW1.27 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-109282 | LOW1.27 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-86424 | LOW1.27 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6879 | LOW1.12 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6879 | LOW1.12 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-34152 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-45853 | NONE0 | zlib1g-dev 1:1.2.13.dfsg-1 No fix yet | 3.4% Low-Moderate Risk | Not Applicable |
| CVE-2025-68809 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-52005 | NONE0 | git-man 1:2.39.5-0+deb12u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72130 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74752 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89656 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89674 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89676 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-99999 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89495 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-97380 | NONE0 | mariadb-common 1:10.11.18-0+deb12u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-107818 | NONE0 | mariadb-common 1:10.11.18-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98466 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2023-39191 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89526 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89631 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89653 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90011 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-93787 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89524 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89633 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78408 | NONE0 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11082 | NONE0 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18220 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-96889 | NONE0 | gir1.2-rsvg-2.0 2.54.7+dfsg-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2013-7445 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-19449 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-19814 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-3847 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-52452 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52624 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52751 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53218 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-21803 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-26836 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26913 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26914 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26944 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35887 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38570 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-38630 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41045 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42118 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44941 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44942 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44951 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46729 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46811 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46813 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-47691 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50029 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-50217 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50226 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50282 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53068 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53168 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53179 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-53218 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56538 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56775 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57900 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21927 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-21967 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-21969 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23133 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37750 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-37777 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-37861 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37952 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-37957 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38069 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38182 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38248 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38369 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38582 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38585 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38595 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38722 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38734 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-39797 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39810 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39859 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39952 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71068 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-71073 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71152 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23171 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23208 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23226 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23361 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23447 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23448 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31493 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31527 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31729 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43049 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43250 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46068 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46219 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46241 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53115 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53117 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53118 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53120 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53129 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53143 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53156 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53262 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53272 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64001 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64305 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64341 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64348 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64424 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64556 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72042 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72098 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80521 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80951 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81000 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89465 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89508 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89617 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89638 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89725 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89736 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89761 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89970 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-89972 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-93288 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93817 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98116 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98260 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98524 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-46274 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-12456 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19378 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-11725 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-26934 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-25265 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-3238 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-26242 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-3640 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.4-4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.4-4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-76642 | NONE0 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78410 | NONE0 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-95619 | NONE0 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-86047 | NONE0 | mariadb-common 1:10.11.18-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-0840 | NONE0 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1179 | NONE0 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-66864 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | binutils-common 2.40-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-24975 | NONE0 | git-man 1:2.39.5-0+deb12u3 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-86420 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-86421 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93589 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93590 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-5709 | NONE0 | krb5-multidev 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-74345 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97417 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98417 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98532 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98548 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98550 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98573 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2019-19070 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-0400 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2026-107815 | NONE0 | mariadb-common 1:10.11.18-0+deb12u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-40170 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89783 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68426 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-53781 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39981 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43248 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63974 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93262 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93813 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97415 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97505 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89610 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-107823 | NONE0 | mariadb-common 1:10.11.18-0+deb12u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-3441 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26669 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41935 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53147 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57982 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21985 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22039 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-38081 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38204 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38636 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39744 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23327 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31568 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45893 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45943 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45957 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46130 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46293 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53179 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53330 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68409 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89481 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89846 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-14040 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-25743 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68183 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68324 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43042 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43126 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43414 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64078 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89596 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89779 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-93812 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97422 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97425 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97493 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97494 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97495 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97497 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2008-4609 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 32.1% High Exploitation Risk | Not Applicable |
| CVE-2026-102010 | NONE0 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109964 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-3864 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-52586 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42162 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37776 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40354 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23191 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43125 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43198 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46054 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46181 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52991 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53000 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53091 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63962 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64017 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64026 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68236 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68470 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74269 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80837 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80841 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81003 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89479 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89487 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89488 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89530 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89545 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89563 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89564 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89569 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89607 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89652 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89659 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89663 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89669 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89675 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89708 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89713 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89777 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89811 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89894 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89932 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90036 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90049 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90111 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90206 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90227 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90315 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98222 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98320 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98323 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98364 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98378 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53762 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53216 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57984 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40158 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23050 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31663 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45859 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-45894 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45942 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46090 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46204 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46330 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52956 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53005 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53009 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53053 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53132 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53185 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53224 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53230 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53246 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63826 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63940 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64025 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64109 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64160 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64319 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64320 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64481 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68086 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68118 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68161 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68273 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68289 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68293 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68323 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68329 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68391 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68401 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68404 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68448 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68453 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72288 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72320 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72329 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72338 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72382 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72398 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72405 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72469 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74289 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74391 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74405 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74474 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74496 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74506 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74537 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74611 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74677 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74684 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74695 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74700 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74715 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80668 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80698 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80710 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80864 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80944 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80947 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80952 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80971 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80973 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80976 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80977 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80978 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80982 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80989 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80994 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81001 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81002 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-81008 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89440 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89444 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89448 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89456 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89458 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89476 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89477 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89478 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89480 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89482 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89485 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89510 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89528 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89532 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89533 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89537 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89538 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89540 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89541 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89542 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89543 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89548 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89550 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89551 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89553 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89555 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89559 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89560 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89575 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89580 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89582 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89583 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89587 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89606 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89609 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89625 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89634 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89636 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89637 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89642 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89643 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89648 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89649 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89650 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89654 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89655 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89662 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89665 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89666 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89671 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89672 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89680 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89682 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89684 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89685 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89686 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89693 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89694 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89697 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89702 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89704 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89706 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89707 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89709 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89712 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89719 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89729 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89741 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89746 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89930 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90071 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90092 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90093 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90099 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90102 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90104 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90110 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90128 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90135 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90146 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90151 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90161 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90180 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90185 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90189 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90203 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90207 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90230 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90234 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90235 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90237 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90263 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90284 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90292 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90294 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90303 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90307 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90313 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90325 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90326 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90334 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90336 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90343 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90347 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93189 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93200 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93283 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93800 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97427 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97476 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97496 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97524 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-97531 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97532 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97555 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97557 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-97561 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97563 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97564 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97573 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97594 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97608 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97611 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97612 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97901 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97926 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97931 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97933 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97935 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97938 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97940 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97949 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97954 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97957 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97965 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97975 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97986 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97988 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97990 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97991 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98014 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98015 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98016 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98023 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98025 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98033 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98034 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98041 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98066 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98068 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98069 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98070 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98075 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98108 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98123 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98130 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98154 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98156 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98173 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98174 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98175 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98186 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98196 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98197 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98201 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98204 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98205 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98213 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98217 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98221 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98229 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98236 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98238 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98239 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98241 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98245 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98246 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98247 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98249 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98251 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98252 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98254 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98255 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98257 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98262 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98264 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98265 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98266 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98276 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98282 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98283 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98284 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98287 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98290 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98295 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98299 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98306 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98312 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98314 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98330 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98331 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98333 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98339 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98341 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98342 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98343 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98347 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98357 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98358 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98365 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98367 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98368 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98370 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98373 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98374 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98375 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98377 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98379 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98380 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98381 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98383 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98401 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98403 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98426 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98428 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98429 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98430 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-1247 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2961 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45884 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45885 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98176 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98362 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53613 | NONE0 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-78409 | NONE0 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90803 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90414 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-36694 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-21264 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-53095 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-57795 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21714 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89579 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98589 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98590 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-93125 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107821 | NONE0 | mariadb-common 1:10.11.18-0+deb12u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-53589 | NONE0 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90801 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90828 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90829 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90831 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21759 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 7.8% Low-Moderate Risk | Not Applicable |
| CVE-2026-53267 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89640 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90255 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2018-20712 | NONE0 | binutils-common 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-32256 | NONE0 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-1972 | NONE0 | binutils-common 2.40-2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2017-11754 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-107778 | NONE0 | krb5-multidev 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6240 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-36968 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43239 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89511 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89696 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-98167 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98439 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98449 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98452 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98454 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98457 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98526 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98578 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98582 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98597 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2024-0564 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-bin 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-40074 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23383 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31502 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31516 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53078 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68399 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90333 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-44032 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44033 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44034 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107822 | NONE0 | mariadb-common 1:10.11.18-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-3397 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89965 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40918 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40146 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98185 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98575 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-4647 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90804 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18090 | NONE0 | gir1.2-gdkpixbuf-2.0 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40071 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40355 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68342 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68736 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31505 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89786 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90054 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90068 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89778 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1153 | NONE0 | binutils-common 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-106565 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106567 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-26458 | NONE0 | krb5-multidev 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | krb5-multidev 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-68320 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98271 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98432 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98570 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98586 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2018-1121 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-3714 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-54107 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23239 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23240 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-49569 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-23039 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1178 | NONE0 | binutils-common 2.40-2 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-15003 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98464 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98471 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2017-13716 | NONE0 | binutils-common 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20673 | NONE0 | binutils-common 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-9996 | NONE0 | binutils-common 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-11081 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8224 | NONE0 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-19548 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6844 | NONE0 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90830 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91779 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91782 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-27943 | NONE0 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-86423 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86425 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2005-0406 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-0597 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-23005 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31082 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-37454 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-4133 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52590 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52591 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52625 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52629 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52648 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52671 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52676 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52761 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52770 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52797 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52888 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52920 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-53149 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53231 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53261 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53336 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53353 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53367 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53394 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53429 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53460 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53491 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-53523 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53529 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53538 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53574 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53627 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53846 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53999 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54013 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54280 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-6039 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-2193 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-25740 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26670 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26677 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26691 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26740 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26756 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26799 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26841 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26866 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26876 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26902 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26947 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26948 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26953 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-26962 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27010 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27011 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27041 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27057 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27062 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27079 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35784 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35794 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35799 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35808 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35860 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35904 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35924 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35931 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35942 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35945 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35946 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35951 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35961 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36911 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-36951 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38557 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38564 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38594 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38608 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38622 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38625 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40965 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40969 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40975 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40998 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40999 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-41008 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41023 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41031 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41082 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42128 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42139 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42239 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42241 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42243 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42279 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42317 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43819 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43824 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43850 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43872 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-43899 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43901 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43913 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44963 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45015 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46678 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46681 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46698 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46727 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46728 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46730 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46760 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46765 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46775 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46776 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46806 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46808 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46834 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46860 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47141 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47658 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-47661 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47662 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47664 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47703 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47752 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47794 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49568 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-49893 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49901 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49906 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49908 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49910 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49914 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49916 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49918 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49919 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49920 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49921 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49922 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49923 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49926 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49940 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49945 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49970 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49988 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-50009 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50017 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50028 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50111 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50166 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50285 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-50289 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-52559 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-52560 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53051 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53056 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53079 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53085 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53089 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53090 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-53091 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53094 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-53114 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53134 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53187 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53195 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53219 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53224 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53687 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-54683 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56544 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56565 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56566 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56583 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56588 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56591 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56592 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56611 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56641 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-56692 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56712 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56742 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57804 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57809 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57872 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57888 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57975 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57976 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57999 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58006 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58012 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58053 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-58089 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58096 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-58097 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58098 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58100 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58237 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58241 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21634 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21635 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21649 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21656 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21658 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21673 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-21693 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21696 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21723 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21729 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21768 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21801 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21831 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21836 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21870 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21872 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21885 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-21888 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21894 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21907 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21949 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21955 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-21961 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-21972 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21976 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22028 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22037 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 69.5% Actively Exploited | Not Applicable |
| CVE-2025-22043 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-22048 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22053 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22057 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22070 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22103 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22109 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22113 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22125 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22127 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23129 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23130 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23132 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37747 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37800 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37802 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-37806 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37807 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37833 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37834 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37842 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37853 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37856 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37860 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37880 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37893 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37956 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-37977 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38006 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38014 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38029 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38038 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38039 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38041 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38042 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38045 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38059 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38064 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38080 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38096 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38127 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38132 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38140 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38195 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38207 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38244 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38246 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38261 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38264 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38272 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38283 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38311 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38333 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38359 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38426 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38429 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38438 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38449 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38507 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38531 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38544 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38590 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38597 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38615 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38692 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38705 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38709 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38716 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39677 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39705 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39707 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39720 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39732 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39746 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39747 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39762 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39767 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39779 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39789 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39829 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39850 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39851 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39886 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39910 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39932 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39933 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39940 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39947 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39989 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40075 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40160 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40325 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40328 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40339 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68188 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68209 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68236 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68304 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68379 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71109 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71129 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71138 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71160 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71184 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71188 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71202 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71227 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71272 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71273 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71285 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71289 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71313 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71315 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100070 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-100072 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100075 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-100076 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100077 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100078 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22996 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23000 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23088 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23137 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23138 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23213 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23214 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23247 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23265 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23276 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23330 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23346 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23371 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23374 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23419 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23465 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23472 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31410 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31420 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31458 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31462 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31487 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31531 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31537 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31557 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31560 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31579 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31592 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31606 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31648 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31655 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31675 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31677 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31692 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31722 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31723 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31724 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31725 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31767 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31771 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31777 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43009 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43010 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43016 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43022 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43036 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43048 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43073 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43083 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43088 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43091 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43101 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43107 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43115 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43118 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43119 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43129 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43137 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43153 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43161 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43167 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43170 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43172 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43173 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43204 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43213 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43215 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43234 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43244 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43271 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43288 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43299 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43308 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43309 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43310 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43317 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43318 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43338 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43344 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43352 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43353 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43362 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43409 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43413 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43416 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43419 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43443 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43456 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45855 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45858 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45877 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45892 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45897 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45899 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45901 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45917 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45934 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45944 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45961 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45981 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45985 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45988 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45993 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46000 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46012 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46014 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46032 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46059 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46071 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46148 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46153 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46156 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46157 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46200 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46225 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46226 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46229 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46245 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46254 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46282 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46302 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46312 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52936 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52937 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52944 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52961 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52988 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52990 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53015 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53017 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53018 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53027 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53070 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53076 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53083 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53102 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53106 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53107 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53122 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53220 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53226 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53232 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53237 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53258 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53265 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53285 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53292 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53297 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53313 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53317 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53345 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53353 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53358 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53376 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53377 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63845 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63846 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63847 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63848 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63853 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63854 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63856 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63858 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63963 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63983 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63999 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64006 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64036 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64060 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64076 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64077 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64079 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64112 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64144 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64146 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64163 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64190 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64210 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64212 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64213 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64241 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64345 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64463 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68085 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68098 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68112 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68152 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68205 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68233 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68242 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68247 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68258 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68286 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68287 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68312 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68396 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68435 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68441 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68445 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68447 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68449 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68471 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72028 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72073 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72106 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72144 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72147 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72162 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72168 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72198 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72200 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72203 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72213 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72324 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72325 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72334 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72336 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72337 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72341 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72369 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72373 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72375 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72379 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72380 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72383 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72397 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72402 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72404 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72413 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72416 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72420 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72423 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72434 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72438 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72440 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72454 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72470 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72472 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72488 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72493 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74257 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74264 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74268 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74272 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74278 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74291 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74294 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74302 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74307 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74314 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74317 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74334 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74337 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74342 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74347 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74350 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74356 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74386 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74388 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74389 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74401 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74407 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74417 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74445 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74466 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74521 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74527 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74544 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74565 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74592 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74599 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74600 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74638 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74687 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74713 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74723 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74725 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74729 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74735 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74740 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74747 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80526 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80551 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80554 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80556 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80576 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80579 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80580 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80587 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80602 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80623 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80628 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80629 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80631 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80634 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80636 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80637 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80650 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80654 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80670 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80671 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80676 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80694 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80695 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80928 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80931 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80932 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80937 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80938 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80964 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80965 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80966 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80968 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80969 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80972 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80980 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80991 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80992 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80999 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81016 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81017 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89437 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89441 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89452 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89457 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89461 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89462 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89463 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89464 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89468 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89469 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89470 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89471 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89472 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89474 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89475 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89483 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89489 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89490 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89491 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89492 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89493 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89494 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89496 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89497 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89498 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89504 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89512 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89515 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89520 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89525 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89544 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89549 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89554 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89557 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89561 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89565 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89567 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89573 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89574 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89585 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89594 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89595 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89597 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89599 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89608 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89611 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89615 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89616 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89621 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89622 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89626 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89628 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89699 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89711 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89718 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89720 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89722 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89723 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89724 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89726 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89730 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89732 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89733 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89738 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89740 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89742 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89751 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89756 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89757 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89762 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89763 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89824 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89837 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89881 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89896 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89912 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89996 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90007 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90015 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90021 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90056 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90061 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90063 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90073 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90074 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90075 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90076 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90081 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90083 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90087 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90088 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90090 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90091 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90098 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90103 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90105 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90106 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90107 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90108 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90112 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90114 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90116 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90122 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90124 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90140 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90141 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90143 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90148 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90149 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90150 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90152 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90154 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90155 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90157 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90162 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90166 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90174 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90176 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90179 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90196 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90198 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90199 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90200 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90204 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90205 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90208 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90214 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90218 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90219 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90221 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90222 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90223 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90224 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90225 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90226 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90228 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90229 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90232 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90245 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90247 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90248 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90249 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90251 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90257 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90259 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90264 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90265 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90273 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90274 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90286 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90287 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90289 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90293 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90295 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90296 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90297 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90298 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90300 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90301 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90302 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90308 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90309 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90314 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90316 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90318 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90319 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90320 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90321 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90322 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90327 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90328 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90337 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90341 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90345 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90348 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90352 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90354 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90361 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90362 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90378 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90407 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90434 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92488 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92504 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93056 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93151 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-93159 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93185 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93188 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93190 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93191 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93192 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93196 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93203 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93204 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93228 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93261 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93264 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93271 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93272 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93278 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93279 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93280 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93281 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93282 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93285 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93287 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93782 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93786 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93789 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93790 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93791 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93793 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93796 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93799 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93802 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93803 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93804 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93805 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93806 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93807 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93808 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93815 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93816 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93819 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93820 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93821 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93822 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93824 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93826 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93830 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97407 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97408 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97409 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97411 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97413 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97418 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97419 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97420 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97421 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97434 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97435 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97437 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97438 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97439 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97442 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97444 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97448 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97451 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97455 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97456 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97472 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97475 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97478 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97482 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97485 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97486 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97489 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97490 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97499 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97500 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97502 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97506 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97507 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97508 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97512 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97515 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97517 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97518 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97523 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-97529 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97534 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97535 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97536 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97537 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97539 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97540 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97541 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97554 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97558 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97559 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97562 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97565 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97567 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97572 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97576 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97581 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97582 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97587 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97596 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97598 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97599 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97600 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97604 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97609 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97908 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97909 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97910 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97918 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97920 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97924 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97925 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97929 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97930 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97939 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97950 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97951 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97952 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97953 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97964 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97969 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97970 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97973 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97977 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97978 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97981 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97982 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97987 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97992 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97994 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97995 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97998 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98006 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98008 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98013 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98017 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98019 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98022 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98026 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98027 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98030 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98031 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98043 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98056 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98063 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98071 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98072 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98080 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98092 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98103 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98104 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98107 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98111 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98113 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98114 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98121 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98131 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98142 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98157 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98158 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98159 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98160 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98161 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98162 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98169 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98170 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98172 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98180 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98187 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98188 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98189 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98190 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98192 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98193 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98194 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98195 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98198 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98199 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98207 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98209 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98210 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98212 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98227 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98248 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98253 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98269 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98272 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98279 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98288 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98292 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98294 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98298 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98302 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98303 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98309 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98311 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98313 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98322 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98327 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98335 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98340 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98348 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98349 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98351 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98352 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98353 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98355 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98359 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98360 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98369 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98407 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98409 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98410 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98413 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98419 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98420 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98423 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98455 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98461 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98503 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98511 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98521 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98539 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98541 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98547 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98554 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98556 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98567 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98580 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98801 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2008-2544 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2011-4915 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2011-4916 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2011-4917 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9892 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9900 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-10723 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-8660 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-13693 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-13694 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12928 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12378 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12379 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12380 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12381 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12382 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12455 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-4543 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-31081 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31085 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-4134 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52653 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-53823 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53857 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54030 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54088 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35843 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39990 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40057 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68219 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68334 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68378 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68822 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100071 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31486 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43253 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53229 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53284 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63855 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64388 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64513 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68102 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68238 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68241 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68288 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68408 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68412 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68418 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72007 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72009 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72254 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72315 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72321 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72376 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72439 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72494 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74261 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74308 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74318 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74338 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74374 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74397 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74536 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74543 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74571 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74653 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74733 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74754 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80611 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80616 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80643 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80653 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80689 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80704 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80930 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80941 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80948 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80949 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80963 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80967 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80974 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80983 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80987 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80988 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80990 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80996 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89484 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89527 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89531 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89539 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89552 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89566 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89576 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89586 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89598 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89601 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89604 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89605 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89627 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89644 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89645 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89647 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89710 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89744 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89749 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89752 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89753 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89759 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89765 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89816 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89862 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89872 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89877 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89923 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89924 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89925 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89944 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89953 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89975 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89982 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90053 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90055 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90058 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90060 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90062 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90066 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90067 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90070 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90072 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90078 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90084 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90097 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90109 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90119 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90125 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90126 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90138 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90139 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90160 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90182 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90183 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90184 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90186 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90187 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90188 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90190 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90194 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90202 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90209 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90213 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90216 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90250 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90253 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90254 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90267 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90281 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90283 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90285 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90290 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90311 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90330 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90335 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90346 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90411 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90415 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92493 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92494 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92524 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93072 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93102 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93116 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93130 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93136 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93145 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93161 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93186 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93199 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93202 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93268 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93269 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93274 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93286 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93785 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93788 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93794 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93795 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93798 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93811 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93814 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93823 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93825 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93828 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93829 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97416 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97424 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97430 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97436 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97440 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97441 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97446 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97477 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97479 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97480 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97481 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97483 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97484 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97487 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97488 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97491 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97492 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97501 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97509 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97510 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97516 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97530 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97556 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97566 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97592 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97597 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97601 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97613 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97615 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97616 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97619 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97899 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97904 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97905 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97906 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97921 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97922 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97923 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97927 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97948 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97958 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97959 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97963 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97979 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97984 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97985 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97989 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97993 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97997 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98003 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98009 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98010 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98011 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98012 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98021 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98044 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98046 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98055 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98058 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98064 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98067 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98073 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98074 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98087 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98124 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98125 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98126 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98127 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98128 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98129 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98148 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98177 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98179 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98182 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98191 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98202 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98203 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98208 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98233 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98234 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98237 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98285 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98289 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98304 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98307 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98308 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98317 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98319 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98321 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98325 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98326 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98328 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98329 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98332 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98334 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98337 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98338 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98344 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98345 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98386 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98387 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98388 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98389 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98393 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98394 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98398 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98399 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98400 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98402 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98404 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98406 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98421 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98422 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98424 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98425 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98427 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-27171 | NONE0 | zlib1g-dev 1:1.2.13.dfsg-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-107816 | NONE0 | mariadb-common 1:10.11.18-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-85985 | NONE0 | mariadb-common 1:10.11.18-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1147 | NONE0 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-16768 | NONE0 | gir1.2-gdkpixbuf-2.0 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-102635 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-106564 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106568 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106577 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109259 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109262 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109265 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109269 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109276 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64685 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-55160 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-36881 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71225 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64391 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98300 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98576 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98577 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-13595 | NONE0 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40338 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71193 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23035 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98501 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2024-57360 | NONE0 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-1176 | NONE0 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90802 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91780 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-1000021 | NONE0 | git-man 1:2.39.5-0+deb12u3 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-62363 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2008-3134 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-11850 | NONE0 | krb5-multidev 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2004-0230 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 80.3% Actively Exploited | Not Applicable |
| CVE-2010-4563 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2026-107708 | NONE0 | krb5-multidev 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2005-3660 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109275 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63871 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98549 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-81893 | NONE0 | gir1.2-gdkpixbuf-2.0 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-30258 | NONE0 | gnupg-l10n 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68972 | NONE0 | gnupg-l10n 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62343 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62946 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-20794 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-52771 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53447 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-24864 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26869 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27408 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36024 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36949 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39508 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42107 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46787 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46870 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-50135 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53176 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-53178 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-56729 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57857 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57974 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21651 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21732 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21825 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21892 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22115 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38234 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38524 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38717 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39726 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39754 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39927 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39961 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68296 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68745 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-71074 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23004 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23118 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23207 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23348 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43053 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45949 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46017 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53108 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64038 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98301 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98354 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98476 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98507 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98508 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98515 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98536 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98537 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98538 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98555 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98559 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98568 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98581 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98598 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98662 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98749 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98768 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98826 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2017-0630 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2019-16230 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16234 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68081 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-15213 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-98181 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98711 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2012-4542 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109281 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2020-14304 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-42123 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68768 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98078 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98273 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98435 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98443 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98460 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98525 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98565 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98569 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98572 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98583 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2018-17977 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-26661 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26662 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26672 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26757 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26758 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26768 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-68337 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98101 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98363 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-107817 | NONE0 | mariadb-common 1:10.11.18-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93588 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98453 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2010-5321 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-44169 | NONE0 | mariadb-common 1:10.11.18-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-85745 | NONE0 | mariadb-common 1:10.11.18-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-105083 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-41848 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-16089 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-42156 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42158 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81005 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93117 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98286 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98416 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98456 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98506 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98544 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98558 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98588 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98593 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98748 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2019-16229 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16231 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16232 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-16233 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106566 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-109260 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109261 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109263 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109264 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109268 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109271 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-105712 | NONE0 | gnupg-l10n 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-105081 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2020-35501 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66861 | NONE0 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66862 | NONE0 | binutils-common 2.40-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | binutils-common 2.40-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | binutils-common 2.40-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-91781 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-3219 | NONE0 | gnupg-l10n 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109267 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109270 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109273 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109277 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-66011 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93586 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93587 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2015-2877 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-54227 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-54233 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50057 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50211 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40268 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40303 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98450 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98451 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98502 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98509 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98514 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98531 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98551 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98579 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-bin 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-57062 | NONE0 | gnupg-l10n 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109278 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69644 | NONE0 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-109258 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109272 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109274 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109279 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109280 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109282 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86424 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-11191 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98433 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98527 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98516 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98535 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98553 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2007-3719 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42155 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98505 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98519 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98529 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98594 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.2.15-2+b13 No fix yet | — | Not Applicable |
| CVE-2026-106570 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106571 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106572 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106573 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106574 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106575 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106576 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106578 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106579 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106580 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107208 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107209 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107210 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109266 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-106570 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106571 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106572 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106573 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106574 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106575 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106576 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106578 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106579 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106580 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107208 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107209 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107210 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109266 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-106570 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106571 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106572 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106573 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106574 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106575 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106576 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106578 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106579 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106580 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107208 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107209 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107210 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109266 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-88373 | NONE0 | libde265-0 1.0.11-1+deb12u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-61147 | NONE0 | libde265-0 1.0.11-1+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-67693 | NONE0 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-88647 | NONE0 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-88648 | NONE0 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-95184 | NONE0 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-95209 | NONE0 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-95210 | NONE0 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-84450 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-84451 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-41069 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-47247 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-47254 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-47714 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-48029 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-50142 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-62289 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-62292 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-84384 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-84446 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-84447 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-84448 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-84449 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-25269 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-84444 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| TEMP-0000000-0F03E5 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| TEMP-0000000-153207 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| TEMP-0000000-18A2CE | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| TEMP-0000000-1B5D39 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| TEMP-0000000-21F713 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| TEMP-0000000-301DE5 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| TEMP-0000000-415AE1 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| TEMP-0000000-4EF776 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| TEMP-0000000-5124DE | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| TEMP-0000000-57F868 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| TEMP-0000000-6C5194 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| TEMP-0000000-78AC20 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| TEMP-0000000-809756 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| TEMP-0000000-8A4B18 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| TEMP-0000000-9253BB | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| TEMP-0000000-956D99 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| TEMP-0000000-BBE297 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| TEMP-0000000-D1A721 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| TEMP-0000000-D2EEB5 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| TEMP-0000000-DB3DE2 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| TEMP-0000000-F2B97A | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| TEMP-0000000-FDE8B2 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| TEMP-1148137-089975 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| TEMP-1148137-126A7B | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| CVE-2025-29070 | NONE0 | liblcms2-2 2.14-2+deb12u1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2025-29070 | NONE0 | liblcms2-dev 2.14-2+deb12u1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-106570 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106571 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106572 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106573 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106574 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106575 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106576 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106578 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106579 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106580 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107208 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107209 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107210 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109266 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-106570 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106571 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106572 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106573 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106574 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106575 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106576 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106578 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106579 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106580 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107208 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107209 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107210 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109266 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-106570 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106571 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106572 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106573 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106574 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106575 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106576 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106578 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106579 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106580 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107208 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107209 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107210 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109266 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-106570 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106571 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106572 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106573 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106574 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106575 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106576 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106578 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106579 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106580 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107208 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107209 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107210 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109266 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-106570 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106571 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106572 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106573 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106574 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106575 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106576 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106578 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106579 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106580 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107208 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107209 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107210 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109266 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-106570 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106571 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106572 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106573 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106574 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106575 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106576 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106578 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106579 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106580 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107208 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107209 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107210 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109266 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-106570 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106571 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106572 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106573 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106574 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106575 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106576 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106578 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106579 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106580 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107208 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107209 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107210 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109266 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-106570 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106571 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106572 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106573 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106574 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106575 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106576 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106578 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106579 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106580 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107208 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107209 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107210 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109266 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-106570 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106571 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106572 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106573 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106574 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106575 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106576 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106578 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106579 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106580 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107208 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107209 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107210 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109266 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-106570 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106571 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106572 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106573 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106574 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106575 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106576 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106578 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106579 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106580 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107208 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107209 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107210 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109266 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-85746 | NONE0 | libmariadb-dev 1:10.11.18-0+deb12u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-92262 | NONE0 | libmariadb-dev 1:10.11.18-0+deb12u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-85746 | NONE0 | libmariadb-dev-compat 1:10.11.18-0+deb12u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-92262 | NONE0 | libmariadb-dev-compat 1:10.11.18-0+deb12u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-85746 | NONE0 | libmariadb3 1:10.11.18-0+deb12u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-92262 | NONE0 | libmariadb3 1:10.11.18-0+deb12u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-31047 | NONE0 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-31047 | NONE0 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-82560 | NONE0 | libperl5.36 5.36.0-7+deb12u4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-107161 | NONE0 | libsasl2-2 2.1.28+dfsg-10 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107161 | NONE0 | libsasl2-modules-db 2.1.28+dfsg-10 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7709 | NONE0 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-7709 | NONE0 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-27587 | NONE0 | libssl-dev 3.0.22-1~deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-27587 | NONE0 | libssl3 3.0.22-1~deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-36849 | NONE0 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | — | Not Applicable |
| CVE-2026-36849 | NONE0 | libtiff6 4.5.0-6+deb12u4 No fix yet | — | Not Applicable |
| CVE-2026-36849 | NONE0 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | — | Not Applicable |
| TEMP-0601525-BEBB65 | NONE0 | libwmf-0.2-7 0.2.12-5.1 No fix yet | — | Not Applicable |
| TEMP-0601525-BEBB65 | NONE0 | libwmf-dev 0.2.12-5.1 No fix yet | — | Not Applicable |
| TEMP-0601525-BEBB65 | NONE0 | libwmflite-0.2-7 0.2.12-5.1 No fix yet | — | Not Applicable |
| CVE-2026-90037 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93221 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40137 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40333 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31432 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64138 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64389 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64392 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64400 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80883 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80905 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89788 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89803 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89810 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89913 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89922 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89980 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90003 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90048 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90057 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90167 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90169 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90375 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90392 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90398 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90417 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92499 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92507 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92509 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92510 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-92511 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-92512 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93105 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93154 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93175 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93176 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93210 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93792 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98085 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98171 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-25742 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40077 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40289 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40311 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40337 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68190 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68322 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71065 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23393 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31706 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31707 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43490 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53401 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63805 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63816 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63819 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63959 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68083 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68097 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68185 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80739 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80761 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80771 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80833 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80834 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80836 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80847 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80861 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80866 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80907 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80912 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80914 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80920 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80925 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81007 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89562 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89776 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89780 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89781 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89782 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89784 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89785 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89787 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89789 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89792 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89793 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89794 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89796 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89808 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89813 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89817 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89818 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89821 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89823 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89832 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89833 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89840 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89843 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89845 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89847 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89849 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89850 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89851 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89852 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89853 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89854 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89855 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89856 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89858 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89861 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89863 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89864 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89865 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89871 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89876 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89878 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89879 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89880 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89883 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89884 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89887 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89888 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89890 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89891 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89892 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89893 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89895 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89897 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89901 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89906 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89926 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89927 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89933 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89934 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89936 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89937 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89939 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89945 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89946 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89947 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89948 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89949 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89951 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89952 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89954 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89955 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89956 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89957 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89958 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89959 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89964 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89968 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-89969 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89973 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89979 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89983 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89984 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89987 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89989 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89992 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89993 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89995 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89997 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89999 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90000 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90016 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90017 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90018 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90019 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90020 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90025 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90029 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90031 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90032 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90033 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90034 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90041 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90153 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90156 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90329 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90353 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90357 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90358 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90360 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90368 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90372 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90382 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90386 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90388 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90391 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90393 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90394 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90395 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90403 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90413 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-90416 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90419 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90420 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90431 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90435 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-92476 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92477 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92480 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92485 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92496 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92498 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92500 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92501 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92503 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92508 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92514 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92520 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92521 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92522 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-92523 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92525 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93037 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93039 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93040 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93041 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93046 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93048 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93049 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93051 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93052 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93053 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93054 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93055 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93061 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93063 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93064 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93067 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93073 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93095 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93098 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93103 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93108 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93109 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93110 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93114 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93115 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93118 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93120 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93131 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93137 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93138 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93140 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93141 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93149 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93152 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93158 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93160 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93165 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93167 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93170 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93174 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93177 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93178 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93179 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93182 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93183 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93184 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93206 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93208 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93213 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93214 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93219 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93222 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93226 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93234 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93236 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93238 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93242 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93243 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93244 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93245 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93247 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93252 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93256 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93781 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93783 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93784 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93797 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97445 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97449 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97450 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97452 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97453 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97454 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97568 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97605 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98076 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98077 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98079 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98081 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98088 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98089 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98090 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98091 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98094 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98095 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98096 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98097 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98098 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98099 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98275 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40003 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40097 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40180 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40266 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68781 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71198 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43249 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43258 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53368 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63825 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68203 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68303 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74690 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80738 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80747 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80755 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80785 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80786 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80820 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80851 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80884 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89795 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89797 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89799 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89822 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89834 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89835 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89838 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89848 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89859 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89860 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89870 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89899 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89920 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89921 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89929 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89938 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89960 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89962 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89988 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89998 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90002 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90013 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90023 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90044 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90045 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90359 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90365 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90379 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90383 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90385 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90389 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90401 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90410 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90418 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90421 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90433 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92481 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92482 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93042 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-93047 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93050 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93058 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93062 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93081 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93091 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93093 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93099 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93100 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93104 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93122 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93128 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93129 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93142 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93146 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93150 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93155 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93163 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93168 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93172 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93205 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93216 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93231 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93235 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93239 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93251 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93260 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93810 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98102 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2023-53851 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98436 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98479 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98481 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98482 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98483 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98484 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98485 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98486 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98488 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98489 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98490 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98491 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98493 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98494 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98495 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98498 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98499 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98602 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98606 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98607 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98608 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98609 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98610 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98612 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98614 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98620 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98621 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98622 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98623 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98624 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98625 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98626 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98628 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98629 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98631 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98632 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98634 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98636 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98640 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98643 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98644 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98647 | NONE0 | linux-libc-dev 6.1.187-1 fixed in 6.1.190-1 | — | Not Applicable |
| CVE-2026-98652 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98655 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98656 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98657 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98660 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98663 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98664 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98665 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98666 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98668 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98669 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98670 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98671 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98672 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98677 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98679 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98681 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98682 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98683 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98684 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98685 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98686 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98687 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98694 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98695 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98696 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98697 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98698 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98700 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98701 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98703 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98704 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98705 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98706 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98707 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98708 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98709 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98710 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98714 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98715 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98716 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98720 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98721 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98722 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98725 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98726 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98732 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98733 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98734 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98735 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98736 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98737 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98738 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98739 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98740 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98741 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98742 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98745 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98750 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98751 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98752 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98753 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98754 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98755 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98756 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98757 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98760 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98761 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98762 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98763 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98764 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98765 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98766 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98767 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98769 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98771 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98772 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98773 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98775 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98777 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98778 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98779 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98780 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98784 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98785 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98786 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98789 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98790 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98792 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98793 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98794 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98795 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98796 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98797 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98798 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98799 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98800 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98802 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98803 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98805 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98807 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98808 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98809 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98810 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98811 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98812 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98814 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98815 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98816 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98819 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98820 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98822 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98823 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98824 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98825 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98827 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98828 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98829 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98830 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98831 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98833 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98834 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98836 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98837 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98838 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98839 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98840 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98846 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98847 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98850 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98851 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98852 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98853 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98854 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98855 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98856 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98857 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98859 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98862 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| CVE-2026-98863 | NONE0 | linux-libc-dev 6.1.187-1 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | — | Not Applicable |
| CVE-2026-85746 | NONE0 | mariadb-common 1:10.11.18-0+deb12u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-92262 | NONE0 | mariadb-common 1:10.11.18-0+deb12u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-27587 | NONE0 | openssl 3.0.22-1~deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | — | Not Applicable |
| CVE-2026-82560 | NONE0 | perl 5.36.0-7+deb12u4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-82560 | NONE0 | perl-base 5.36.0-7+deb12u4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-82560 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| TEMP-0517018-A83CE6 | NONE0 | sysvinit-utils 3.06-4 No fix yet | — | Not Applicable |
| TEMP-0290435-0B57B5 | NONE0 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-85091 | NONE0 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-85091 | NONE0 | zlib1g-dev 1:1.2.13.dfsg-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.