Last scanned:
This base/runtime image is a clean foundation for building production images. It has no exposed vulnerabilities and only low-severity post-exploit findings that pose minimal risk in typical deployment scenarios. The image is officially published and immutable, ensuring integrity. All 177 post-exploit-only vulnerabilities have severity below 5.0, making them unlikely to be exploited in a real-world attack. Note: this is a general-purpose base/runtime image — many findings live in components that an application built on top may never load, so actual exploitability depends on the final image. For an accurate risk picture, re-scan the final application image with context.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-8286 | MEDIUM4.13 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2018-20712 | LOW3.9 | binutils 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-11856 | LOW3.9 | curl 7.88.1-10+deb12u15 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2008-3234 | LOW3.9 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2024-10524 | LOW3.9 | wget 1.21.3-1+deb12u1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0840 | LOW3.82 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW3.82 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | curl 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | curl 7.88.1-10+deb12u15 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW3.82 | gzip 1.12-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59999 | LOW3.82 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-60000 | LOW3.82 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2021-31879 | LOW3.66 | wget 1.21.3-1+deb12u1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-58471 | LOW3.62 | wget 1.21.3-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-58472 | LOW3.62 | wget 1.21.3-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2005-2541 | LOW3.6 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2020-14145 | LOW3.54 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2010-4651 | LOW3.48 | patch 2.7.6-7 No fix yet | 4.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53589 | LOW3.37 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils 2.40-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2016-2781 | LOW3.31 | coreutils 9.1-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-59998 | LOW3.31 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-60001 | LOW3.31 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2379 | LOW3.24 | curl 7.88.1-10+deb12u15 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2016-20012 | LOW3.18 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 5.3% Low-Moderate Risk | Post-Exploit |
| CVE-2018-15919 | LOW3.18 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 3.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2020-15778 | LOW3.07 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 13.0% High Exploitation Risk | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-15146 | LOW3.01 | wget 1.21.3-1+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-1000021 | LOW3 | git 1:2.39.5-0+deb12u3 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2007-2243 | LOW3 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-60002 | LOW2.87 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils 2.40-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2019-6110 | LOW2.81 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 20.9% High Exploitation Risk | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-45261 | LOW2.8 | patch 2.7.6-7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-56288 | LOW2.8 | patch 2.7.6-7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56289 | LOW2.8 | patch 2.7.6-7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-59995 | LOW2.75 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59996 | LOW2.75 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59997 | LOW2.75 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-24975 | LOW2.7 | git 1:2.39.5-0+deb12u3 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2008-1687 | LOW2.7 | m4 1.4.19-3 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2008-1688 | LOW2.7 | m4 1.4.19-3 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6951 | LOW2.7 | patch 2.7.6-7 No fix yet | 8.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6952 | LOW2.7 | patch 2.7.6-7 No fix yet | 8.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | curl 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | mount 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42767 | LOW2.7 | openssl 3.0.20-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58470 | LOW2.7 | wget 1.21.3-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-52005 | LOW2.69 | git 1:2.39.5-0+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2007-2768 | LOW2.58 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 8.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-42250 | LOW2.55 | bzip2 1.0.8-5+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | curl 7.88.1-10+deb12u15 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 9.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | curl 7.88.1-10+deb12u15 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | dirmngr 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | dirmngr 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gnupg 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gnupg 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg-agent 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg-agent 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgconf 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgconf 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgsm 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgsm 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.12-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-0725 | LOW2.4 | curl 7.88.1-10+deb12u15 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils 9.1-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | dirmngr 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gnupg 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg-agent 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgconf 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgsm 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-4217 | LOW1.68 | unzip 6.0-28 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | dirmngr 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gnupg 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gpg 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gpg-agent 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gpgconf 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gpgsm 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-34152 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-34152 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-34152 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-6879 | NONE0 | libaom3 3.6.0-1+deb12u2 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2016-1585 | NONE0 | libapparmor1 3.0.8-3 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010022 | NONE0 | libc-bin 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010022 | NONE0 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010022 | NONE0 | libc6 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010022 | NONE0 | libc6-dev 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-34152 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-34152 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-34152 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-34152 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-34152 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-34152 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-34152 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-34152 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-34152 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-34152 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-42217 | NONE0 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42217 | NONE0 | libopenexr-dev 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8376 | NONE0 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6653 | NONE0 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6653 | NONE0 | libxml2-dev 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8376 | NONE0 | perl 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8376 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8376 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45853 | NONE0 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2023-45853 | NONE0 | zlib1g-dev 1:1.2.13.dfsg-1 No fix yet | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2009-3546 | NONE0 | libwmf-0.2-7 0.2.12-5.1 No fix yet | 10.2% High Exploitation Risk | Not Applicable |
| CVE-2009-3546 | NONE0 | libwmf-dev 0.2.12-5.1 No fix yet | 10.2% High Exploitation Risk | Not Applicable |
| CVE-2009-3546 | NONE0 | libwmflite-0.2-7 0.2.12-5.1 No fix yet | 10.2% High Exploitation Risk | Not Applicable |
| CVE-2026-46470 | NONE0 | gstreamer1.0-plugins-good 1.22.0-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56372 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-56372 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-56372 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-58016 | NONE0 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58016 | NONE0 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58016 | NONE0 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58016 | NONE0 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58016 | NONE0 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56372 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-56372 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-56372 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-56372 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-56372 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-56372 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-56372 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-56372 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-56372 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-56372 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2023-5841 | NONE0 | libopenexr-3-1-30 3.1.5-5 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-42216 | NONE0 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-5841 | NONE0 | libopenexr-dev 3.1.5-5 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-42216 | NONE0 | libopenexr-dev 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13221 | NONE0 | libperl5.36 5.36.0-7+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-42496 | NONE0 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-2369 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-2369 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-7458 | NONE0 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-7458 | NONE0 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7598 | NONE0 | libssh2-1 1.10.0-3+b1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-13221 | NONE0 | perl 5.36.0-7+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-42496 | NONE0 | perl 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13221 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-42496 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13221 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-42496 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-32911 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-32911 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-52005 | NONE0 | git-man 1:2.39.5-0+deb12u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-3083 | NONE0 | gstreamer1.0-plugins-good 1.22.0-5+deb12u3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-3085 | NONE0 | gstreamer1.0-plugins-good 1.22.0-5+deb12u3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc-bin 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc6 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc6-dev 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2014-8166 | NONE0 | libcups2 2.4.2-3+deb12u9 No fix yet | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2026-32740 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-49463 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-4367 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 72.6% Actively Exploited | Not Applicable |
| CVE-2026-20664 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-28857 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-28859 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43705 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43715 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43731 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-41142 | NONE0 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-41142 | NONE0 | libopenexr-dev 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-9580 | NONE0 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2016-9581 | NONE0 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2018-16376 | NONE0 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2016-9580 | NONE0 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2016-9581 | NONE0 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2018-16376 | NONE0 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2024-4367 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 72.6% Actively Exploited | Not Applicable |
| CVE-2026-20664 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-28857 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-28859 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43705 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43715 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43731 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-0719 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-1761 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-0719 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-1761 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-57432 | NONE0 | libperl5.36 5.36.0-7+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-57432 | NONE0 | perl 5.36.0-7+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-57432 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-57432 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-55200 | NONE0 | libssh2-1 1.10.0-3+b1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-37555 | NONE0 | libsndfile1 1.2.0-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-14523 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-2436 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5119 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-14523 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-2436 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5119 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-39191 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8286 | NONE0 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-15079 | NONE0 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8286 | NONE0 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-15079 | NONE0 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8286 | NONE0 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-15079 | NONE0 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-41071 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31486 | NONE0 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2023-31486 | NONE0 | perl 5.36.0-7+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2023-31486 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2023-31486 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2025-11082 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11082 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11082 | NONE0 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11082 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11082 | NONE0 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1365 | NONE0 | libdw1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-1372 | NONE0 | libdw1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-1365 | NONE0 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-1372 | NONE0 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25210 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-25210 | NONE0 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11082 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncurses-dev 6.4-4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncurses5-dev 6.4-4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncurses6 6.4-4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncursesw5-dev 6.4-4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncursesw6 6.4-4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-1013 | NONE0 | libodbc1 2.3.11-2+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-1013 | NONE0 | libodbc2 2.3.11-2+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-1013 | NONE0 | libodbccr2 2.3.11-2+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12495 | NONE0 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-12839 | NONE0 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-12840 | NONE0 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-27622 | NONE0 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-34588 | NONE0 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-12495 | NONE0 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-12839 | NONE0 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-12840 | NONE0 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-27622 | NONE0 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-34588 | NONE0 | libopenexr-dev 3.1.5-5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-48962 | NONE0 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-8176 | NONE0 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8177 | NONE0 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-8176 | NONE0 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8177 | NONE0 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-8176 | NONE0 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8177 | NONE0 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.4-4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-11979 | NONE0 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-11979 | NONE0 | libxml2-dev 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2013-7445 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-19449 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-19814 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-3847 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-52452 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52624 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52751 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53218 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-21803 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-26836 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26913 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26914 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26944 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35887 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38570 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38630 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41045 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42118 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44941 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44942 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44951 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46729 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46811 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46813 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47691 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50029 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50217 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50226 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50282 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53068 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53168 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53179 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53218 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56538 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56775 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57900 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21927 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21967 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21969 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23133 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37750 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37777 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37861 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37952 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37957 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38069 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38117 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38182 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38206 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38248 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38369 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38582 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38585 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38595 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38722 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38734 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39797 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39810 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39859 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39952 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71068 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71073 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71152 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23171 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23208 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23226 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23361 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23447 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23448 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31493 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31527 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31729 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43049 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43250 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46068 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46219 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46241 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53129 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53143 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53156 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53157 | NONE0 | linux-libc-dev 6.1.176-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53262 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53272 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53359 | NONE0 | linux-libc-dev 6.1.176-1 fixed in 6.1.177-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53362 | NONE0 | linux-libc-dev 6.1.176-1 fixed in 6.1.177-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46274 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-12456 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19378 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-11725 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-26934 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-25265 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-3238 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-26242 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-3640 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.4-4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.4-4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-48962 | NONE0 | perl 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-48962 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-48962 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53705 | NONE0 | gstreamer1.0-plugins-good 1.22.0-5+deb12u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56208 | NONE0 | libaom3 3.6.0-1+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-0840 | NONE0 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1179 | NONE0 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-66864 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | binutils-common 2.40-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-0840 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1179 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-66864 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-24975 | NONE0 | git-man 1:2.39.5-0+deb12u3 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-1940 | NONE0 | gstreamer1.0-plugins-good 1.22.0-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61857 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61861 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61863 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61866 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61870 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61857 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61861 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61863 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61866 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61870 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61857 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61861 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61863 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61866 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61870 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2018-5709 | NONE0 | krb5-multidev 1.20.1-2+deb12u5 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-39616 | NONE0 | libaom3 3.6.0-1+deb12u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-0840 | NONE0 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1179 | NONE0 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-66864 | NONE0 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | libbinutils 2.40-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-20796 | NONE0 | libc-bin 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc-bin 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20796 | NONE0 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20796 | NONE0 | libc6 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc6 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20796 | NONE0 | libc6-dev 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc6-dev 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2025-0840 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1179 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-66864 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-0840 | NONE0 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1179 | NONE0 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-66864 | NONE0 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | libctf0 2.40-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-34980 | NONE0 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12064 | NONE0 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6276 | NONE0 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8927 | NONE0 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-8932 | NONE0 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12064 | NONE0 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6276 | NONE0 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8927 | NONE0 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-8932 | NONE0 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12064 | NONE0 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6276 | NONE0 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8927 | NONE0 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-8932 | NONE0 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-33164 | NONE0 | libde265-0 1.0.11-1+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-1352 | NONE0 | libdw1 0.188-2.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1352 | NONE0 | libelf1 0.188-2.1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-45186 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-28757 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-45186 | NONE0 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-28757 | NONE0 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2018-6829 | NONE0 | libgcrypt20 1.10.1-3+deb12u1 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2026-58011 | NONE0 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58011 | NONE0 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58011 | NONE0 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58011 | NONE0 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58011 | NONE0 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-0840 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1179 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-66864 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-5709 | NONE0 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-5709 | NONE0 | libgssrpc4 1.20.1-2+deb12u5 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-25193 | NONE0 | libharfbuzz-icu0 6.0.0+dfsg-3 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2023-25193 | NONE0 | libharfbuzz0b 6.0.0+dfsg-3 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2012-2663 | NONE0 | libip4tc2 1.8.9-2 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2018-5709 | NONE0 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-5709 | NONE0 | libkadm5clnt-mit12 1.20.1-2+deb12u5 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-5709 | NONE0 | libkadm5srv-mit12 1.20.1-2+deb12u5 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-5709 | NONE0 | libkdb5-10 1.20.1-2+deb12u5 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-5709 | NONE0 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-5709 | NONE0 | libkrb5-dev 1.20.1-2+deb12u5 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-5709 | NONE0 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-2953 | NONE0 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2015-3276 | NONE0 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 5.3% Low-Moderate Risk | Not Applicable |
| CVE-2017-17740 | NONE0 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 7.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-61857 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61861 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61863 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61866 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61870 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61857 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61861 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61863 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61866 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61870 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61857 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61861 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61863 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61866 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61870 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61857 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61861 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61863 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61866 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61870 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61857 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61861 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61863 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61866 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61870 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61857 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61861 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61863 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61866 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61870 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61857 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61861 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61863 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61866 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61870 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61857 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61861 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61863 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61866 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61870 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61857 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61861 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61863 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61866 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61870 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61857 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61861 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61863 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61866 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61870 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2025-64181 | NONE0 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-34543 | NONE0 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-64181 | NONE0 | libopenexr-dev 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-34543 | NONE0 | libopenexr-dev 3.1.5-5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-9113 | NONE0 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2016-9114 | NONE0 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2016-9113 | NONE0 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2016-9114 | NONE0 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-42497 | NONE0 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9538 | NONE0 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69534 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-3644 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7210 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-69534 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-3644 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7210 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-32906 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-32913 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-4948 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-4271 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-32049 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-32906 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-32913 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-4948 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-4271 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-32049 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-55199 | NONE0 | libssh2-1 1.10.0-3+b1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52355 | NONE0 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-16232 | NONE0 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 4.8% Low-Moderate Risk | Not Applicable |
| CVE-2023-52355 | NONE0 | libtiff6 4.5.0-6+deb12u4 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-16232 | NONE0 | libtiff6 4.5.0-6+deb12u4 No fix yet | 4.8% Low-Moderate Risk | Not Applicable |
| CVE-2023-52355 | NONE0 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-16232 | NONE0 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 4.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-19070 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-0400 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-42497 | NONE0 | perl 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9538 | NONE0 | perl 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42497 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9538 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42497 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9538 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69534 | NONE0 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-3644 | NONE0 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7210 | NONE0 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-69534 | NONE0 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-3644 | NONE0 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7210 | NONE0 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-9547 | NONE0 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-9547 | NONE0 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-9547 | NONE0 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-32914 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-32914 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-40170 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-34544 | NONE0 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-34545 | NONE0 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-34544 | NONE0 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-34545 | NONE0 | libopenexr-dev 3.1.5-5 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-3099 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-3099 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12912 | NONE0 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-61144 | NONE0 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-12912 | NONE0 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-61144 | NONE0 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-12912 | NONE0 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-61144 | NONE0 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-53781 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39981 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43248 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3441 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3441 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-54369 | NONE0 | libacl1 2.3.1-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56209 | NONE0 | libaom3 3.6.0-1+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56210 | NONE0 | libaom3 3.6.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56211 | NONE0 | libaom3 3.6.0-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-3441 | NONE0 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3441 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3441 | NONE0 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3441 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68431 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-32741 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-32882 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43701 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43725 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34379 | NONE0 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-40244 | NONE0 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-40250 | NONE0 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-34379 | NONE0 | libopenexr-dev 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-40244 | NONE0 | libopenexr-dev 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-40250 | NONE0 | libopenexr-dev 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15366 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15367 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-15366 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15367 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-5673 | NONE0 | libtheora0 1.1.1+dfsg.1-16.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43701 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43725 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26669 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41935 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53147 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57982 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21985 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22039 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22104 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38081 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38204 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38616 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38636 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39744 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39901 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23327 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31568 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45893 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45943 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45957 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46130 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46293 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53138 | NONE0 | linux-libc-dev 6.1.176-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53179 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-25742 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-25743 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36013 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-53216 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40064 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68183 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68324 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43126 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43414 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46135 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2008-4609 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 32.1% High Exploitation Risk | Not Applicable |
| CVE-2025-15366 | NONE0 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15367 | NONE0 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-15366 | NONE0 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15367 | NONE0 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-3864 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-52586 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42162 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37776 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23191 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31419 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31663 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43125 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43198 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46054 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46181 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52991 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53000 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53091 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53762 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57984 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40158 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40168 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40328 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23050 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45859 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-45894 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45942 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46090 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46266 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46330 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52956 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53005 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53009 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53053 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53078 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53089 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53132 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53185 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53224 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53230 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53246 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53361 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53366 | NONE0 | linux-libc-dev 6.1.176-1 fixed in 6.1.177-1 | — | Not Applicable |
| CVE-2022-1247 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2961 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45884 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45885 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56132 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56403 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56404 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56405 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56406 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56410 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56411 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56132 | NONE0 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56403 | NONE0 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56404 | NONE0 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56405 | NONE0 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56406 | NONE0 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56410 | NONE0 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56411 | NONE0 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-1965 | NONE0 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-1965 | NONE0 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-1965 | NONE0 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-22185 | NONE0 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-46421 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-46421 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2007-3996 | NONE0 | libwmf-0.2-7 0.2.12-5.1 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2007-3996 | NONE0 | libwmf-dev 0.2.12-5.1 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2007-3996 | NONE0 | libwmflite-0.2-7 0.2.12-5.1 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-61915 | NONE0 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-40897 | NONE0 | liborc-0.4-0 1:0.4.33-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-36694 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-21264 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53095 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57795 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21714 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53589 | NONE0 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53589 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53589 | NONE0 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53589 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53589 | NONE0 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53589 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21759 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 7.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-53267 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2018-20712 | NONE0 | binutils-common 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-32256 | NONE0 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-1972 | NONE0 | binutils-common 2.40-2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2018-20712 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-32256 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-1972 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-61465 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2017-11754 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-61465 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2017-11754 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-61465 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2017-11754 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-68468 | NONE0 | libavahi-client3 0.8-10+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68471 | NONE0 | libavahi-client3 0.8-10+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-24401 | NONE0 | libavahi-client3 0.8-10+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68468 | NONE0 | libavahi-common-data 0.8-10+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68471 | NONE0 | libavahi-common-data 0.8-10+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-24401 | NONE0 | libavahi-common-data 0.8-10+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68468 | NONE0 | libavahi-common3 0.8-10+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68471 | NONE0 | libavahi-common3 0.8-10+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-24401 | NONE0 | libavahi-common3 0.8-10+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2018-20712 | NONE0 | libbinutils 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-32256 | NONE0 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-1972 | NONE0 | libbinutils 2.40-2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc6 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-0856 | NONE0 | libcaca0 0.99.beta20-3+deb12u1 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2018-18064 | NONE0 | libcairo-gobject2 1.16.0-7 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2019-6461 | NONE0 | libcairo-gobject2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-6462 | NONE0 | libcairo-gobject2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-18064 | NONE0 | libcairo-script-interpreter2 1.16.0-7 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2019-6461 | NONE0 | libcairo-script-interpreter2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-6462 | NONE0 | libcairo-script-interpreter2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-18064 | NONE0 | libcairo2 1.16.0-7 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2019-6461 | NONE0 | libcairo2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-6462 | NONE0 | libcairo2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-18064 | NONE0 | libcairo2-dev 1.16.0-7 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2019-6461 | NONE0 | libcairo2-dev 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-6462 | NONE0 | libcairo2-dev 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-20712 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-32256 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-1972 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2018-20712 | NONE0 | libctf0 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-32256 | NONE0 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-1972 | NONE0 | libctf0 2.40-2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-34978 | NONE0 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-11856 | NONE0 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-5545 | NONE0 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6429 | NONE0 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8924 | NONE0 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-11856 | NONE0 | libcurl4 7.88.1-10+deb12u15 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-5545 | NONE0 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6429 | NONE0 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8924 | NONE0 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-11856 | NONE0 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-5545 | NONE0 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6429 | NONE0 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8924 | NONE0 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2018-20712 | NONE0 | libgprofng0 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-32256 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-1972 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-32738 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-32739 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-32814 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-49271 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-46299 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39872 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43663 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43676 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43699 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43707 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43712 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43713 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43716 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43720 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43721 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43726 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43727 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43732 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43734 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43740 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43742 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43745 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2017-9937 | NONE0 | libjbig-dev 2.1-6.1 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2017-9937 | NONE0 | libjbig0 2.1-6.1 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2026-61465 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2017-11754 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-61465 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2017-11754 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-61465 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2017-11754 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-61465 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2017-11754 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-61465 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2017-11754 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-61465 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2017-11754 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-61465 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2017-11754 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-61465 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2017-11754 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-61465 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2017-11754 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-61465 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2017-11754 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | libncurses-dev 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libncurses5-dev 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libncurses6 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libncursesw5-dev 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libncursesw6 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-39329 | NONE0 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2016-10505 | NONE0 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2016-9115 | NONE0 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2016-9116 | NONE0 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2016-9117 | NONE0 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-6988 | NONE0 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2023-39329 | NONE0 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2016-10505 | NONE0 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2016-9115 | NONE0 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2016-9116 | NONE0 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2016-9117 | NONE0 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-6988 | NONE0 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2025-15649 | NONE0 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-37769 | NONE0 | libpixman-1-0 0.42.2-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-37769 | NONE0 | libpixman-1-dev 0.42.2-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-11972 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-11972 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-50613 | NONE0 | libsndfile1 1.2.0-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-2784 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-32052 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-32053 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-32910 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-32912 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-46420 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-4969 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-1801 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-3633 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3634 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-2784 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-32052 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-32053 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-32910 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-32912 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-46420 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-4969 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-1801 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-3633 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3634 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-15661 | NONE0 | libssh2-1 1.10.0-3+b1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6277 | NONE0 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2018-10126 | NONE0 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-1210 | NONE0 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2023-6277 | NONE0 | libtiff6 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2018-10126 | NONE0 | libtiff6 4.5.0-6+deb12u4 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-1210 | NONE0 | libtiff6 4.5.0-6+deb12u4 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2023-6277 | NONE0 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2018-10126 | NONE0 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-1210 | NONE0 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | libtinfo6 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2025-46299 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39872 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43663 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43676 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43699 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43707 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43712 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43713 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43716 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43720 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43721 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43726 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43727 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43732 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43734 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43740 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43742 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43745 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6240 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-36968 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43239 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-0564 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-bin 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2025-15649 | NONE0 | perl 5.36.0-7+deb12u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-15649 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-15649 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-11972 | NONE0 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-11972 | NONE0 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40074 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23383 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31502 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31516 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53090 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-44032 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44033 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44034 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54370 | NONE0 | libacl1 2.3.1-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-54371 | NONE0 | libattr1 1:2.5.1-4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27447 | NONE0 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-3397 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40307 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40918 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39314 | NONE0 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-39316 | NONE0 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-13757 | NONE0 | libp11-kit0 0.24.1-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-28162 | NONE0 | libpng-dev 1.6.39-2+deb12u5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-28162 | NONE0 | libpng16-16 1.6.39-2+deb12u5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40146 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libfdisk1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6019 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6019 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-1916 | NONE0 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-1916 | NONE0 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-1916 | NONE0 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40071 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40355 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68342 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68736 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31505 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6019 | NONE0 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6019 | NONE0 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1153 | NONE0 | binutils-common 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-1153 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-26458 | NONE0 | krb5-multidev 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | krb5-multidev 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-1153 | NONE0 | libbinutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-5435 | NONE0 | libc-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | libc6 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1153 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-1153 | NONE0 | libctf0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-10966 | NONE0 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-10966 | NONE0 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-10966 | NONE0 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-32570 | NONE0 | libdav1d6 1.0.0-2+deb12u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-50219 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56412 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50219 | NONE0 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56412 | NONE0 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-2236 | NONE0 | libgcrypt20 1.10.1-3+deb12u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-1153 | NONE0 | libgprofng0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-26458 | NONE0 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-26458 | NONE0 | libgssrpc4 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libgssrpc4 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-26458 | NONE0 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-26458 | NONE0 | libkadm5clnt-mit12 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libkadm5clnt-mit12 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-26458 | NONE0 | libkadm5srv-mit12 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libkadm5srv-mit12 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-26458 | NONE0 | libkdb5-10 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libkdb5-10 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-26458 | NONE0 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-26458 | NONE0 | libkrb5-dev 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libkrb5-dev 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-26458 | NONE0 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-9669 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9669 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-32050 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-9901 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-32050 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-9901 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-13151 | NONE0 | libtasn1-6 4.19.0-2+deb12u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-1121 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-3714 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-9669 | NONE0 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9669 | NONE0 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-1539 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-1539 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53706 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54107 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54141 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23239 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23240 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-49569 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-23039 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1178 | NONE0 | binutils-common 2.40-2 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-1178 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-47183 | NONE0 | gstreamer1.0-plugins-good 1.22.0-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1178 | NONE0 | libbinutils 2.40-2 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-1178 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-1178 | NONE0 | libctf0 2.40-2 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-1178 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | binutils-common 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20673 | NONE0 | binutils-common 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-9996 | NONE0 | binutils-common 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-11081 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8224 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6844 | NONE0 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20673 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-9996 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-11081 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8224 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6844 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-27943 | NONE0 | cpp-12 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-27943 | NONE0 | g++-12 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-27943 | NONE0 | gcc-12 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-27943 | NONE0 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-46469 | NONE0 | gstreamer1.0-plugins-good 1.22.0-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2005-0406 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2005-0406 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2005-0406 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-27943 | NONE0 | libasan8 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-27943 | NONE0 | libatomic1 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-59529 | NONE0 | libavahi-client3 0.8-10+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68276 | NONE0 | libavahi-client3 0.8-10+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-34933 | NONE0 | libavahi-client3 0.8-10+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-59529 | NONE0 | libavahi-common-data 0.8-10+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68276 | NONE0 | libavahi-common-data 0.8-10+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-34933 | NONE0 | libavahi-common-data 0.8-10+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-59529 | NONE0 | libavahi-common3 0.8-10+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68276 | NONE0 | libavahi-common3 0.8-10+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-34933 | NONE0 | libavahi-common3 0.8-10+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | libbinutils 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20673 | NONE0 | libbinutils 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-9996 | NONE0 | libbinutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-11081 | NONE0 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8224 | NONE0 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6844 | NONE0 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-7475 | NONE0 | libcairo-gobject2 1.16.0-7 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2017-7475 | NONE0 | libcairo-script-interpreter2 1.16.0-7 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2017-7475 | NONE0 | libcairo2 1.16.0-7 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2017-7475 | NONE0 | libcairo2-dev 1.16.0-7 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-27943 | NONE0 | libcc1-0 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20673 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-9996 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-11081 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8224 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6844 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | libctf0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20673 | NONE0 | libctf0 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-9996 | NONE0 | libctf0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-11081 | NONE0 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8224 | NONE0 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6844 | NONE0 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-58436 | NONE0 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1371 | NONE0 | libdw1 0.188-2.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1377 | NONE0 | libdw1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-1371 | NONE0 | libelf1 0.188-2.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1377 | NONE0 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66382 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-32776 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-32777 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-32778 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-52426 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-66382 | NONE0 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-32776 | NONE0 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-32777 | NONE0 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-32778 | NONE0 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-52426 | NONE0 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libfdisk1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-27943 | NONE0 | libgcc-12-dev 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-27943 | NONE0 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-27943 | NONE0 | libgomp1 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | libgprofng0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20673 | NONE0 | libgprofng0 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-9996 | NONE0 | libgprofng0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-11081 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8224 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6844 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-27943 | NONE0 | libitm1 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-26924 | NONE0 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-29932 | NONE0 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-29933 | NONE0 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-29934 | NONE0 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-29935 | NONE0 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-29939 | NONE0 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-29941 | NONE0 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-29942 | NONE0 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-27943 | NONE0 | liblsan0 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2005-0406 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2005-0406 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2005-0406 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2005-0406 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2005-0406 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2005-0406 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2005-0406 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2005-0406 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2005-0406 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2005-0406 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-0563 | NONE0 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-48074 | NONE0 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2017-14988 | NONE0 | libopenexr-3-1-30 3.1.5-5 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2025-48074 | NONE0 | libopenexr-dev 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2017-14988 | NONE0 | libopenexr-dev 3.1.5-5 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-39328 | NONE0 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-39328 | NONE0 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-4214 | NONE0 | libpng-dev 1.6.39-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-4214 | NONE0 | libpng16-16 1.6.39-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-14330 | NONE0 | libpulse0 16.1+dfsg1-2+b1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-0864 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-0864 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-27943 | NONE0 | libquadmath0 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-3632 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3632 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-29088 | NONE0 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-29088 | NONE0 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-27943 | NONE0 | libstdc++-12-dev 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-27943 | NONE0 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-3164 | NONE0 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6228 | NONE0 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61143 | NONE0 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-3164 | NONE0 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6228 | NONE0 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61143 | NONE0 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-3164 | NONE0 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6228 | NONE0 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61143 | NONE0 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-27943 | NONE0 | libtsan2 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-27943 | NONE0 | libubsan1 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-10911 | NONE0 | libxslt1-dev 1.1.35-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-10911 | NONE0 | libxslt1.1 1.1.35-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-0597 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-23005 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31082 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-37454 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-4133 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52485 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52590 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52591 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52625 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52629 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52648 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52671 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52676 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52761 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52770 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52797 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52888 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52920 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53149 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53231 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53261 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53336 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53353 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53367 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53394 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53429 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53460 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53491 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53523 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53529 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53538 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53574 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53627 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53846 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53999 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54013 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54280 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-6039 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-2193 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-25740 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26670 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26677 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26691 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26740 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26756 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26799 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26841 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26866 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26876 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26902 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26947 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26948 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26953 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26962 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27010 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27011 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27041 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27057 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27062 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27079 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35784 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35794 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35799 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35808 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35860 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35904 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35924 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35931 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35942 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35945 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35946 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35951 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35961 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36911 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36951 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38557 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38564 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38594 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38608 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38620 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38622 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38625 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40965 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40969 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40975 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40998 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40999 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41008 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41023 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41031 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41082 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42128 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42139 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42239 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42241 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42243 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42279 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42317 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43819 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43824 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43850 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43872 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-43899 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43901 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43913 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44963 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45015 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46678 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46681 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46698 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46727 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46728 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46730 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46754 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46760 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46765 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46775 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46776 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46806 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46808 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46834 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46860 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47141 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47658 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47661 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47662 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47664 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47703 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47752 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47794 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49568 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49893 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49901 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49906 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49908 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49910 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49914 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49916 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49918 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49919 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49920 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49921 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49922 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49923 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49926 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49940 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49945 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49970 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49988 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50009 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50017 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50028 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50111 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50166 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50285 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50289 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-52559 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-52560 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53051 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53056 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53079 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53085 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53089 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53090 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53091 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53094 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53114 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53134 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53187 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53195 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53219 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53224 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53687 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-54683 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56544 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56565 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56566 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56583 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56588 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56591 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56592 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56611 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56641 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56692 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56712 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56742 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57804 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57809 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57872 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57888 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57975 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57976 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57999 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58006 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58012 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58053 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58089 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58094 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58095 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58096 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58097 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58098 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58100 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58237 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58241 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21634 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21635 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21649 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21656 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21658 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21673 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21693 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21696 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21723 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21729 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21768 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21801 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21831 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21836 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21870 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21872 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21885 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21888 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21894 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21907 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21949 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21955 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21961 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21972 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21976 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22028 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22037 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 28.2% High Exploitation Risk | Not Applicable |
| CVE-2025-22043 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22048 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22053 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22057 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22070 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22103 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22109 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22113 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22125 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22127 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23129 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23130 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23131 | NONE0 | linux-libc-dev 6.1.176-1 fixed in 6.1.177-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23132 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37747 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37800 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37802 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37806 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37807 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37833 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37834 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37842 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37853 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37856 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37860 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37880 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37893 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37956 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37977 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38006 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38014 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38029 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38038 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38039 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38041 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38042 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38045 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38059 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38064 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38080 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38096 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38127 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38132 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38140 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38195 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38203 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38207 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38237 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38244 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38246 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38261 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38264 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38272 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38283 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38311 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38333 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38359 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38426 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38429 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38438 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38449 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38507 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38531 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38544 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38590 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38597 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38615 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38692 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38705 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38709 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38716 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39677 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39705 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39707 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39720 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39732 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39746 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39747 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39762 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39767 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39779 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39789 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39829 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39833 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39850 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39851 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39886 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39910 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39925 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39932 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39933 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39940 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39947 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39989 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40075 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40102 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40160 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40325 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40339 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68188 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68209 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68236 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68304 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68379 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71109 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71129 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71138 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71160 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71184 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71188 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71202 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71227 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71272 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71273 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71285 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71289 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71313 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71315 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22996 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23000 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23088 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23137 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23138 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23213 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23214 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23247 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23265 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23272 | NONE0 | linux-libc-dev 6.1.176-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23276 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23278 | NONE0 | linux-libc-dev 6.1.176-1 fixed in 6.1.177-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23330 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23346 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23371 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23374 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23419 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23465 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23472 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31410 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31420 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31451 | NONE0 | linux-libc-dev 6.1.176-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31458 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31462 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31487 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31531 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31537 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31557 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31560 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31579 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31592 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31606 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31610 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31648 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31655 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31675 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31677 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31692 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31722 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31723 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31724 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31725 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31767 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31771 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31777 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43009 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43010 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43016 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43022 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43036 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43042 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43048 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43073 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43083 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43088 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43091 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43101 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43107 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43115 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43118 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43119 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43129 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43137 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43153 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43161 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43167 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43170 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43172 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43173 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43204 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43213 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43215 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43216 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43234 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43244 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43271 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43288 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43299 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43308 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43309 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43310 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43317 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43318 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43338 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43344 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43352 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43353 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43362 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43409 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43413 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43416 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43419 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43443 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43456 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43491 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45855 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45858 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45877 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45892 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45897 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45899 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45901 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45917 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45934 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45944 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45961 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45963 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45981 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45985 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45988 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45993 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46000 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46012 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46014 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46032 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46059 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46071 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46111 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46148 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46153 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46156 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46157 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46158 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46170 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46200 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46225 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46226 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46229 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46245 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46252 | NONE0 | linux-libc-dev 6.1.176-1 fixed in 6.1.177-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46254 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46282 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46302 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46312 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52928 | NONE0 | linux-libc-dev 6.1.176-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52936 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52937 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52944 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52961 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52988 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52990 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53015 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53017 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53018 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53027 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53070 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53076 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53108 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53115 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53117 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53118 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53120 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53122 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53139 | NONE0 | linux-libc-dev 6.1.176-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53158 | NONE0 | linux-libc-dev 6.1.176-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53163 | NONE0 | linux-libc-dev 6.1.176-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53167 | NONE0 | linux-libc-dev 6.1.176-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53220 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53226 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53229 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53232 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53237 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53258 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53265 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53285 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53292 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53297 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53313 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53317 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53325 | NONE0 | linux-libc-dev 6.1.176-1 fixed in 6.1.177-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53358 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2008-2544 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2011-4915 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2011-4916 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2011-4917 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9892 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9900 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-10723 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-8660 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2017-13693 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-13694 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12928 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12378 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12379 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12380 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12381 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12382 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12455 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-4543 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-31081 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31085 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-4134 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52653 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-53823 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53857 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54030 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54088 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35843 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39990 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40057 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40196 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68219 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68334 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68378 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68794 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68822 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31486 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43253 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53083 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53102 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53106 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53284 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53327 | NONE0 | linux-libc-dev 6.1.176-1 fixed in 6.1.177-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53353 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-0864 | NONE0 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-0864 | NONE0 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-27171 | NONE0 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-27171 | NONE0 | zlib1g-dev 1:1.2.13.dfsg-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-2574 | NONE0 | glib-networking 2.74.0-4 No fix yet | — | Not Applicable |
| CVE-2026-2574 | NONE0 | glib-networking-common 2.74.0-4 No fix yet | — | Not Applicable |
| CVE-2026-2574 | NONE0 | glib-networking-services 2.74.0-4 No fix yet | — | Not Applicable |
| CVE-2026-41079 | NONE0 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-2379 | NONE0 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2024-2379 | NONE0 | libcurl4 7.88.1-10+deb12u15 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2024-2379 | NONE0 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2026-20643 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-20665 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-20643 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-20665 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1147 | NONE0 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1147 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2025-55160 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2025-55160 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2025-55160 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-52615 | NONE0 | libavahi-client3 0.8-10+deb12u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-52616 | NONE0 | libavahi-client3 0.8-10+deb12u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-52615 | NONE0 | libavahi-common-data 0.8-10+deb12u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-52616 | NONE0 | libavahi-common-data 0.8-10+deb12u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-52615 | NONE0 | libavahi-common3 0.8-10+deb12u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-52616 | NONE0 | libavahi-common3 0.8-10+deb12u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1147 | NONE0 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc-bin 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc-bin 2.36-9+deb12u14 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc6 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc6 2.36-9+deb12u14 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc6-dev 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc6-dev 2.36-9+deb12u14 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-1147 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1147 | NONE0 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-34979 | NONE0 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-4873 | NONE0 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6253 | NONE0 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4873 | NONE0 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6253 | NONE0 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4873 | NONE0 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6253 | NONE0 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-59375 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-59375 | NONE0 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-13595 | NONE0 | libfdisk1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libfdisk1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-1147 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-22693 | NONE0 | libharfbuzz-icu0 6.0.0+dfsg-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-22693 | NONE0 | libharfbuzz0b 6.0.0+dfsg-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2025-55160 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2025-55160 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2025-55160 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2025-55160 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2025-55160 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2025-55160 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2025-55160 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2025-55160 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2025-55160 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2025-55160 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-34380 | NONE0 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34380 | NONE0 | libopenexr-dev 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31437 | NONE0 | libpam-systemd 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | libpam-systemd 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | libpam-systemd 252.39-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12087 | NONE0 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-3713 | NONE0 | libpng-dev 1.6.39-2+deb12u5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3713 | NONE0 | libpng16-16 1.6.39-2+deb12u5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-12781 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-3276 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-3446 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-12781 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-3276 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-3446 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-56226 | NONE0 | libsndfile1 1.2.0-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-32907 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-32909 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-1467 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-1536 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-1760 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-2443 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-2708 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-32907 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-32909 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-1467 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-1536 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-1760 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-2443 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-2708 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42767 | NONE0 | libssl-dev 3.0.20-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42767 | NONE0 | libssl3 3.0.20-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31437 | NONE0 | libsystemd-shared 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | libsystemd-shared 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | libsystemd-shared 252.39-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31437 | NONE0 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-8851 | NONE0 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8851 | NONE0 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8851 | NONE0 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-31437 | NONE0 | libudev1 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | libudev1 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | libudev1 252.39-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2015-9019 | NONE0 | libxslt1-dev 1.1.35-1+deb12u4 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2015-9019 | NONE0 | libxslt1.1 1.1.35-1+deb12u4 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-36881 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71225 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-12087 | NONE0 | perl 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12087 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12087 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-12781 | NONE0 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-3276 | NONE0 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-3446 | NONE0 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-12781 | NONE0 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-3276 | NONE0 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-3446 | NONE0 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-31437 | NONE0 | systemd 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | systemd 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | systemd 252.39-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31437 | NONE0 | systemd-sysv 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | systemd-sysv 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | systemd-sysv 252.39-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-34990 | NONE0 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40338 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71193 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23035 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57360 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1176 | NONE0 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-57360 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1176 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2018-1000021 | NONE0 | git-man 1:2.39.5-0+deb12u3 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2008-3134 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2008-3134 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2008-3134 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-11850 | NONE0 | krb5-multidev 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57360 | NONE0 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1176 | NONE0 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-42250 | NONE0 | libbz2-1.0 1.0.8-5+b1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-42250 | NONE0 | libbz2-dev 1.0.8-5+b1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc-bin 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc6 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc6 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-57360 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1176 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-57360 | NONE0 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1176 | NONE0 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33165 | NONE0 | libde265-0 1.0.11-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2012-0039 | NONE0 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2012-0039 | NONE0 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2012-0039 | NONE0 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2012-0039 | NONE0 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2012-0039 | NONE0 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-57360 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1176 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-11850 | NONE0 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11850 | NONE0 | libgssrpc4 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11850 | NONE0 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11850 | NONE0 | libkadm5clnt-mit12 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11850 | NONE0 | libkadm5srv-mit12 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11850 | NONE0 | libkdb5-10 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11850 | NONE0 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11850 | NONE0 | libkrb5-dev 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11850 | NONE0 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2008-3134 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2008-3134 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2008-3134 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2008-3134 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2008-3134 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2008-3134 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2008-3134 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2008-3134 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2008-3134 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2008-3134 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-34589 | NONE0 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-34589 | NONE0 | libopenexr-dev 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-48959 | NONE0 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-48961 | NONE0 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-28164 | NONE0 | libpng-dev 1.6.39-2+deb12u5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-28164 | NONE0 | libpng16-16 1.6.39-2+deb12u5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-61145 | NONE0 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-61145 | NONE0 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-61145 | NONE0 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2007-3477 | NONE0 | libwmf-0.2-7 0.2.12-5.1 No fix yet | 4.9% Low-Moderate Risk | Not Applicable |
| CVE-2007-3477 | NONE0 | libwmf-dev 0.2.12-5.1 No fix yet | 4.9% Low-Moderate Risk | Not Applicable |
| CVE-2007-3477 | NONE0 | libwmflite-0.2-7 0.2.12-5.1 No fix yet | 4.9% Low-Moderate Risk | Not Applicable |
| CVE-2004-0230 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 80.9% Actively Exploited | Not Applicable |
| CVE-2010-4563 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-48959 | NONE0 | perl 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-48961 | NONE0 | perl 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-48959 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-48961 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-48959 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-48961 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2005-3660 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2007-5686 | NONE0 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-60018 | NONE0 | glib-networking 2.74.0-4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-60018 | NONE0 | glib-networking-common 2.74.0-4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-60018 | NONE0 | glib-networking-services 2.74.0-4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-14017 | NONE0 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-14017 | NONE0 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-14017 | NONE0 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules-bin 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-runtime 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam0g 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-0716 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6324 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-0716 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6324 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-30258 | NONE0 | gnupg-l10n 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68972 | NONE0 | gnupg-l10n 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-30258 | NONE0 | gnupg-utils 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68972 | NONE0 | gnupg-utils 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-30258 | NONE0 | gpg-wks-client 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68972 | NONE0 | gpg-wks-client 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-30258 | NONE0 | gpg-wks-server 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68972 | NONE0 | gpg-wks-server 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-30258 | NONE0 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68972 | NONE0 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-10536 | NONE0 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-15224 | NONE0 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-10536 | NONE0 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-15224 | NONE0 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-10536 | NONE0 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-15224 | NONE0 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-1376 | NONE0 | libdw1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-1376 | NONE0 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libfdisk1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2017-14159 | NONE0 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-modules 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-modules-bin 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-runtime 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam0g 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-20794 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-52771 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53447 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-24864 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26869 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27408 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36024 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36949 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39508 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42107 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46787 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46870 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-50135 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53176 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53178 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56729 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57857 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57974 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21651 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21732 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21825 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21892 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22115 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38234 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38524 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38717 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39726 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39754 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39927 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39961 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40139 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68296 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68745 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71074 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23004 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23118 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23207 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23302 | NONE0 | linux-libc-dev 6.1.176-1 fixed in 6.1.177-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23348 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23394 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43053 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45949 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46017 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2017-0630 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-16230 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16234 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-15213 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-4010 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2012-4542 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-1502 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-1502 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-1502 | NONE0 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-1502 | NONE0 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2020-14304 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-54263 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42123 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40206 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68768 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-17977 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-26661 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26662 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26672 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26757 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26758 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26768 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-10028 | NONE0 | glib-networking 2.74.0-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-10028 | NONE0 | glib-networking-common 2.74.0-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-10028 | NONE0 | glib-networking-services 2.74.0-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-25068 | NONE0 | libasound2 1.2.8-1+b1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-25068 | NONE0 | libasound2-data 1.2.8-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2011-3389 | NONE0 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 73.3% Actively Exploited | Not Applicable |
| CVE-2026-28861 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-20691 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-28871 | NONE0 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-44169 | NONE0 | libmariadb-dev 1:10.11.18-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-44169 | NONE0 | libmariadb-dev-compat 1:10.11.18-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-44169 | NONE0 | libmariadb3 1:10.11.18-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-39327 | NONE0 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-39327 | NONE0 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-4035 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-4476 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-4035 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-4476 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-45346 | NONE0 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2021-45346 | NONE0 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-28861 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-20691 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-28871 | NONE0 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2007-3476 | NONE0 | libwmf-0.2-7 0.2.12-5.1 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2007-3476 | NONE0 | libwmf-dev 0.2.12-5.1 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2007-3476 | NONE0 | libwmflite-0.2-7 0.2.12-5.1 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2010-5321 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-44169 | NONE0 | mariadb-common 1:10.11.18-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-15719 | NONE0 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2024-31852 | NONE0 | libllvm15 1:15.0.6-4+b1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-41848 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-16089 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-42156 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42158 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-16229 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16231 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16232 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-16233 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2010-4756 | NONE0 | libc-bin 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2010-4756 | NONE0 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2010-4756 | NONE0 | libc6 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2010-4756 | NONE0 | libc6-dev 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2025-0725 | NONE0 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-0725 | NONE0 | libcurl4 7.88.1-10+deb12u15 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-0725 | NONE0 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-25260 | NONE0 | libdw1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-25260 | NONE0 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-60019 | NONE0 | glib-networking 2.74.0-4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-60019 | NONE0 | glib-networking-common 2.74.0-4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-60019 | NONE0 | glib-networking-services 2.74.0-4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61860 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61868 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61871 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61860 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61868 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61871 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61860 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61868 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61871 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2011-3374 | NONE0 | libapt-pkg6.0 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-1152 | NONE0 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-41080 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-41080 | NONE0 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-7883 | NONE0 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-61860 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61868 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61871 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61860 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61868 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61871 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61860 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61868 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61871 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61860 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61868 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61871 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61860 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61868 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61871 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61860 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61868 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61871 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61860 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61868 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61871 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61860 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61868 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61871 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61860 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61868 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61871 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61860 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61868 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61871 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2025-4945 | NONE0 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-4945 | NONE0 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-56433 | NONE0 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-35501 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66861 | NONE0 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66862 | NONE0 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66861 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66862 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-3219 | NONE0 | gnupg-l10n 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-3219 | NONE0 | gnupg-utils 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-3219 | NONE0 | gpg-wks-client 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-3219 | NONE0 | gpg-wks-server 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-3219 | NONE0 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56375 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61859 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-56375 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61859 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-56375 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61859 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2025-66861 | NONE0 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66862 | NONE0 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-50422 | NONE0 | libcairo-gobject2 1.16.0-7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-50422 | NONE0 | libcairo-script-interpreter2 1.16.0-7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-50422 | NONE0 | libcairo2 1.16.0-7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-50422 | NONE0 | libcairo2-dev 1.16.0-7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66861 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66862 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66861 | NONE0 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66862 | NONE0 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66861 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66862 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3949 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56375 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61859 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-56375 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61859 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-56375 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61859 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-56375 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61859 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-56375 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61859 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-56375 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61859 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-56375 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61859 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-56375 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61859 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-56375 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61859 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-56375 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61859 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2025-6141 | NONE0 | libncurses-dev 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncurses5-dev 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncurses6 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncursesw5-dev 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncursesw6 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | libpam-systemd 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | libpam-systemd 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2011-4116 | NONE0 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-4016 | NONE0 | libproc2-0 2:4.0.2-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3479 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3479 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-70873 | NONE0 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-70873 | NONE0 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | libsystemd-shared 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | libsystemd-shared 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8961 | NONE0 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-9165 | NONE0 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8961 | NONE0 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-9165 | NONE0 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8961 | NONE0 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-9165 | NONE0 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | libudev1 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | libudev1 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2015-2877 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-54227 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54233 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50057 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50211 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40268 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40303 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-bin 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2011-4116 | NONE0 | perl 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2011-4116 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2011-4116 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-4016 | NONE0 | procps 2:4.0.2-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3479 | NONE0 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3479 | NONE0 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | systemd 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | systemd 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | systemd-sysv 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | systemd-sysv 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-11731 | NONE0 | libxslt1-dev 1.1.35-1+deb12u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11731 | NONE0 | libxslt1.1 1.1.35-1+deb12u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-57062 | NONE0 | gnupg-l10n 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-57062 | NONE0 | gnupg-utils 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-57062 | NONE0 | gpg-wks-client 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-57062 | NONE0 | gpg-wks-server 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-57062 | NONE0 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61862 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61864 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61865 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61867 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61869 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61862 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61864 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61865 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61867 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61869 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61862 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61864 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61865 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61867 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61869 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61862 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61864 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61865 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61867 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61869 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61862 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61864 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61865 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61867 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61869 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61862 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61864 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61865 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61867 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61869 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61862 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61864 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61865 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61867 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61869 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61862 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61864 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61865 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61867 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61869 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61862 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61864 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61865 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61867 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61869 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61862 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61864 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61865 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61867 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61869 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61862 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61864 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61865 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61867 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61869 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61862 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61864 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61865 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61867 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61869 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61862 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61864 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61865 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61867 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61869 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2025-69644 | NONE0 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69644 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69644 | NONE0 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69644 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69644 | NONE0 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69644 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61872 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61872 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61872 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-24515 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-24515 | NONE0 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61872 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61872 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61872 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61872 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61872 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61872 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61872 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61872 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61872 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61872 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2024-13978 | NONE0 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8534 | NONE0 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-13978 | NONE0 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8534 | NONE0 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-13978 | NONE0 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8534 | NONE0 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-11191 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2007-3719 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42155 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.2.15-2+b13 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-8458 | NONE0 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-39043 | NONE0 | gstreamer1.0-plugins-good 1.22.0-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-39044 | NONE0 | gstreamer1.0-plugins-good 1.22.0-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-61464 | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61464 | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61464 | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-56109 | NONE0 | libasound2 1.2.8-1+b1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56109 | NONE0 | libasound2-data 1.2.8-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libblkid1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl4-openssl-dev 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-51792 | NONE0 | libde265-0 1.0.11-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38949 | NONE0 | libde265-0 1.0.11-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-38950 | NONE0 | libde265-0 1.0.11-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45382 | NONE0 | libde265-0 1.0.11-1+deb12u2 No fix yet | — | Not Applicable |
| CVE-2026-45383 | NONE0 | libde265-0 1.0.11-1+deb12u2 No fix yet | — | Not Applicable |
| CVE-2026-49295 | NONE0 | libde265-0 1.0.11-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-49337 | NONE0 | libde265-0 1.0.11-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-49346 | NONE0 | libde265-0 1.0.11-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-54240 | NONE0 | libde265-0 1.0.11-1+deb12u2 No fix yet | — | Not Applicable |
| CVE-2026-54241 | NONE0 | libde265-0 1.0.11-1+deb12u2 No fix yet | — | Not Applicable |
| CVE-2025-61147 | NONE0 | libde265-0 1.0.11-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-45913 | NONE0 | libegl-mesa0 22.3.6-1+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libegl-mesa0 22.3.6-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libegl-mesa0 22.3.6-1+deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libegl-mesa0 22.3.6-1+deb12u2 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-45924 | NONE0 | libegl1 1.6.0-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-56131 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56407 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56408 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56409 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56131 | NONE0 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56407 | NONE0 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56408 | NONE0 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56409 | NONE0 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libfdisk1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libfdisk1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2023-45913 | NONE0 | libgbm1 22.3.6-1+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libgbm1 22.3.6-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libgbm1 22.3.6-1+deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libgbm1 22.3.6-1+deb12u2 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-45924 | NONE0 | libgl-dev 1.6.0-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45924 | NONE0 | libgl1 1.6.0-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45913 | NONE0 | libgl1-mesa-dri 22.3.6-1+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libgl1-mesa-dri 22.3.6-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libgl1-mesa-dri 22.3.6-1+deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libgl1-mesa-dri 22.3.6-1+deb12u2 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-45913 | NONE0 | libglapi-mesa 22.3.6-1+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libglapi-mesa 22.3.6-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libglapi-mesa 22.3.6-1+deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libglapi-mesa 22.3.6-1+deb12u2 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-45924 | NONE0 | libgles2 1.6.0-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45924 | NONE0 | libglvnd0 1.6.0-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45924 | NONE0 | libglx-dev 1.6.0-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45913 | NONE0 | libglx-mesa0 22.3.6-1+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libglx-mesa0 22.3.6-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libglx-mesa0 22.3.6-1+deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libglx-mesa0 22.3.6-1+deb12u2 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-45924 | NONE0 | libglx0 1.6.0-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-41069 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-47178 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-47247 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-47254 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-47709 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-47714 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-48029 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-50142 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| CVE-2024-25269 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-47251 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| CVE-2025-29070 | NONE0 | liblcms2-2 2.14-2+deb12u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-29070 | NONE0 | liblcms2-dev 2.14-2+deb12u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-61464 | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61464 | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61464 | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61464 | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61464 | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61464 | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61464 | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61464 | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61464 | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-61464 | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u12 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount-dev 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libmount-dev 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libmount1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-58055 | NONE0 | libnghttp2-14 1.52.0-1+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-31047 | NONE0 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-31047 | NONE0 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-45924 | NONE0 | libopengl-dev 1.6.0-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45924 | NONE0 | libopengl0 1.6.0-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | libperl5.36 5.36.0-7+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-7017 | NONE0 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-45927 | NONE0 | libslang2 2.3.3-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-45929 | NONE0 | libslang2 2.3.3-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2025-7709 | NONE0 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11822 | NONE0 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50812 | NONE0 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50813 | NONE0 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-7709 | NONE0 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11822 | NONE0 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50812 | NONE0 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50813 | NONE0 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-27587 | NONE0 | libssl-dev 3.0.20-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-27587 | NONE0 | libssl3 3.0.20-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-36849 | NONE0 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | — | Not Applicable |
| CVE-2026-36849 | NONE0 | libtiff6 4.5.0-6+deb12u4 No fix yet | — | Not Applicable |
| CVE-2026-36849 | NONE0 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libuuid1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libuuid1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| TEMP-0601525-BEBB65 | NONE0 | libwmf-0.2-7 0.2.12-5.1 No fix yet | — | Not Applicable |
| TEMP-0601525-BEBB65 | NONE0 | libwmf-dev 0.2.12-5.1 No fix yet | — | Not Applicable |
| TEMP-0601525-BEBB65 | NONE0 | libwmflite-0.2-7 0.2.12-5.1 No fix yet | — | Not Applicable |
| CVE-2024-58249 | NONE0 | libwxbase3.2-1 3.2.2+dfsg-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-58249 | NONE0 | libwxgtk-gl3.2-1 3.2.2+dfsg-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-58249 | NONE0 | libwxgtk-webview3.2-1 3.2.2+dfsg-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-58249 | NONE0 | libwxgtk-webview3.2-dev 3.2.2+dfsg-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-58249 | NONE0 | libwxgtk3.2-1 3.2.2+dfsg-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-58249 | NONE0 | libwxgtk3.2-dev 3.2.2+dfsg-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31432 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31706 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43490 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40003 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40077 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40097 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40137 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40180 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40266 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40289 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40311 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40333 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40337 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40354 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68190 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68320 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68322 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68809 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71065 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71198 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23393 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31707 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43258 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46204 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53107 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53330 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53332 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53345 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43249 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | — | Not Applicable |
| CVE-2023-53851 | NONE0 | linux-libc-dev 6.1.176-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | mount 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | mount 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2025-27587 | NONE0 | openssl 3.0.20-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl 5.36.0-7+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-7017 | NONE0 | perl 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| TEMP-0517018-A83CE6 | NONE0 | sysvinit-utils 3.06-4 No fix yet | — | Not Applicable |
| TEMP-0290435-0B57B5 | NONE0 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | util-linux 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | util-linux 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | uuid-dev 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | uuid-dev 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-58469 | NONE0 | wget 1.21.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-58249 | NONE0 | wx-common 3.2.2+dfsg-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-58249 | NONE0 | wx3.2-headers 3.2.2+dfsg-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.