This image is safe for production use. It is an official Docker Hub image, published by Docker Official, and pinned by digest, providing a high level of trust and immutability. While there are 117 identified vulnerabilities, none are directly exposed on the container's surface. The highest severity found among these post-exploit vulnerabilities is 4.5 (e.g., CVE-2026-5773 and CVE-2026-6276 in `curl`), which typically require an attacker to first gain access to the system. The overall threat score of 0 reflects its minimal immediate security risk for deployment.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-5773 | MEDIUM4.5 | curl 8.14.1-2+deb13u3 No fix yet | — | Post-Exploit |
| CVE-2026-6276 | MEDIUM4.5 | curl 8.14.1-2+deb13u3 No fix yet | — | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.9 | curl 8.14.1-2+deb13u3 No fix yet | — | Post-Exploit |
| CVE-2026-6429 | LOW3.9 | curl 8.14.1-2+deb13u3 No fix yet | — | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2005-2541 | LOW3.6 | tar 1.35+dfsg-3.1 No fix yet | 3.8% Low-Moderate Risk | Post-Exploit |
| CVE-2010-4651 | LOW3.48 | patch 2.8-2 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-20712 | LOW3.31 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3805 | LOW3.21 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW3.18 | curl 8.14.1-2+deb13u3 No fix yet | — | Post-Exploit |
| CVE-2026-6253 | LOW3.18 | curl 8.14.1-2+deb13u3 No fix yet | — | Post-Exploit |
| CVE-2026-7168 | LOW3.18 | curl 8.14.1-2+deb13u3 No fix yet | — | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-6951 | LOW3.1 | patch 2.8-2 No fix yet | 15.3% High Exploitation Risk | Post-Exploit |
| CVE-2018-6952 | LOW3.1 | patch 2.8-2 No fix yet | 11.8% High Exploitation Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.01 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-42250 | LOW3 | bzip2 1.0.8-6 No fix yet | — | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2018-20673 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-9996 | LOW2.8 | binutils 2.44-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% 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.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-45261 | LOW2.8 | patch 2.8-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.35+dfsg-3.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2008-1687 | LOW2.7 | m4 1.4.19-8 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2008-1688 | LOW2.7 | m4 1.4.19-8 No fix yet | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1: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.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-34743 | LOW2.7 | xz-utils 5.8.1-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.17.4-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 9.7-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl 8.14.1-2+deb13u3 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-2025-5278 | 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.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45232 | LOW2.22 | rsync 3.4.1+ds1-5+deb13u3 No fix yet | — | Post-Exploit |
| CVE-2024-56433 | LOW2.16 | passwd 1:4.17.4-2 No fix yet | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils 2.44-3 No fix yet | <0.1% 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.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils 2.44-3 No fix yet | <0.1% 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.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-34152 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 75.0% Actively Exploited | Not Applicable |
| CVE-2019-1010022 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-1010022 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-1010022 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-1010022 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-34152 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 75.0% Actively Exploited | Not Applicable |
| CVE-2023-34152 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 75.0% Actively Exploited | Not Applicable |
| CVE-2023-34152 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 75.0% Actively Exploited | Not Applicable |
| CVE-2026-42217 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | — | Not Applicable |
| CVE-2026-8376 | NONE0 | libperl5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7210 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-7210 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-20884 | NONE0 | libraw23t64 0.21.4-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-24450 | NONE0 | libraw23t64 0.21.4-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-24660 | NONE0 | libraw23t64 0.21.4-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-8376 | NONE0 | perl 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-8376 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-8376 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7210 | NONE0 | python3.13 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-7210 | NONE0 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| CVE-2009-3546 | NONE0 | libwmflite-0.2-7 0.2.13-1.1+b3 No fix yet | 4.7% Low-Moderate Risk | Not Applicable |
| CVE-2026-42216 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | — | Not Applicable |
| CVE-2026-42496 | NONE0 | libperl5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7598 | NONE0 | libssh2-1t64 1.11.1-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-42496 | NONE0 | perl 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-42496 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-42496 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-29004 | NONE0 | busybox-static 1:1.37.0-6+b8 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-32740 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-32740 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-32740 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-41142 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | — | Not Applicable |
| CVE-2016-9580 | NONE0 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-9581 | NONE0 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2018-16376 | NONE0 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2018-1000500 | NONE0 | busybox-static 1:1.37.0-6+b8 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-15079 | NONE0 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-41071 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-41071 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-41071 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2007-0086 | NONE0 | apache2 2.4.67-1~deb13u2 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2007-0086 | NONE0 | apache2-bin 2.4.67-1~deb13u2 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2007-0086 | NONE0 | apache2-data 2.4.67-1~deb13u2 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2007-0086 | NONE0 | apache2-utils 2.4.67-1~deb13u2 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-11082 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11082 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-39810 | NONE0 | busybox-static 1:1.37.0-6+b8 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11082 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11082 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11082 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1365 | NONE0 | libelf1t64 0.192-4 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1372 | NONE0 | libelf1t64 0.192-4 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-25210 | NONE0 | libexpat1 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11082 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncursesw6 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-12495 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-12839 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-12840 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27622 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-34588 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48962 | NONE0 | libperl5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2025-11082 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-8176 | NONE0 | libtiff6 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-8177 | NONE0 | libtiff6 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2013-7445 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-19449 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19814 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-3847 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-21803 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58093 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38137 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38187 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38206 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38421 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39859 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39862 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39958 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23208 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31493 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31688 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46274 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2019-12456 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2019-19378 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-11725 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2021-26934 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-25265 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-3238 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-26242 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-3640 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48962 | NONE0 | perl 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-48962 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-48962 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-49975 | NONE0 | apache2 2.4.67-1~deb13u2 fixed in 2.4.67-1~deb13u3 | — | Not Applicable |
| CVE-2026-49975 | NONE0 | apache2-bin 2.4.67-1~deb13u2 fixed in 2.4.67-1~deb13u3 | — | Not Applicable |
| CVE-2026-49975 | NONE0 | apache2-data 2.4.67-1~deb13u2 fixed in 2.4.67-1~deb13u3 | — | Not Applicable |
| CVE-2026-49975 | NONE0 | apache2-utils 2.4.67-1~deb13u2 fixed in 2.4.67-1~deb13u3 | — | Not Applicable |
| CVE-2025-66864 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66864 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66864 | NONE0 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2018-20796 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2018-20796 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2018-20796 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2018-20796 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-66864 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66864 | NONE0 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-5773 | NONE0 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-6276 | NONE0 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-33164 | NONE0 | libde265-0 1.0.15-1+b3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1352 | NONE0 | libelf1t64 0.192-4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45186 | NONE0 | libexpat1 2.7.1-2 No fix yet | — | Not Applicable |
| CVE-2025-66864 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2018-5709 | NONE0 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2020-36325 | NONE0 | libjansson4 2.14-2+b3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2018-5709 | NONE0 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-5709 | NONE0 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-5709 | NONE0 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2015-3276 | NONE0 | libldap-common 2.6.10+dfsg-1 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-17740 | NONE0 | libldap-common 2.6.10+dfsg-1 No fix yet | 6.1% Low-Moderate Risk | Not Applicable |
| CVE-2015-3276 | NONE0 | libldap2 2.6.10+dfsg-1 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-17740 | NONE0 | libldap2 2.6.10+dfsg-1 No fix yet | 6.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-64181 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-34543 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2016-9113 | NONE0 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-9114 | NONE0 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-42497 | NONE0 | libperl5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-9538 | NONE0 | libperl5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-20889 | NONE0 | libraw23t64 0.21.4-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-21413 | NONE0 | libraw23t64 0.21.4-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66864 | NONE0 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2017-16232 | NONE0 | libtiff6 4.7.0-3+deb13u2 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-19070 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2022-0400 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-42497 | NONE0 | perl 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-9538 | NONE0 | perl 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-42497 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-9538 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-42497 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-9538 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-34544 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-34545 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-61144 | NONE0 | libtiff6 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46244 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-3441 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3441 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3441 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3441 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3441 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3441 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68431 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-32741 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-32882 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2025-68431 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-32741 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-32882 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2025-68431 | NONE0 | libheif1 1.19.8-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-32741 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-32882 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-34379 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40244 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40250 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-15366 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-15367 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-15366 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-15367 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3441 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58015 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22104 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38204 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38636 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23102 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23327 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31568 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40064 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31613 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43414 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2008-4609 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2025-15366 | NONE0 | python3.13 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-15367 | NONE0 | python3.13 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-15366 | NONE0 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-15367 | NONE0 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-26157 | NONE0 | busybox-static 1:1.37.0-6+b8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-26158 | NONE0 | busybox-static 1:1.37.0-6+b8 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2021-3864 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31663 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43198 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-45932 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46054 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46117 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46181 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2025-40158 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40168 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43116 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43303 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-45840 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-45934 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46017 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46032 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46158 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46160 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46170 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46242 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46275 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2022-1247 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2022-2961 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2022-45884 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2022-45885 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71313 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-1965 | NONE0 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-14819 | NONE0 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22185 | NONE0 | libldap-common 2.6.10+dfsg-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22185 | NONE0 | libldap2 2.6.10+dfsg-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2007-3996 | NONE0 | libwmflite-0.2-7 0.2.13-1.1+b3 No fix yet | 15.1% High Exploitation Risk | Not Applicable |
| CVE-2025-40130 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2020-36694 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-6238 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2018-20712 | NONE0 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-32256 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2018-20712 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-32256 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2017-11754 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2017-11755 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-15607 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2018-20712 | NONE0 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-32256 | NONE0 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2018-18064 | NONE0 | libcairo2 1.18.4-1+b1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-20712 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-32256 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2018-20712 | NONE0 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-32256 | NONE0 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3784 | NONE0 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-5545 | NONE0 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-6429 | NONE0 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | — | Not Applicable |
| CVE-2025-14524 | NONE0 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2018-20712 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-32256 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-32738 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-32739 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-32814 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-32738 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-32739 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-32814 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-32738 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-32739 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-32814 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2017-9937 | NONE0 | libjbig0 2.1-6.1+b2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2017-11754 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2017-11755 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-15607 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2017-11754 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2017-11755 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-15607 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2017-11754 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2017-11755 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-15607 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-39329 | NONE0 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2016-10505 | NONE0 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2016-9115 | NONE0 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-9116 | NONE0 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2016-9117 | NONE0 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-6988 | NONE0 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-37769 | NONE0 | libpixman-1-0 0.44.0-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2018-20712 | NONE0 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-32256 | NONE0 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2018-10126 | NONE0 | libtiff6 4.7.0-3+deb13u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-1210 | NONE0 | libtiff6 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-6240 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68729 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-0564 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40074 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2022-44032 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2022-44033 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3805 | NONE0 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-3397 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-1757 | NONE0 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40146 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libblkid-dev 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libblkid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | liblastlog2-2 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libmount-dev 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libmount1 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libsmartcols1 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libuuid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40355 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68319 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43197 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2025-14104 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | uuid-dev 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1153 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1153 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1153 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1153 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1153 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-10966 | NONE0 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50219 | NONE0 | libexpat1 2.7.1-2 No fix yet | — | Not Applicable |
| CVE-2025-1153 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-26458 | NONE0 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-26458 | NONE0 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-26458 | NONE0 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-26458 | NONE0 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1153 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-13151 | NONE0 | libtasn1-6 4.20.0-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-0990 | NONE0 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2018-1121 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2021-3714 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3783 | NONE0 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-23039 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1178 | 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.1% Theoretical Threat | Not Applicable |
| CVE-2025-1178 | 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.1% Theoretical Threat | Not Applicable |
| CVE-2025-1178 | 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.1% Theoretical Threat | Not Applicable |
| CVE-2025-1178 | 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 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-20673 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2018-9996 | NONE0 | binutils-common 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-11081 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% 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 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-20673 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2018-9996 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-11081 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% 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-2023-42366 | NONE0 | busybox-static 1:1.37.0-6+b8 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2005-0406 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-7275 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-20673 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2018-9996 | NONE0 | libbinutils 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-11081 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% 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 | libblkid-dev 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libblkid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2017-7475 | NONE0 | libcairo2 1.18.4-1+b1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-20673 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2018-9996 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-11081 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% 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 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-20673 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2018-9996 | NONE0 | libctf0 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-11081 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6844 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1371 | NONE0 | libelf1t64 0.192-4 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1377 | NONE0 | libelf1t64 0.192-4 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66382 | NONE0 | libexpat1 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-32776 | NONE0 | libexpat1 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-32777 | NONE0 | libexpat1 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-32778 | NONE0 | libexpat1 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-20673 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2018-9996 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-11081 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% 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.1% Theoretical Threat | Not Applicable |
| CVE-2005-0406 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-7275 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2005-0406 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-7275 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2005-0406 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-7275 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libmount-dev 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libmount1 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-48074 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2017-14988 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-39328 | NONE0 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2021-4214 | NONE0 | libpng16-16t64 1.6.48-1+deb13u5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2020-24890 | NONE0 | libraw23t64 0.21.4-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-20673 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2018-9996 | NONE0 | libsframe1 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-11081 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% 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.1% Theoretical Threat | Not Applicable |
| CVE-2025-61143 | NONE0 | libtiff6 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libuuid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-31082 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-37454 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-2193 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-25740 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-52560 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-56709 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58074 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58094 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58095 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21752 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21807 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21949 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22108 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22109 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22127 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23131 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23132 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23135 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37743 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37746 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37880 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38029 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38036 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38041 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38042 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38064 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38132 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38140 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38199 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38203 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38205 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38207 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38237 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38261 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38284 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38311 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38359 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38597 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38605 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38621 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39677 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39762 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39775 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39789 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39822 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39830 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39833 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39834 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39910 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39925 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39933 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40102 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68209 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68236 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68304 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68353 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68368 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68730 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71117 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71141 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71188 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71202 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71227 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71285 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2025-71289 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2025-71302 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-23007 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23017 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23137 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23152 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23217 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23247 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23259 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23265 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23272 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23346 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23371 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23377 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23385 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23472 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31420 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31435 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31526 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31537 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31560 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31562 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31579 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31591 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31592 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31630 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31692 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31732 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31771 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31777 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43009 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43010 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43022 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43029 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43034 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43042 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43048 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43083 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43101 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43115 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43118 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43127 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43172 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43191 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43204 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43213 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43216 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43219 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43234 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43272 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43294 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43298 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43299 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43301 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43308 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43309 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43310 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43311 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43325 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43326 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43331 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43337 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43344 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43346 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43352 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43353 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43355 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43416 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43443 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43463 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43464 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43465 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-45838 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-45841 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-45842 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-45843 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-45844 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-45845 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-45846 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-45944 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46066 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46093 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46130 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46137 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46252 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2008-2544 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2011-4915 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2011-4916 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2011-4917 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2014-9892 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2014-9900 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2016-10723 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2016-8660 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2017-13693 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2017-13694 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2018-12928 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2019-12378 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-12379 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2019-12380 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2019-12381 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2019-12382 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-12455 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2022-4543 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31081 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-31085 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40086 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68193 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68251 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68359 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71315 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-31486 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45897 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-45901 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-45961 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-45963 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46014 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46059 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46071 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46092 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46153 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46203 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46216 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46256 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46279 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46302 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2022-0563 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2018-21232 | NONE0 | re2c 4.1-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | uuid-dev 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27171 | NONE0 | zlib1g 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27171 | NONE0 | zlib1g-dev 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-60876 | NONE0 | busybox-static 1:1.37.0-6+b8 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1147 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1147 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-55160 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1147 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libblkid-dev 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libblkid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-1147 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1147 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4873 | NONE0 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-6253 | NONE0 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-7168 | NONE0 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | — | Not Applicable |
| CVE-2025-59375 | NONE0 | libexpat1 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1147 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | liblastlog2-2 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-34743 | NONE0 | liblzma5 5.8.1-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-55160 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-55160 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-55160 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libmount-dev 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libmount1 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-34380 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | <0.1% 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-12781 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3276 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| CVE-2025-12781 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3276 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-5342 | NONE0 | libraw23t64 0.21.4-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1147 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libsmartcols1 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-31437 | NONE0 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-31437 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libuuid1 2.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.1% Theoretical Threat | Not Applicable |
| CVE-2025-12781 | NONE0 | python3.13 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3276 | NONE0 | python3.13 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| CVE-2025-12781 | NONE0 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3276 | NONE0 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-3184 | NONE0 | uuid-dev 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40217 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40338 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1176 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% 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.2% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% 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-2012-0039 | NONE0 | girepository-tools 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2008-3134 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2025-1176 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | libbinutils 2.44-3 No fix yet | 0.1% 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 | — | Not Applicable |
| CVE-2026-5450 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1176 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.1% 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.2% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33165 | NONE0 | libde265-0 1.0.15-1+b3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2012-0039 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2012-0039 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2012-0039 | NONE0 | libgirepository-2.0-0 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2012-0039 | NONE0 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2012-0039 | NONE0 | libglib2.0-bin 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2012-0039 | NONE0 | libglib2.0-data 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2012-0039 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2012-0039 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-1176 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2008-3134 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2008-3134 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2008-3134 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2026-34589 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1176 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-61145 | NONE0 | libtiff6 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2007-3477 | NONE0 | libwmflite-0.2-7 0.2.13-1.1+b3 No fix yet | 7.2% Low-Moderate Risk | Not Applicable |
| CVE-2004-0230 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 9.3% Low-Moderate Risk | Not Applicable |
| CVE-2010-4563 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2007-3303 | NONE0 | apache2 2.4.67-1~deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2007-3303 | NONE0 | apache2-bin 2.4.67-1~deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2007-3303 | NONE0 | apache2-data 2.4.67-1~deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2007-3303 | NONE0 | apache2-utils 2.4.67-1~deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2005-3660 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2007-5686 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-14017 | NONE0 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libblkid-dev 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libblkid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-15224 | NONE0 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1376 | NONE0 | libelf1t64 0.192-4 No fix yet | <0.1% 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 | libldap-common 2.6.10+dfsg-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2017-14159 | NONE0 | libldap2 2.6.10+dfsg-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libmount-dev 2.41-5 No fix yet | <0.1% 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.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-24864 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37906 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40139 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68745 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71074 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23348 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23394 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23469 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31456 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43053 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2017-0630 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-16230 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2019-16234 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% 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-2026-27456 | NONE0 | uuid-dev 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2019-15213 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-4010 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2012-4542 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-1502 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-1502 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68360 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-1502 | NONE0 | python3.13 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-1502 | NONE0 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2007-1743 | NONE0 | apache2 2.4.67-1~deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2007-1743 | NONE0 | apache2-bin 2.4.67-1~deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2007-1743 | NONE0 | apache2-data 2.4.67-1~deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2007-1743 | NONE0 | apache2-utils 2.4.67-1~deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-14304 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68768 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2018-17977 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2003-1307 | NONE0 | apache2 2.4.67-1~deb13u2 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2003-1580 | NONE0 | apache2 2.4.67-1~deb13u2 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2003-1307 | NONE0 | apache2-bin 2.4.67-1~deb13u2 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2003-1580 | NONE0 | apache2-bin 2.4.67-1~deb13u2 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2003-1307 | NONE0 | apache2-data 2.4.67-1~deb13u2 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2003-1580 | NONE0 | apache2-data 2.4.67-1~deb13u2 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2003-1307 | NONE0 | apache2-utils 2.4.67-1~deb13u2 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2003-1580 | NONE0 | apache2-utils 2.4.67-1~deb13u2 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2011-3389 | NONE0 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 3.9% Low-Moderate Risk | Not Applicable |
| CVE-2023-39327 | NONE0 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2021-45346 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2007-3476 | NONE0 | libwmflite-0.2-7 0.2.13-1.1+b3 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2010-5321 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2020-15719 | NONE0 | libldap-common 2.6.10+dfsg-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-15719 | NONE0 | libldap2 2.6.10+dfsg-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-41848 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2019-16089 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-16229 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2019-16231 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2019-16232 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2019-16233 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2010-4756 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2010-4756 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2010-4756 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2010-4756 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-25260 | NONE0 | libelf1t64 0.192-4 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2011-3374 | NONE0 | libapt-pkg7.0 3.0.3 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-1152 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-41080 | NONE0 | libexpat1 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-0989 | NONE0 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-56433 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 4.5% Low-Moderate Risk | Not Applicable |
| CVE-2020-35501 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% 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.1% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% 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.1% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-46394 | NONE0 | busybox-static 1:1.37.0-6+b8 No fix yet | <0.1% 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.1% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-50422 | NONE0 | libcairo2 1.18.4-1+b1 No fix yet | <0.1% 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.1% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% 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.1% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% 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.1% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3949 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3949 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3949 | NONE0 | libheif1 1.19.8-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncursesw6 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2011-4116 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3479 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3479 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | <0.1% 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.1% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-70873 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | libsystemd0 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | libsystemd0 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-8732 | NONE0 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2015-2877 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68751 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-bin 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2011-4116 | NONE0 | perl 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2011-4116 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2011-4116 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3479 | NONE0 | python3.13 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3479 | NONE0 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | <0.1% 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.1% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-0992 | NONE0 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | <0.1% 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.1% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | binutils-common 2.44-3 No fix yet | <0.1% 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.1% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% 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.1% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | libbinutils 2.44-3 No fix yet | <0.1% 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.1% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | <0.1% 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.1% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | libctf0 2.44-3 No fix yet | <0.1% 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.1% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | libgprofng0 2.44-3 No fix yet | <0.1% 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.1% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2003-1581 | NONE0 | apache2 2.4.67-1~deb13u2 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2008-0456 | NONE0 | apache2 2.4.67-1~deb13u2 No fix yet | 7.6% Low-Moderate Risk | Not Applicable |
| CVE-2003-1581 | NONE0 | apache2-bin 2.4.67-1~deb13u2 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2008-0456 | NONE0 | apache2-bin 2.4.67-1~deb13u2 No fix yet | 7.6% Low-Moderate Risk | Not Applicable |
| CVE-2003-1581 | NONE0 | apache2-data 2.4.67-1~deb13u2 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2008-0456 | NONE0 | apache2-data 2.4.67-1~deb13u2 No fix yet | 7.6% Low-Moderate Risk | Not Applicable |
| CVE-2003-1581 | NONE0 | apache2-utils 2.4.67-1~deb13u2 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2008-0456 | NONE0 | apache2-utils 2.4.67-1~deb13u2 No fix yet | 7.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-24515 | NONE0 | libexpat1 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-8534 | NONE0 | libtiff6 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40113 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2019-11191 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2001-1534 | NONE0 | apache2 2.4.67-1~deb13u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2001-1534 | NONE0 | apache2-bin 2.4.67-1~deb13u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2001-1534 | NONE0 | apache2-data 2.4.67-1~deb13u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2001-1534 | NONE0 | apache2-utils 2.4.67-1~deb13u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2007-3719 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-29167 | NONE0 | apache2 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-29170 | NONE0 | apache2 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-34355 | NONE0 | apache2 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-34356 | NONE0 | apache2 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-42535 | NONE0 | apache2 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-42536 | NONE0 | apache2 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-43951 | NONE0 | apache2 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-44119 | NONE0 | apache2 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-44185 | NONE0 | apache2 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-44186 | NONE0 | apache2 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-44631 | NONE0 | apache2 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-48913 | NONE0 | apache2 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-29167 | NONE0 | apache2-bin 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-29170 | NONE0 | apache2-bin 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-34355 | NONE0 | apache2-bin 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-34356 | NONE0 | apache2-bin 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-42535 | NONE0 | apache2-bin 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-42536 | NONE0 | apache2-bin 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-43951 | NONE0 | apache2-bin 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-44119 | NONE0 | apache2-bin 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-44185 | NONE0 | apache2-bin 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-44186 | NONE0 | apache2-bin 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-44631 | NONE0 | apache2-bin 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-48913 | NONE0 | apache2-bin 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-29167 | NONE0 | apache2-data 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-29170 | NONE0 | apache2-data 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-34355 | NONE0 | apache2-data 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-34356 | NONE0 | apache2-data 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-42535 | NONE0 | apache2-data 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-42536 | NONE0 | apache2-data 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-43951 | NONE0 | apache2-data 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-44119 | NONE0 | apache2-data 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-44185 | NONE0 | apache2-data 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-44186 | NONE0 | apache2-data 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-44631 | NONE0 | apache2-data 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-48913 | NONE0 | apache2-data 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-29167 | NONE0 | apache2-utils 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-29170 | NONE0 | apache2-utils 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-34355 | NONE0 | apache2-utils 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-34356 | NONE0 | apache2-utils 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-42535 | NONE0 | apache2-utils 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-42536 | NONE0 | apache2-utils 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-43951 | NONE0 | apache2-utils 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-44119 | NONE0 | apache2-utils 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-44185 | NONE0 | apache2-utils 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-44186 | NONE0 | apache2-utils 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-44631 | NONE0 | apache2-utils 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-48913 | NONE0 | apache2-utils 2.4.67-1~deb13u2 No fix yet | — | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.2.37-2+b9 No fix yet | — | Not Applicable |
| CVE-2024-58251 | NONE0 | busybox-static 1:1.37.0-6+b8 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-38949 | NONE0 | libde265-0 1.0.15-1+b3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-38950 | NONE0 | libde265-0 1.0.15-1+b3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-61147 | NONE0 | libde265-0 1.0.15-1+b3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50593 | NONE0 | libgraphite2-3 1.3.14-2+b1 No fix yet | — | Not Applicable |
| CVE-2026-41069 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-41069 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-41069 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2025-29070 | NONE0 | liblcms2-2 2.16-2+deb13u2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-48959 | NONE0 | libperl5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2025-15649 | NONE0 | libperl5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | libperl5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-48961 | NONE0 | libperl5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7774 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-9669 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-7774 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-9669 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-34180 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34181 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34182 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34183 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42764 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42766 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42767 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42768 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42769 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42770 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45445 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45446 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45447 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-7383 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-9076 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| TEMP-0601525-BEBB65 | NONE0 | libwmflite-0.2-7 0.2.13-1.1+b3 No fix yet | — | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40098 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68174 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68318 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68376 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68735 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31717 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43245 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43263 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43485 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-45839 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-45850 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-45930 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46044 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46096 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46148 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46171 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46228 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46245 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46272 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46314 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46315 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46316 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46317 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46319 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46320 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46321 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46322 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46323 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46325 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46330 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login.defs 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-34180 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34181 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34182 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34183 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42764 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42766 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42767 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42768 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42769 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42770 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45445 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45446 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45447 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-7383 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-9076 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34180 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34181 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34182 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34183 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42764 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42766 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42767 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42768 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42769 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42770 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45445 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45446 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45447 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-7383 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-9076 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-48959 | NONE0 | perl 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2025-15649 | NONE0 | perl 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-48961 | NONE0 | perl 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-48959 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2025-15649 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-48961 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-48959 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2025-15649 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-48961 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7774 | NONE0 | python3.13 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.13 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-9669 | NONE0 | python3.13 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-7774 | NONE0 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-9669 | NONE0 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | — | 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-44167 | NONE0 | phpseclib/phpseclib 2.0.53 fixed in 1.0.29, 2.0.54, 3.0.52 | — | Not Applicable |
| CVE-2026-45071 | NONE0 | symfony/dom-crawler v6.4.32 fixed in 6.2.0, 7.1.0, 4.0.0, 5.3.0, 5.4.0, 5.4.52, 7.2.0, 7.4.0, 6.3.0, 6.4.0, 6.4.40, 3.0.0, 5.1.0, 5.2.0, 6.1.0, 8.0.12, 5.0.0, 7.3.0, 7.4.12 | — | Not Applicable |
| CVE-2026-48736 | NONE0 | symfony/http-foundation v6.4.33 fixed in 7.2.0, 7.3.0, 7.4.0, 7.4.13, 8.0.13, 6.4.41, 7.1.0 | — | Not Applicable |
| CVE-2026-45068 | NONE0 | symfony/mailer v6.4.31 fixed in 6.4.0, 6.4.40, 4.0.0, 5.0.0, 5.1.0, 6.1.0, 7.4.0, 8.0.12, 5.3.0, 7.1.0, 7.3.0, 3.0.0, 5.4.0, 6.2.0, 7.2.0, 7.4.12, 5.2.0, 5.4.52, 6.3.0 | — | Not Applicable |
| CVE-2026-45067 | NONE0 | symfony/mime v6.4.32 fixed in 6.2.0, 7.3.0, 4.0.0, 6.1.0, 6.3.0, 7.1.0, 7.2.0, 7.4.0, 5.0.0, 5.2.0, 6.4.0, 7.4.12, 3.0.0, 5.1.0, 5.3.0, 5.4.52, 6.4.40, 8.0.12, 5.4.0 | — | Not Applicable |
| CVE-2026-45070 | NONE0 | symfony/mime v6.4.32 fixed in 5.0.0, 6.4.40, 5.1.0, 5.2.0, 5.3.0, 5.4.0, 6.4.0, 7.1.0, 7.3.0, 8.0.12, 3.0.0, 5.4.52, 6.1.0, 6.2.0, 6.3.0, 7.2.0, 7.4.0, 7.4.12, 4.0.0 | — | Not Applicable |
| CVE-2026-46644 | NONE0 | symfony/polyfill-intl-idn v1.32.0 fixed in 1.38.1 | — | Not Applicable |
| CVE-2026-45065 | NONE0 | symfony/routing v6.4.32 fixed in 7.1.0, 3.0.0, 5.1.0, 5.3.0, 6.2.0, 6.3.0, 7.2.0, 7.3.0, 7.4.12, 4.0.0, 6.4.0, 6.4.40, 7.4.0, 8.0.12, 5.0.0, 5.4.0, 5.4.52, 5.2.0, 6.1.0 | — | Not Applicable |
| CVE-2026-48784 | NONE0 | symfony/routing v6.4.32 fixed in 5.4.53, 6.1.0, 5.1.0, 6.4.0, 6.3.0, 7.2.0, 7.4.0, 7.4.13, 5.4.0, 4.0.0, 6.2.0, 7.3.0, 8.0.13, 6.4.41, 7.1.0, 3.0.0, 5.0.0, 5.2.0, 5.3.0 | — | Not Applicable |