Last scanned:
This image is safe for production use. The scanner identified 124 post-exploit-only issues, but the highest severity is only 3.98 and none reach the high-severity threshold, so they pose minimal real-world risk without prior access. Given the official status, immutability, and absence of exposed vulnerabilities, this image is suitable for production deployment.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2025-11082 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18220 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils 2.44-3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | curl 8.14.1-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9079 | LOW3.82 | curl 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | curl 8.14.1-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW3.82 | gzip 1.13-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | curl 8.14.1-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW3.72 | curl 8.14.1-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2005-2541 | LOW3.6 | tar 1.35+dfsg-3.1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2010-4651 | LOW3.48 | patch 2.8-2 No fix yet | 4.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils 2.44-3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | curl 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56391 | LOW3.11 | coreutils 9.7-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils 2.44-3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-15003 | LOW2.86 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-45261 | LOW2.8 | patch 2.8-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-56288 | LOW2.8 | patch 2.8-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56289 | LOW2.8 | patch 2.8-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.35+dfsg-3.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2008-1687 | LOW2.7 | m4 1.4.19-8 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2008-1688 | LOW2.7 | m4 1.4.19-8 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6951 | LOW2.7 | patch 2.8-2 No fix yet | 8.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6952 | LOW2.7 | patch 2.8-2 No fix yet | 8.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | bsdutils 1:2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | mount 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-42250 | LOW2.55 | bzip2 1.0.8-6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | LOW2.48 | curl 8.14.1-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | LOW2.48 | curl 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | curl 8.14.1-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 9.7-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | curl 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.13-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-20712 | LOW2.34 | binutils 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2025-66864 | LOW2.29 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW2.29 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils 9.7-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW2.24 | coreutils 9.7-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2019-1010022 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010022 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010022 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010022 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-8376 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6653 | NONE0 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8376 | NONE0 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8376 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8376 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13221 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42496 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13221 | NONE0 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42496 | NONE0 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13221 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42496 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13221 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42496 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-57432 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57432 | NONE0 | perl 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57432 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57432 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-8286 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-15079 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2007-0086 | NONE0 | apache2 2.4.68-1~deb13u1 No fix yet | 9.6% Low-Moderate Risk | Not Applicable |
| CVE-2007-0086 | NONE0 | apache2-bin 2.4.68-1~deb13u1 No fix yet | 9.6% Low-Moderate Risk | Not Applicable |
| CVE-2007-0086 | NONE0 | apache2-data 2.4.68-1~deb13u1 No fix yet | 9.6% Low-Moderate Risk | Not Applicable |
| CVE-2007-0086 | NONE0 | apache2-utils 2.4.68-1~deb13u1 No fix yet | 9.6% Low-Moderate Risk | Not Applicable |
| CVE-2025-11082 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18220 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11082 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18220 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11082 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18220 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11082 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18220 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11082 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18220 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11082 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18220 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncursesw6 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-48962 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11082 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18220 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-11979 | NONE0 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2013-7445 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-19449 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-19814 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-3847 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-21803 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-38137 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38187 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38206 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38421 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39859 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39862 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39958 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23208 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31493 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46279 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53089 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53109 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53118 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64530 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64531 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-12456 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19378 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-11725 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-26934 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-25265 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-3238 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-26242 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-3640 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-48962 | NONE0 | perl 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-48962 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-48962 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56208 | NONE0 | libaom3 3.12.1-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66864 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | binutils-common 2.44-3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-66864 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-66864 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | libbinutils 2.44-3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-20796 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20796 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20796 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20796 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2025-66864 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-66864 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | libctf0 2.44-3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12064 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8927 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8932 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9079 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-9545 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66864 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-5709 | NONE0 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-5709 | NONE0 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-5709 | NONE0 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-5709 | NONE0 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2015-3276 | NONE0 | libldap2 2.6.10+dfsg-1 No fix yet | 5.3% Low-Moderate Risk | Not Applicable |
| CVE-2017-17740 | NONE0 | libldap2 2.6.10+dfsg-1 No fix yet | 7.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-42497 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9538 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-66864 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | libsframe1 2.44-3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-19070 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-0400 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-42497 | NONE0 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9538 | NONE0 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42497 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9538 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42497 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9538 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9547 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-9080 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-3441 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-3441 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54369 | NONE0 | libacl1 2.3.2-2+b1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56209 | NONE0 | libaom3 3.12.1-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-56210 | NONE0 | libaom3 3.12.1-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56211 | NONE0 | libaom3 3.12.1-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-3441 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-3441 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-3441 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-3441 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-3441 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-58015 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22104 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38204 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38636 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23102 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23327 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31568 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46130 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53330 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40064 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43414 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2008-4609 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 32.1% High Exploitation Risk | Not Applicable |
| CVE-2021-3864 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-43198 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46181 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52991 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53000 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53091 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53277 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63879 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63970 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64017 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64287 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64364 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64375 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64434 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64534 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64552 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64558 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40158 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40168 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46317 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46325 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46330 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52953 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52956 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53005 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53009 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53078 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53224 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53246 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53250 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53260 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63941 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63979 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64024 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64068 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64117 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64160 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64192 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64216 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64255 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64280 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64283 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64286 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64341 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64401 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64481 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64508 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64520 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64539 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64543 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64548 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64551 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64554 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64557 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64559 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64560 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-1247 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2961 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45884 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45885 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-22185 | NONE0 | libldap2 2.6.10+dfsg-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40130 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-36694 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6238 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2018-20712 | NONE0 | binutils-common 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-32256 | NONE0 | binutils-common 2.44-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2018-20712 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-32256 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2018-20712 | NONE0 | libbinutils 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-32256 | NONE0 | libbinutils 2.44-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-20712 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-32256 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2018-20712 | NONE0 | libctf0 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-32256 | NONE0 | libctf0 2.44-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-11856 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8924 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2018-20712 | NONE0 | libgprofng0 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-32256 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-15649 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2018-20712 | NONE0 | libsframe1 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-32256 | NONE0 | libsframe1 2.44-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-66032 | NONE0 | libssh2-1t64 1.11.1-1+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-66033 | NONE0 | libssh2-1t64 1.11.1-1+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6240 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2025-68729 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64535 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-0564 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-15649 | NONE0 | perl 5.40.1-6 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-15649 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-15649 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40074 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45932 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53090 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53092 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-44032 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44033 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54370 | NONE0 | libacl1 2.3.2-2+b1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-54371 | NONE0 | libattr1 1:2.5.2-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-3397 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-13757 | NONE0 | libp11-kit0 0.25.5-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40146 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libblkid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | liblastlog2-2 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libmount1 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libsmartcols1 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libuuid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40355 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68319 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43197 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1153 | NONE0 | binutils-common 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-1153 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-1153 | NONE0 | libbinutils 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-5435 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1153 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-1153 | NONE0 | libctf0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-10966 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-1153 | NONE0 | libgprofng0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-26458 | NONE0 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-26458 | NONE0 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-26458 | NONE0 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-26458 | NONE0 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-1153 | NONE0 | libsframe1 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-66034 | NONE0 | libssh2-1t64 1.11.1-1+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2018-1121 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-3714 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-23039 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1178 | NONE0 | binutils-common 2.44-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-15003 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1178 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-15003 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1178 | NONE0 | libbinutils 2.44-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-15003 | NONE0 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1178 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-15003 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1178 | NONE0 | libctf0 2.44-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-15003 | NONE0 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1178 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-15003 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1178 | NONE0 | libsframe1 2.44-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-15003 | NONE0 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | binutils-common 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20673 | NONE0 | binutils-common 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-9996 | NONE0 | binutils-common 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-11081 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6844 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20673 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-9996 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-11081 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6844 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | libbinutils 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20673 | NONE0 | libbinutils 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-9996 | NONE0 | libbinutils 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-11081 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6844 | NONE0 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libblkid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20673 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-9996 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-11081 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6844 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | libctf0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20673 | NONE0 | libctf0 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-9996 | NONE0 | libctf0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-11081 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6844 | NONE0 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66382 | NONE0 | libexpat1 2.8.2-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | libgprofng0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20673 | NONE0 | libgprofng0 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-9996 | NONE0 | libgprofng0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-11081 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6844 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | liblastlog2-2 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libmount1 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-4214 | NONE0 | libpng16-16t64 1.6.48-1+deb13u5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | libsframe1 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20673 | NONE0 | libsframe1 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-9996 | NONE0 | libsframe1 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-11081 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6844 | NONE0 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libsmartcols1 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libuuid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31082 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-37454 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-2193 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-25740 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-52560 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56709 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58074 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58094 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58095 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21752 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21949 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22108 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22109 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22127 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23132 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23135 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37743 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37746 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37880 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38029 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38036 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38041 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38042 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38064 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38132 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38140 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38199 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38203 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38205 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38207 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38237 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38261 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38284 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38311 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38359 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38597 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38605 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38621 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39677 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39762 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39775 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39789 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39822 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39830 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39833 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39834 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39910 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39925 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39933 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40102 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68209 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68236 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68304 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68353 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68368 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68730 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71117 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71141 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71188 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71202 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71227 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71285 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71302 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71313 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71315 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23007 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23017 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23137 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23152 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23217 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23259 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23265 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23371 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23377 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23385 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23472 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31435 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31526 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31537 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31562 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31579 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31591 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31592 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31630 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31692 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31771 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31777 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43009 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43022 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43029 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43034 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43042 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43048 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43083 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43101 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43115 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43118 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43127 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43172 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43191 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43204 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43213 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43234 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43272 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43294 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43298 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43299 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43301 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43308 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43309 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43310 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43311 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43325 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43326 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43337 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43344 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43346 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43352 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43353 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43416 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43443 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43463 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43464 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43465 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43485 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45897 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45901 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45934 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45944 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45961 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45963 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46014 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46032 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46044 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46059 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46066 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46071 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46096 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46148 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46153 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46171 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46228 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46245 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46256 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46302 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46314 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52937 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52944 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52988 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52994 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53017 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53018 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53102 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53103 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53104 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53106 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53107 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53113 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53258 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53281 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53285 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53292 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53297 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53313 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53321 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53365 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53377 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63832 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63858 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64006 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64036 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64038 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64058 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64067 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64076 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64077 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64079 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64159 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64190 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64205 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64206 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64210 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64212 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64290 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64307 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64363 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64369 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64405 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64413 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64416 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64472 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64507 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64510 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64540 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64541 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64542 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64545 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64546 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64547 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64553 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64555 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2008-2544 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2011-4915 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2011-4916 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2011-4917 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9892 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9900 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-10723 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-8660 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2017-13693 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-13694 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12928 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12378 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12379 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12380 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12381 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12382 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12455 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-4543 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-31081 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31085 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40086 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68193 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68359 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53284 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63853 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63872 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63998 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63999 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64060 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64066 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64070 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64078 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64146 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64213 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64227 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64352 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64388 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64428 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64488 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64513 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64537 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64544 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-21232 | NONE0 | re2c 4.1-1 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-27171 | NONE0 | zlib1g 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-58055 | NONE0 | libnghttp2-14 1.64.0-1.1+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1147 | NONE0 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1147 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1147 | NONE0 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libblkid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libblkid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-1147 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1147 | NONE0 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1147 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | liblastlog2-2 2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | liblastlog2-2 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libmount1 2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libmount1 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12087 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-3713 | NONE0 | libpng16-16t64 1.6.48-1+deb13u5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1147 | NONE0 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libsmartcols1 2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libsmartcols1 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-66035 | NONE0 | libssh2-1t64 1.11.1-1+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31437 | NONE0 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31437 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libuuid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libuuid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64538 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12087 | NONE0 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12087 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12087 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-45440 | NONE0 | drupal/core 9.8.0 fixed in 10.3.6, 11.0.5, 10.2.9 | 9.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-45440 | NONE0 | drupal/core-recommended 9.8.0 fixed in 10.3.6, 11.0.5, 10.2.9 | 9.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-40217 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40338 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1176 | NONE0 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1176 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1176 | NONE0 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-42250 | NONE0 | libbz2-1.0 1.0.8-6 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-1176 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1176 | NONE0 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1176 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-11850 | NONE0 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11850 | NONE0 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11850 | NONE0 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11850 | NONE0 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-48959 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-48961 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-1176 | NONE0 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2004-0230 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 80.3% Actively Exploited | Not Applicable |
| CVE-2010-4563 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-48959 | NONE0 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-48961 | NONE0 | perl 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-48959 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-48961 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-48959 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-48961 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2007-3303 | NONE0 | apache2 2.4.68-1~deb13u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2007-3303 | NONE0 | apache2-bin 2.4.68-1~deb13u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2007-3303 | NONE0 | apache2-data 2.4.68-1~deb13u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2007-3303 | NONE0 | apache2-utils 2.4.68-1~deb13u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2005-3660 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2007-5686 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-8926 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-14017 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules-bin 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-runtime 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam0g 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libblkid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-10536 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-15224 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | liblastlog2-2 2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2017-14159 | NONE0 | libldap2 2.6.10+dfsg-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libmount1 2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libsmartcols1 2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libuuid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-20794 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-24864 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37906 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40139 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68745 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71074 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23348 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43053 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46017 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46272 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53108 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2017-0630 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-16230 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16234 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-15213 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-4010 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2012-4542 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68360 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2007-1743 | NONE0 | apache2 2.4.68-1~deb13u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2007-1743 | NONE0 | apache2-bin 2.4.68-1~deb13u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2007-1743 | NONE0 | apache2-data 2.4.68-1~deb13u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2007-1743 | NONE0 | apache2-utils 2.4.68-1~deb13u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2020-14304 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-17977 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2003-1307 | NONE0 | apache2 2.4.68-1~deb13u1 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2003-1580 | NONE0 | apache2 2.4.68-1~deb13u1 No fix yet | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2003-1307 | NONE0 | apache2-bin 2.4.68-1~deb13u1 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2003-1580 | NONE0 | apache2-bin 2.4.68-1~deb13u1 No fix yet | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2003-1307 | NONE0 | apache2-data 2.4.68-1~deb13u1 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2003-1580 | NONE0 | apache2-data 2.4.68-1~deb13u1 No fix yet | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2003-1307 | NONE0 | apache2-utils 2.4.68-1~deb13u1 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2003-1580 | NONE0 | apache2-utils 2.4.68-1~deb13u1 No fix yet | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2011-3389 | NONE0 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 73.3% Actively Exploited | Not Applicable |
| CVE-2021-45346 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2010-5321 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-15719 | NONE0 | libldap2 2.6.10+dfsg-1 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-41848 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-16089 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16229 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16231 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16232 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-16233 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2010-4756 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2010-4756 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2010-4756 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2010-4756 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2025-1152 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2011-3374 | NONE0 | libapt-pkg7.0 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-1152 | NONE0 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-56433 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-35501 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66861 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66862 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66861 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66862 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66861 | NONE0 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66862 | NONE0 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66861 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66862 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66861 | NONE0 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66862 | NONE0 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66861 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66862 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncursesw6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2011-4116 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-66861 | NONE0 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66862 | NONE0 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-70873 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2015-2877 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-68751 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-bin 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2011-4116 | NONE0 | perl 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2011-4116 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2011-4116 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-2903 | NONE0 | re2c 4.1-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-69644 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69644 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69644 | NONE0 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69644 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69644 | NONE0 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69644 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69644 | NONE0 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2003-1581 | NONE0 | apache2 2.4.68-1~deb13u1 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2008-0456 | NONE0 | apache2 2.4.68-1~deb13u1 No fix yet | 19.0% High Exploitation Risk | Not Applicable |
| CVE-2003-1581 | NONE0 | apache2-bin 2.4.68-1~deb13u1 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2008-0456 | NONE0 | apache2-bin 2.4.68-1~deb13u1 No fix yet | 19.0% High Exploitation Risk | Not Applicable |
| CVE-2003-1581 | NONE0 | apache2-data 2.4.68-1~deb13u1 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2008-0456 | NONE0 | apache2-data 2.4.68-1~deb13u1 No fix yet | 19.0% High Exploitation Risk | Not Applicable |
| CVE-2003-1581 | NONE0 | apache2-utils 2.4.68-1~deb13u1 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2008-0456 | NONE0 | apache2-utils 2.4.68-1~deb13u1 No fix yet | 19.0% High Exploitation Risk | Not Applicable |
| CVE-2025-40113 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-11191 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2001-1534 | NONE0 | apache2 2.4.68-1~deb13u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2001-1534 | NONE0 | apache2-bin 2.4.68-1~deb13u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2001-1534 | NONE0 | apache2-data 2.4.68-1~deb13u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2001-1534 | NONE0 | apache2-utils 2.4.68-1~deb13u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2007-3719 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.2.37-2+b9 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-8458 | NONE0 | curl 8.14.1-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53910 | NONE0 | diffutils 1:3.10-4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-57433 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-11822 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50812 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50813 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43263 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53010 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40098 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68174 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68318 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68376 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68735 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52983 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53368 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53401 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63805 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63811 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63819 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63825 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63857 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63859 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64082 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64154 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64361 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64371 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64389 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64390 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64400 | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64421 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64438 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64441 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64461 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64462 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64493 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64509 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64532 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64533 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64549 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64550 | NONE0 | linux-libc-dev 6.12.96-1 fixed in 6.12.100-1 | 0.1% Theoretical Threat | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.12.96-1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login.defs 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-57433 | NONE0 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| TEMP-0517018-A83CE6 | NONE0 | sysvinit-utils 3.14-4 No fix yet | — | Not Applicable |
| TEMP-0290435-0B57B5 | NONE0 | tar 1.35+dfsg-3.1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
| GHSA-f283-ghqc-fg79 | NONE0 | guzzlehttp/guzzle 7.14.2 fixed in 7.15.1 | — | Not Applicable |
| GHSA-h95v-h523-3mw8 | NONE0 | guzzlehttp/guzzle 7.14.2 fixed in 7.15.1 | — | Not Applicable |
| GHSA-wm3w-8rrp-j577 | NONE0 | guzzlehttp/guzzle 7.14.2 fixed in 7.15.1 | — | Not Applicable |
| CVE-2026-9082 | NONE0 | drupal/core 9.8.0 fixed in 10.4.10, 10.5.10, 10.6.9, 11.1.10, 11.2.12, 11.3.10 | 88.3% Actively Exploited | Not Applicable |
| CVE-2024-55637 | NONE0 | drupal/core 9.8.0 fixed in 10.2.11, 10.3.9, 11.0.8 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-55638 | NONE0 | drupal/core 9.8.0 fixed in 10.2.11, 10.3.9, 7.102 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-12393 | NONE0 | drupal/core 9.8.0 fixed in 10.2.11, 10.3.9, 11.0.8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-55634 | NONE0 | drupal/core 9.8.0 fixed in 10.2.11, 10.3.9, 11.0.8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-13081 | NONE0 | drupal/core 9.8.0 fixed in 10.4.9, 10.5.6, 11.1.9, 11.2.8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3057 | NONE0 | drupal/core 9.8.0 fixed in 10.3.13, 10.4.3, 11.0.12, 11.1.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-31673 | NONE0 | drupal/core 9.8.0 fixed in 10.3.13, 10.4.3, 11.0.12, 11.1.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-31674 | NONE0 | drupal/core 9.8.0 fixed in 10.3.13, 10.4.3, 11.0.12, 11.1.3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-6365 | NONE0 | drupal/core 9.8.0 fixed in 10.5.9, 10.6.7, 11.2.11, 11.3.7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6366 | NONE0 | drupal/core 9.8.0 fixed in 10.5.9, 10.6.7, 11.2.11, 11.3.7 | 0.4% Theoretical Threat | Not Applicable |
| GHSA-6ccv-8fgf-cjpw | NONE0 | drupal/core 9.8.0 fixed in 10.1.8, 10.2.2 | — | Not Applicable |
| CVE-2024-55636 | NONE0 | drupal/core 9.8.0 fixed in 10.2.11, 10.3.9, 11.0.8 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-13080 | NONE0 | drupal/core 9.8.0 fixed in 10.4.9, 10.5.6, 11.1.9, 11.2.8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-13082 | NONE0 | drupal/core 9.8.0 fixed in 10.4.9, 10.5.6, 11.1.9, 11.2.8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-13083 | NONE0 | drupal/core 9.8.0 fixed in 10.4.9, 10.5.6, 11.1.9, 11.2.8, 7.103 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-31675 | NONE0 | drupal/core 9.8.0 fixed in 10.3.14, 10.4.5, 11.0.13, 11.1.5 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-55637 | NONE0 | drupal/core-recommended 9.8.0 fixed in 10.2.11, 10.3.9, 11.0.8 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-55638 | NONE0 | drupal/core-recommended 9.8.0 fixed in 10.2.11, 10.3.9, 7.102 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-12393 | NONE0 | drupal/core-recommended 9.8.0 fixed in 10.2.11, 10.3.9, 11.0.8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-55634 | NONE0 | drupal/core-recommended 9.8.0 fixed in 10.2.11, 10.3.9, 11.0.8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-55636 | NONE0 | drupal/core-recommended 9.8.0 fixed in 10.2.11, 10.3.9, 11.0.8 | 0.9% Theoretical Threat | Not Applicable |
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.